Thread: signify with -C
View Single Post
  #5   (View Single Post)  
Old 14th September 2021
jmccue jmccue is offline
Real Name: John McCue
Package Pilot
 
Join Date: Aug 2012
Location: here
Posts: 167
Default

About SHA256 makes sense, so I just need to do this instead just in case. But I did not originally run into the issue since SHA256* did not exist:
Code:
sha256 * | egrep -v '\(SHA256\)|\(SHA256\.sig\)' > SHA256
"SHA256 -c SHA256" by itself will not work for me since I am trying to use signify(1) for file signing instead of gpg(1).

As things stand, I think I am all set to sign all files (and large files) in a specific directory without using having to use gpg(1), unless someone knows of a better "signify" method of signing files.

It is interesting how this seems to be done, one signs SHA256 instead of each file in the directory. This is different than what you would do using gpg(1) and this method generates just 1 "signed" file instead of multiple *.asc files.

Thanks

Last edited by jmccue; 14th September 2021 at 05:06 PM. Reason: typo
Reply With Quote