Topic: No CSR file written

[theprophecy]

Win Server 2003/Apache2.2.4/OpenSSL 0.9.8e

Will not under any circumstances write a .csr file. Does not throw any errors, just... doesn't actually do anything. The command's pretty straightforward:

openssl req -new -key mykey.key -out mycsr.csr

It goes through the whole Q&A process, just... doesn't write an output CSR file. Apache 2.0.52 and OpenSSL 0.9.7 works flawlessly. I've tried both the openssl.exe in Apache2\bin and in OpenSSL\bin, both behave the same. I've dir /s'd the whole drive, the files are definitely not being written anywhere. What is the cause and fix?

[tdonovan]

I had no problem generating mycsr.csr on a Windows Server 2003/Apache2.2.4/OpenSSL 0.9.8e system,
although I needed to point to the correct openssl configuration file.

If you got Apache 2.2.4/OpenSSL here at Apache Lounge - the openssl.cnf file is in the Apache2\conf directory.

openssl genrsa -out mykey.key

openssl req -config \Apache2\conf\openssl.cnf -new -key mykey.key -out mycsr.csr

-tom-

p.s. Note that openssl.cnf is incorrectly identified as a SpeedDial file by Windows Explorer.

[theprophecy]

Yes, I've done exactly that. I've even cut-and-pasted the exact same thing (hell, I've cut-and-pasted your post) and it runs through the whole process and generates... nothing. No CSR file, no error, not a bloody thing.

[theprophecy]

Apparently OpenSSL does not like names containing the word "aux". When I name either the key or csr aux.key or aux.csr or any variant thereof it does not work. wtf.key and wtf.csr do however work.

[tdonovan]

Yes - AUX is a reserved device name in Windows.
Any file named aux.* refers to the serial port - usually COM1.

The name mycsr.csr should have worked fine, though, if you cut-and-pasted my post?!?

-tom-