I'm also not finding any documentation on what the ppk format
consists of. [...] Since the source code is made available, I'm
assuming that the PPK file creation/format is likewise open,
Zac Morris <z...@zacwolf.com> wrote:
I'm also not finding any documentation on what the ppk formatYes, and there's a comment describing it in the code:
consists of. [...] Since the source code is made available, I'm
assuming that the PPK file creation/format is likewise open,
https://git.tartarus.org/?p=simon/putty.git;a=blob;f=sshpubk.c;h=b8d7ffb2014569b2654453dcdf6ba62ed76fc098;hb=6fc0eb29ac30421524c9d9db6e359c364db413d8#l473
Sorry it was hard for you to find. If you feel like pulling that
comment out into an appendix in the manual, I'd accept a patch.
Could you please give more detail on: "the plaintext version of the
private part, including the final padding"
When I look through the code (Line 759-766) it looks like the string
that is being built to HMAC hash includes the private_blob *post* byte64 decode AND *post* AES decryption? Is that correct? That is confusing me regarding your comment about the plaintext.
So, during decoding:
* the base64 data is decoded to binary data
* that binary data is decrypted
* the decrypted data ("plaintext") is used to verify the MAC
Anything jump out at you?
Anything jump out at you?No, nothing obvious. So the next step is surely to debug everything in detail, printing out all the intermediate values.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 78:27:44 |
Calls: | 6,658 |
Calls today: | 4 |
Files: | 12,203 |
Messages: | 5,332,975 |
Posted today: | 1 |