Hi, I'm in the process of tinkering with slackware 12.0 and found a nasty pitfall. While 11.0 used "uuencode (GNU sharutils) 4.6.3", slackware 12.0 uses "uuencode - GMime 2.2.9" The difference between those two is the length of output lines: KvmUf1QL24tMm2WqNBngufef05ggcrePvKUj/InniYpWkkGvvVSWaD23PfjP of GNU sharutils, and tC22uMJKMY1Rnun/EptRojfTdeURMgF4ny/2Mne06sYOag5sSEgWE+BC6UM/yuDjRI0LOxg4otDu of GMime 2.2.9 This broke several scripts on my system which relied on the length of output lines of GNU sharutils uuencode. Among them, the examples of loop-aes.readme As workaround for creating loop-aes v3 keys on systems with GMime-uuencode you can use instead openssl rand -base64 3120 | head -n 66 | tail -n 65 | gpg ... gpg --gen-random 1 3120 | openssl enc -base64 | gpg ... head -c 3120 /dev/random | openssl enc -base64 | gpg ... -- left blank, right bald
Attachment:
pgpZk4XqQnsie.pgp
Description: PGP signature
