🚀 go-pugleaf

Thus said darrell@cse.ucsc.edu (Darrell Long):
>If I set the RIPEM_KEY_TO_PRIVATE_KEY environment variable, I can encrypt but
>not decrypt.  For example,
>
>sequoia [2]% ripem -e -m encrypted -r darrell@sequoia | ripem -d
>Hello world!
>Private key could not be decrypted with this password.

Hmmm.... curious.

The fact that it complains "private key could not be decrypted with this
password" does not necessarily mean that the error was in the "ripem -d"
call; it probably was in the first call to RIPEM to encrypt.  Most likely,
there was something about the passphrase (spaces, shell metacharacters,
etc.) that didn't get to RIPEM unchanged.  Was "XYZZY" the passphrase?

I can't duplicate this bug; what does it show if you turn on debugging
output (-D 5)?
-- 
Marc VanHeyningen    mvanheyn@whale.cs.indiana.edu    MIME & RIPEM accepted
"I cannot recommend this candidate too highly or say enough good things about
him.  In my opinion you will be lucky to get him to work for you.  I urge you
to waste no time making him an offer.  No one would be better for the job."