Hi,
I am running as Administrator and tried moving the dlls to the
windows\system32 directory because I remembered this as being an issue
for me in the past.
Ran command from the DOS command line. Will try it again later without
quotes - as has been indicated quotes are not required in my case.
Quotes or no quotes aside the command I have issue to openssl finds the
cnf file but then seems to have an issue using it.
David
On Sun, 27 Jun 2010 20:32 -0400, "Dave Thompson" <dthomp...@prinpay.com>
wrote:
> > From: owner-openssl-us...@openssl.org On Behalf Of David Schulberg
> > Sent: Sunday, 27 June, 2010 08:57
>
> > Have OpenSSL 0.9.8m on Windows 7. I have copied libeay32.dll and
> ssleay32.dll
> > from my to windows\system32 directory.
>
> Aside: You mean from your build dir(s) to system32? Does Seven like that?
> I thought it was supposed to be stricter about \progfiles and \windows .
> Or are you doing everything as Adminstrator, the old-Windows no-security
> way?
>
> > openssl genrsa –des3 –out server.key 1024
>
> > [Winpath]\Apache2.2\bin>openssl req -new
> > -config "..\conf\openssl.cnf" -key server.key -out server.csr
>
> > error on line -1 of ô..\conf\openssl.cnfö
> > 280:error:02001003:system library:fopen:No such
> process:.\crypto\bio\bss_file.c:
> > 126:fopen('ô..\conf\openssl.cnfö','rb')
> > 280:error:2006D080:BIO routines:BIO_new_file:no such
> file:.\crypto\bio\bss_file.c:129:
> > 280:error:0E078072:configuration file routines:DEF_LOAD:no such
> file:.\crypto\conf\conf_def.c:197:
>
> > Wondering what I have wrong...
>
> The filename you specified for configfile didn't work.
>
> Notice that as logged it has bogus characters at beginning
> and end, where your command shows quote characters.
>
> Did you manually type that (openssl req) command?
> If so, exactly what did you type for the quotes?
> Was this in a CommandPrompt=CMD aka "DOS" window,
> or something like mingw bash? (It doesn't look like it.)
>
> Or did you cut&paste from a Microsoft document (e.g. Word)
> or maybe a Microsoft-served webpage (e.g. IIS)?
> Those like to use "smart quotes" which are different
> for left and right and supposedly nicer looking,
> but are NOT the (plain-ASCII) quote character
> accepted by Windows CMD much less Unix shells.
>
> Note you don't actually need any quotes there at all if CMD.
> You may need to quote the backslashes in mingw/cygwin/etc;
> if so it's easier to use (forward)slashes instead.
> That works for most actual programs (not CMD builtins like DIR).
>
>
>
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> User Support Mailing List openssl-users@openssl.org
> Automated List Manager majord...@openssl.org
>
Regards,
David Schulberg
--
http://www.fastmail.fm - IMAP accessible web-mail
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
