Another bug in RIPEM?

Article View: alt.security.ripem

Article #46

Back to alt.security.ripem Previous Next

#46

From: Darrell Long
Date: Mon, 11 Jan 1993 00:44

22 lines
1171 bytes

If I set the RIPEM_KEY_TO_PRIVATE_KEY environment variable, I can encrypt but
not decrypt.  For example,

sequoia [1]% printenv
HOME=/home/darrell
LOGNAME=darrell
USER=darrell
...
RIPEM_PUBLIC_KEY_FILE=/home/darrell/lib/keys/public
RIPEM_PRIVATE_KEY_FILE=/home/darrell/lib/keys/private
RIPEM_KEY_TO_PRIVATE_KEY=XYZZY
sequoia [2]% ripem -e -m encrypted -r darrell@sequoia | ripem -d
Hello world!
Private key could not be decrypted with this password.

But if I don't set it, and type the password each time, everything works fine:

sequoia [1]% ripem -e -m encrypted -r darrell@sequoia | ripem -d
Hello world!
Enter password to private key: 
Enter password to private key: 
Hello world!

Technical Details

Message-ID: <1iqftkINN39h@darkstar.UCSC.EDU>

Path:

arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!howland.reston.ans.net!usc!sol.ctr.columbia.edu!ucselx!newshub.sdsu.edu!darkstar.UCSC.EDU!darrell

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!howland.reston.ans.net!usc!sol.ctr.columbia.edu!ucselx!newshub.sdsu.edu!darkstar.UCSC.EDU!darrell
From: darrell@cse.ucsc.edu (Darrell Long)
Newsgroups: alt.security.ripem
Subject: Another bug in RIPEM?
Date: 11 Jan 1993 00:44:36 GMT
Organization: University of California, Santa Cruz (CE/CIS Boards)
Lines: 23
Distribution: world
Message-ID: <1iqftkINN39h@darkstar.UCSC.EDU>
NNTP-Posting-Host: cypress.ucsc.edu