> From: owner-openssl-us...@openssl.org On Behalf Of Kurtis Golding
> Sent: Tuesday, 14 June, 2011 23:45
> I have been working with the latest release (1.0.0d) and the
> command line tool, however, I am having some difficulty.
<snips>
> "openssl+.exe" des3 -in T1.txt -out T2.txt
> ... prompts for a password however, the out file is
> never created. No errors, actually no output of any kind.
> [using enc -des3] just causes some directions to appear.
> I was also having some difficulty using the -pass parameter,
> however, -k seems to work ok. using -pass pass:test causes a path
exception..
> Anyway, I was starting to suspect that the command line tool
> has changed ... or I am missing something :(...
> Thanks for any suggestions..
There has been no change I can see in this area, and all cases
you give or mention work for me in 1.0.0d same as older versions.
This really sounds like something screwing up the commandline
even before openssl gets it. What OS and command processor
are you using (e.g. Unix shell or Windows CMD or what?) What
openssl build are you using? In particular AFAIK no standard
build produces an executable with a plussign in the name. Are
you using any kind of input device or modifier that might fix
special characters or expand abbreviations/macros or suchlike?
I assume you are using exactly T1.txt and T2.txt (and T1.txt
exists and contains data). If you sanitized those names and
are on Windows, remember that certain filenames on Windows
that were devices in the days of DOS a decade ago don't work.
http://msdn.microsoft.com/en-us/library/aa365247%28v=vs.85%29.aspx
Try command _input_ rather than command line: either run your
executable and type a command to the "OpenSSL>" prompt; or
pipe or redirect from a file containing the command e.g.
echo des3 -in t1.txt -out t2.txt | openssl
openssl <cmdfile # cmdfile contains that command
# for that latter one, dump the file to check it contains
# exactly and only the desired command (if possible)
Note these only work for commands that don't use stdin for data;
your two examples satisfy this, but some other cases don't.
Or put the one-line commandline (executable plus arguments)
in a Unix script or Windows batch file, making sure it's
exactly right, and invoke that. Especially if you're using
an unusual shell on Unix, use plain /bin/sh for the script.
And env -i to drop any weirdness in the environment variables.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
