You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to use keys to sign a SHA256 hash of a binary, but the UX seems off to me. As far as I can tell so far, there is no output when the signature is successfully verified. The only obvious sign that it did something is a 0 exit code.
That works, because I get "verify failed" if I make a change to the binary.
But, from a user experience perspective I think it would inspire more confidence if a successful verification also had something on stdout, with maybe a -q, --quiet flag to only look at the return code.
The text was updated successfully, but these errors were encountered:
I think the bigger issue is the lack of any output when you verify something. For example, if I sign a file with minisign, I get a nice console output saying that the signature is valid, time, comment, etc.
Hi @gabriel
I want to use keys to sign a SHA256 hash of a binary, but the UX seems off to me. As far as I can tell so far, there is no output when the signature is successfully verified. The only obvious sign that it did something is a 0 exit code.
I started with this:
Then verified with this:
That works, because I get "verify failed" if I make a change to the binary.
But, from a user experience perspective I think it would inspire more confidence if a successful verification also had something on stdout, with maybe a
-q, --quiet
flag to only look at the return code.The text was updated successfully, but these errors were encountered: