On Wed, Jan 08, 2014 at 03:53:32PM -0500, Ted Unangst wrote: > This may or may not be useful. We can embed the message after the > signature and reduce the number of files in half. It's not a lot of > code. (This is how the crypto_sign API originally worked, but we've > since added some metadata, so we still need to destruct and > reconstruct the crypto_sign inputs and outputs.) > > The -e option is added. It works a lot like gzip/gunzip by default. > You sign a message, creating message.txt.sig: > signify -e -S message.txt > You verify message.txt.sig, creating message.txt: > signify -e -V message.txt > Note you always specify the message name. I've cleaned up the source a > bit to disambiguate between "input" and "message". And of course, -o > works as before.
I'm not fond of embedded as a global variable, especially since it's only used by two functions. Can you pass it as a parameter, so that it's more explicit where it's used ?
