alip3d ago
News from #sydbox git: Starting next release, we're going to be signing binary releases with #OpenBSD signify rather than #GnuPG. To enable practical signing in #Exherbo #Gitlab CI, I wrote an #ISC licensed, pure portable #POSIX shell implementation of #OpenBSD signify. signify.sh has no external dependencies and runs with PATH=. It has unit tests embedded which may be run with --test option: https://gitlab.exherbo.org/sydbox/sydbox/-/raw/next/dev/signify.sh #exherbo #linux #security
Show threadmei2d ago
@alip sooo... if /dev/urandom fails to provide randomness for some reason... you just fall back to generating keys with only 32 bits of entropy? don't you think that's a little unwise?

like, don't get me wrong, I've implemented cryptography in bash myself but like, as a *shitpost*
Show threadalip
@mei Thank you very much for the feedback, I have removed the fallback.
Apr 6 at 11:13amWeb
Show threadmei2d ago
@alip cool, glad to hear that! btw, I haven't really taken a proper look at the test suite, do you include the Wycheproof test vectors in there?
Show threadalip2d ago
@mei yes, that's correct. signify.sh includes 65 NIST CAVP SHA-256, 129 NIST CAVP SHA-512, 1024 DJB Ed25519 sign/verify, and 150 Wycheproof Ed25519 vectors.
Show threadmei2d ago
@alip cool, in that case the only thing I'd be worried about is timing side channels, so it'd probably be a good idea to have some kind of warning to not let attackers run signing operations interactively because that could leak secrets