Hi,
I am a h0peless n00b, I admit it! Still, I kinda expected the reality to match the map, 100%. When I downloaded and installed the WD Suite v/1.95, I learned right away that I should change the SSL certificate key, since it is the same for everyone who downloads the Suite until changed by the individual user. I was referred to a page to do that via a link. When I got to the page in question, entitled "SSL Private/Public Key-Pair Setup for Apache 2.0", I read the following opening lines:
"For a web-server to be able to accept 'https://' requests, a private/public key-pair (for Apache2 w/ mod_ssl) needs to be generated and stored in the proper location(s).
Note: Before proceeding - the location of executable 'openssl.exe' must be in the PATH. Also, make sure that 'openssl.exe' can find its configuration file 'openssl.cnf'.
To create a self-signed private/public 1024 bit key-pair that will be valid for 365 days...
Open the commad line, and change to the directory that contains 'openssl.exe'...
cd /d C:\www\openssl\bin {NB: my emphasis}
Creates a certificate signing request (server.csr) and private key (privkey.pem).
Note:
* 'common name' is the exact name of your website (example: www.yourdomain.com).
* If openssl.cnf is not fully configured, you will be asked several questions.
* While not required, openssl.cnf can be edited with the proper information; that will not be asked for if present."The problem is that the command line opens, not surprisingly, like this: "C:\www>", and any attempt to access "cd /d C:\www.openssl\bin", or "C:\www.openssl\bin", or just "openssl", results in an error string. I assume that "the command line" refers to the "command prompt" of the Suite's Web-Developer Controller window? If there is the slightest ambiguity - maybe that the "command line" refers to the MS DOS command prompt - then that should have been clarified. Of course, I cannot know whether "the command line" and "the command prompt" are one and the same thing.
On the GUI that comes with the program I installed (version 1.95), there seems to only be a reference to a "command prompt", not a "command line". I am a stickler for mappings reflecting reality - believing that those who violate the sanctity of this should have their fingers broken (only one joint at a time, of course) until one absorbs the lesson.
The instructions go on to say that such and such a line should be altered, but it begins, in the above, by indicating that key pairs will be generated by writing the listed code in the
command line, whatever that is! I dare not proceed further until I am aware of what I am doing. I need specifically to know where the devil the "command line" referred to is located, and if it is the same as the command prompt in the Suite, then how the devil one can generate the key pairs mentioned, since the given code string only generates errors. I might add that I did eventually get into the "openssl" directory by simply writing "dir" at the C:\www> prompt. I could see that there was indeed an "openssl" directory, and I could also enter that directory, but since I was unable to first generate the key pairs mentioned, there was no point in proceeding further.
I will end my rant here, in case it turns out that "command line" and "command prompt" are NOT the same animals...
Yours,
codenode