On Wed, 2005-08-31 at 22:44 +0200, Oliver Welter wrote: > Hi John, > > > private keys. The passphrases contain the characters [EMAIL PROTECTED] as > > well as > > caps, lower case and numbers. There are no spaces. > > I assume this is the problem, @ and $ are special characters in perl and > at least $ might be interpreted by the bash. Unfortunately I dont have > an idea how to fix it...... > > Oliver Thanks, Oliver. However, it's strange that the passwords previously worked then. The perl problem wouldn't explain why we can't unlock the key from the command line. The $ could except I would suspect that the password input is not being processed by the shell. Just in case, I tried entering it with single quotes to make all characters literal and it still failed.
Any other ideas? We're a bit desperate. By the way, it does appear that the configuration signing returns successful no matter what string is entered so the fact we can seemingly unlock the key within that function may be a red herring - John -- John A. Sullivan III Open Source Development Corporation +1 207-985-7880 [EMAIL PROTECTED] If you would like to participate in the development of an open source enterprise class network security management system, please visit http://iscs.sourceforge.net ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Openca-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openca-users
