get the sourcecode
A bughunter via Unicode <[email protected]>
| Newsgroups | gmane.text.unicode.general |
|---|---|
| Message-ID | <EdTuSW0KcRiK5rDp1Lp66vdG6_9N7iD9nesZc9dJFBRPeJ_qAsbXi4uLE9hRg9AKS5zpe5Hwdw4jAM_RKFbeRI31cRuWOxJKRmZ0WGA6g0Q=@proton.me> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Giacomo wrote: " and your question is too vague (and imprecise) to help." No, my question is specific yet you evaded to answer it with a list of offpoint errata. Where is the sourcecode for the UTF-8 " bytecode to glyph map "? I simply stated the use-case: checksum text. I will agree that PGP should have a precise way to checksum when producing fingerprints of keys. So should SSL. If I must seek hints having no answer. from [email protected] Sent with Proton Mail secure email. -----BEGIN PGP SIGNATURE----- Version: ProtonMail wnUEARYKACcFgmcpmUUJkKkWZTlQrvKZFiEEZlQIBcAycZ2lO9z2qRZlOVCu 8pkAAOrrAQDNS7lMFP17kcxKq/0mwGcst6kRakHTqydi2Ab2QpJBpAD6AhJj hOpZEZCl+Jy3fee4WGhvS6ugS1IHGyEllFFuKQY= =egrh -----END PGP SIGNATURE-----
publickey - [email protected] - 0x66540805.asc
(application/pgp-keys, 653 B)
-----BEGIN PGP PUBLIC KEY BLOCK----- xjMEZu0X1xYJKwYBBAHaRw8BAQdAH0I47jDsPZ6gvb+YUGBnAx7Jyf14AVOH xa8y0+dmN5bNLUFfYnVnaHVudGVyQHByb3Rvbi5tZSA8QV9idWdodW50ZXJA cHJvdG9uLm1lPsKMBBAWCgA+BYJm7RfXBAsJBwgJkKkWZTlQrvKZAxUICgQW AAIBAhkBApsDAh4BFiEEZlQIBcAycZ2lO9z2qRZlOVCu8pkAAD9FAP9/ddT6 56Gka9NtMvmdoY5ktNgqbY5Xbd9fx6kPE5/4tQD/XiialKQHjmwAtbcSe1Q+ 3cxYLxNhjU7mynQspv9dxADOOARm7RfXEgorBgEEAZdVAQUBAQdAnfp/z2Fw RkpvUgf7mqYI9RKnTVadwGfgaQLhmwg3LxMDAQgHwngEGBYKACoFgmbtF9cJ kKkWZTlQrvKZApsMFiEEZlQIBcAycZ2lO9z2qRZlOVCu8pkAAJi8AQC+fnOm 4Vj9QmH4H0GVt7RuOQK+wOQ1PRvpymSjeyBJOwD9GYuvxOAVK8iAupJ+ppwM r36VukIe1pXuHo9RhjveAw0= =FQFw -----END PGP PUBLIC KEY BLOCK-----
publickey - [email protected] - 0x66540805.asc.sig
(application/pgp-signature, 119 B) - not displayed