3 ms·
http://pgp.mit.edu/pks/lookup?search=B9E39278 http://pgp.mit.edu/pks/lookup?search=B9E39278
by amenghra 10y ago
http://pgp.mit.edu/pks/lookup?search=B9E39278 http://pgp.mit.edu/pks/lookup?search=B9E39278
- ktta 10y agowait, this looks interesting. Can someone comment on this? Are you supposed to know the fingerprint after you input name and stuff or before? Or is this just modification of data like how you can add email IDs?
- lmm 10y agoYou're supposed to confirm the fingerprint with the person. At the time the recommendation was a phone call (if you knew their voice) using the PGP word list - it was felt to be computationally implausible to fake that up in realtime. Or people publish fingerprints on their site etc. Obv. the fingerprint only matters if you want to be sure you are talking to someone specific, in which case you usually have a way to know who they are or why you care. For some use cases trust-on-first-use is adequate.
- ktta 10y agoThanks for taking the time, but seems like you didn't click on the link. When you look at the name of the keyholder of the fingerprint (B9E39278), the User Name of the keyholder is same as the fingerprint of the key. I was asking if the User Name is set after the key is generated or before. Or if one can change user name after key generation. And I think you can, so there's nothing interesting here :)
- amenghra 10y agomethod 1: Keep generating keys until you have a collision. method 2: What you said, modify the details. A fun way to play/explore all things GPG is to use a javascript library and Chrome's javascript debugger (e.g. https://openpgpjs.org/ https://openpgpjs.org/)
- ktta 10y agoYeah I was wondering if method 2 exists. I remember reading about something similar but wasn't sure. Thanks for the link!