Generate SHA1 hash for each file in a list

ls [FILENAME] | xargs openssl sha1
List files and pass to openssl to calculate the hash for each file.
Sample Output
7za e ./Tomato_1_25.7z

ls WR*.bin | xargs openssl sha1
SHA1(WR850G.bin)= 0bc270630cb63c9933da4cd2fee2a964e250e97b
SHA1(WRT54GS.bin)= 1b3264845575ac7735b949d8f57c9d2caef5712a
SHA1(WRT54GSv4.bin)= ed8933a0ce41d3404ce012093fd1746f1846940c
SHA1(WRT54G_WRT54GL.bin)= 738ac48ea477b0e6f6054332c293cf0aaf55b1be
SHA1(WRTSL54GS.bin)= 4701058caadc4f0e97e90eb891586583b0b0838b

By: m00dimus
2009-10-03 02:05:43

3 Alternatives + Submit Alt

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: