"If you’ve seen the low level parts of RSA keys, you’ll immediately recognise this. Otherwise, convert it to an unsigned integer and you get 65537 – a common RSA modulus. RSA public keys require two pieces: the modulus and the public exponent. Let’s take a guess that the next piece is going to be the public exponent."<p>That's backwards - 65537 is a common public exponent. The modulus is the 2048-bit long thing.<p>Also, the writer says "2048-byte" RSA key when it's really 2048-bits.
<i>When most people think of SSH keys, they probably think of RSA if they’re aware of the underlying cryptography. Until recently, they would be right: RSA has been a mainstay of public key cryptography for some time now, and although it’s on the way out for new protocols and systems, it will be around for quite some time.</i><p>Why is RSA on the way out? This is news for me. Are there any (potential) weaknesses that have been discovered recently in the RSA? I know that elliptic curve cryptography has shorter (and hence somewhat more convenient) keys, but that fact alone hardly makes RSA obsolete. Are there anything else?
Very clear and informative!<p>I got lost at this part, if anyone could clarify that would be great:<p><i>3. The key uses the PKCS#5 padding scheme: the last byte contains the number of padding bytes; e.g. if there are 5 bytes of padding, it contains 0x05. The last five bytes of the plaintext should then be 0x05 (something you should validate if you are decrypting the key yourself). If you decrypt the key above, you’ll see the last eight bytes are, in fact, 0x08.</i><p>The key is the MD5 of the combination of IV+pass, so how could the last byte of the key be controllable? The last two bytes shown are <i>532b</i>, which is not 0x08? I must be missing some step that happens between getting the MD5 and this padding scheme.
> One of the ideas I’ve also been tossing around is using Github’s public key API to provide a way to sign PGP keys using Github SSH keys. I have much of the groundwork laid out, but I need to actually code everything up.<p>If you didn't know: you can use a gpg key <i>as</i> an ssh key. You configure gpg-agent to act as an ssh-agent. This is quite popular for those that use yubikeys.
Howdy, just a FYI here - your site doesn't display properly on mobile devices, it's all squashed into a tiny column in the middle of the page and the text wrapping is warped in places, additional if you're using Safari the 'reader view' is not available to clean the page and make it more readable.
Hmm, what I've always wondered: why can't I have the SSH public key of the server signed/certified the same way as a SSL public key?<p>That could e.g. allow me to specify "mark all SSH keys certified by company-internal CA as trusted" or putting the expected certificate into DNS...
<i>We can tell from the length field that we need to read 0x00000101 (or 257) bytes; 257 </i> 8 = 2056 bytes, which is in the range for a 2048-byte RSA key (with some of the bits going unused).<i>