<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 28, 2017, at 13:05, Rainer Müller <<a href="mailto:raimue@macports.org" class="">raimue@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 2017-08-24 22:50, Richard L. Hamilton wrote:<br class=""><blockquote type="cite" class="">Attempting<br class="">mcrypt -a enigma --keymode scrypt --bare --decrypt </tmp/test<br class=""><br class="">with a file containing "testing\n" and encrypted (via old Unix crypt(1)) with key "abcdefg", I get the response<br class=""><br class="">File /tmp/test was NOT decrypted successfully.<br class=""><br class="">The same procedure works on CentOS, Ubuntu, and Cygwin, at least. Why is it failing with the MacPorts installation of mcrypt (on Sierra)?<br class=""></blockquote><br class="">Apparently you also need to add the option --no-openpgp, as mcrypt<br class="">otherwise expects input in the OpenPGP format.<br class=""><br class=""> $ mcrypt -a enigma -o scrypt --bare --decrypt --no-openpgp < /tmp/test<br class=""> Enter passphrase:<br class=""><br class=""> testing<br class=""> Stdin was decrypted.<br class=""><br class="">I don't know if this behavior is controlled by a configure option and<br class="">also could not spot any difference in a quick comparison with the Debian<br class="">package. No idea what what causes this.<br class=""><br class="">Rainer<br class=""><br class=""></div></div></blockquote></div><br class=""><div class="">Thanks; that does work, although it seems odd that it wasn't necessary on any other platform (CentOS, Ubuntu, Solaris 11) I tried mcrypt on.</div><div class=""><br class=""></div><div class="">I do see that it's not an unknown issue <a href="https://sourceforge.net/p/mcrypt/patches/11/" class="">https://sourceforge.net/p/mcrypt/patches/11/</a></div><div class=""><br class=""></div><div class="">Perhaps the others had a patch for that which wasn't accepted/incorporated back into the distributed version.</div><div class=""><br class=""></div></body></html>