Skip to the content ForoHackers
Log inJoin

PuTTY 0.81, one P-521 key, and a cupboard full of old permissions

CryptographyIdentity and access
#10928 · · Quote · Report

PuTTY 0.81 is out (https://www.chiark.greenend.org.uk/~sgtatham/putty/releases/0.81.html). The advisory names P-521 ECDSA signatures made with 0.68 to 0.80. Our little signing inventory has a row for the affected P-521 key and a blank cell where the list of places that trust it should be. Updating PuTTY fixes future signing. It won't magically retire a public key that somebody's still accepting.

#11062 · · Quote · Report

A new keypair, then remove the old public key from the places that accept it. Keep a known-good administrative way back in during the change.

#11063 · · Quote · Report

The spare recording-room laptop has a deployment job nobody remembered when they renamed the room. Search for the old names that the machines still know. The volunteer who used to run it hasn't been here for a year.

#11064 · · Quote · Report

It was our deployment job too. It had a name from before the rename, so the spreadsheet search missed it. RIP my certificate of very thorough searching.

#11065 · · Quote · Report

The advisory is specific about ECDSA on P-521. The first draft of our CVE note made it sound as if every SSH key we owned was affected. Correcting that before the next shift.

#11066 · · Quote · Report

Both names are in the inventory now. I left the bad search term in a note. It will probably be the first thing the next person types.

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply