openssl md5 output

2011-07-18 Thread Patrick Donnelly
Why does this command prepend useless redundant information? $ openssl md5 (echo foo) MD5(/dev/fd/63)= d3b07384d113edec49eaa6238ad5ff00 ^ ^ I just cannot fathom why this was done. This is just all around terrible design. Not only is this information redundant and entirely

Re: openssl md5 output

2011-07-18 Thread Patrick Donnelly
On Mon, Jul 18, 2011 at 4:05 PM, Coda Highland chighl...@gmail.com wrote: On Mon, Jul 18, 2011 at 2:41 PM, Patrick Donnelly batr...@batbytes.com wrote: Why does this command prepend useless redundant information? $ openssl md5 (echo foo) MD5(/dev/fd/63)= d3b07384d113edec49eaa6238ad5ff00

Re: openssl md5 output

2011-07-18 Thread Coda Highland
To answer your initial question, consider the case of $ openssl md5 *.txt, where each line needs to have that information. The new format makes the output consistent regardless of manner of implementation, which from a future-proofing standpoint makes more sense than changing the output

Re: openssl md5 output

2011-07-18 Thread Wim Lewis
On 18 Jul 2011, at 1:25 PM, Patrick Donnelly wrote: Are you seriously suggesting that parsing the md5sums of multiple files from the output of openssl md5 *.txt is a sensible use case? It's not just sensible, it's fairly common. The DIGEST(filename)=hexhexhex... output style is in imitation