-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 07/27/2015 07:55 PM, n...@enigmail.net wrote: > Hi MFPA, Thanks a lot for your feedback.
.. > >> Why would the notation value be base64 encoded? What is the >> rationale for preventing users from reading the notation values >> in a key listing? > > Hmm, it was a recommendation by Kristina Fiskerstrand: "the value > should be base64 encoded to avoid some issues" @Kristian: Can you > elaborate on that? It makes the information more compact and will make hkp vindex lists look cleaner. Presuming this information contains data objects in json format it will be interpreted by a parser, and raw data from keyservers anyways shouldn't be trusted directly before validating the signature (including its subpackets/notations) since no crypto has been performed at that point. - -- - ---------------------------- Kristian Fiskerstrand Blog: http://blog.sumptuouscapital.com Twitter: @krifisk - ---------------------------- Public OpenPGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 - ---------------------------- "Knowing is not enough; we must apply. Willing is not enough; we must do ." (Johann Wolfgang von Goethe) -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJVtnGkAAoJECULev7WN52FyFAIAKgXWzCuH8/k96sw+Bgw4Y5O fuAzTVTFk4D4UO9F0T1YIinfWNiDXV37sOGdGdgR5BGNGSyeXNU3R0GgyeM4NTaT K8UGnY2xwpY2wndi8rKpLVj5uoLofCrvhnrqJ1juuNHOXy0xuQarYwB5/5TWYfgT rBBMeIrEUgBita8Eh+7/0H4AkmRioTJIcHZDNqySqA5UF9ai6skcvVIoyh/zAmtH 230shQfx4XG4wJpWTRE7W0oCyEMBl38Pdno0c2GfJ7rHszpnk3DnOViyf9JHFzvI rjWP0DTP7CCsJ3N0YomphnDGxtpZyKJw3R8znk1CU3Q8quZ/R1dlkvF8alwGfxI= =XKeM -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
