4 ms·
signify[1] signatures are 64 bytes + 10 byte header, making total base64 encoded length 100 characters, which would conveniently have fit to even the old alt te
by zokier 7y ago
signify[1] signatures are 64 bytes + 10 byte header, making total base64 encoded length 100 characters, which would conveniently have fit to even the old alt text easily
[1] https://man.openbsd.org/signify https://man.openbsd.org/signify
- upofadown 7y agoHow would you get the public key to verify such a signature?
- zokier 7y ago> There are no key servers for signify. No web of trust. Just keys. The good news is the keys are pretty small. As demonstrated. We can stick them just about everywhere, and we do. They're on the web site, they're on twitter, they're on the top side of CD. 56 base64 characters. You can read it out loud over the phone in under a minute. Wide dispersion makes it harder and harder to intercept all the ways you may get the key and increases the risk of detection should anybody try some funny business. https://www.openbsd.org/papers/bsdcan-signify.html https://www.openbsd.org/papers/bsdcan-signify.html but if you really want to have a central public place for keys, then the recently discussed https://keys.pub https://keys.pub should work, just needs minor format conversion: https://keys.pub/docs/specs/keys.html https://keys.pub/docs/specs/keys.html
- zimpenfish 7y agoI just tried this and I get 140 characters for the `.sig` file - to verify it, you do need the first line "untrusted comment: verify with sig.pub" which adds 39 to the 100 for the signature (but I suppose since that's a standard part, you could take it as read...)