Hallo,
ich installiere für einen Kunden von B1G Software und Server. In der FAQ wird folgendes angegeben:
1. Loggen Sie sich per SSH auf Ihrem Server ein
2. Erstellen Sie Ihr SSL-Zertifikat und Ihren privaten SSL-Schlüssel. Folgen
Sie den Anweisungen und beantworten Sie die Fragen. Das Passwort-Feld
muss freigelassen werden.
openssl req –new –nodes –out req.pem –keyout key.pem
3. Signieren Sie Ihr SSL-Zertifikat:
openssl rsa –in key.pem –out new-key.pem
openssl x509 –in req.pem –out server.cert –req –signkey
new-key.pem –days 999
4. Kopieren Sie SSL-Zertifikat und –Schlüssel in das „tls“-Verzeichnis von
b1gMailServer:
cp new-key.pem /opt/b1gmailserver/tls/server.key
cp server.cert /opt/b1gmailserver/tls/server.cert
Alles nicht schlecht beschrieben, jedoch bekomme ich folgende Ausgabe bei SUSE Linux 9.0 Apache2 :
server1#openssl req .new .nodes .out req.pem .keyout key.pem
unknown option .new
req [options] <infile >outfile
where options are
-inform arg input format - DER or PEM
-outform arg output format - DER or PEM
-in arg input file
-out arg output file
-text text form of request
-pubkey output public key
-noout do not output REQ
-verify verify signature on REQ
-modulus RSA modulus
-nodes don't encrypt the output key
-engine e use engine e, possibly a hardware device
-subject output the request's subject
-passin private key password source
-key file use the private key contained in file
-keyform arg key file format
-keyout arg file to send the key to
-rand file:file:...
load the file (or the files in the directory) into
the random number generator
-newkey rsa:bits generate a new RSA key of 'bits' in size
-newkey dsa:file generate a new DSA key, parameters taken from CA in 'file'
-[digest] Digest to sign with (md5, sha1, md2, mdc2, md4)
-config file request template file.
-subj arg set or modify request subject
-new new request.
-batch do not ask anything during request generation
-x509 output a x509 structure instead of a cert. req.
-days number of days a certificate generated by -x509 is valid for.
-set_serial serial number to use for a certificate generated by -x509.
-newhdr output "NEW" in the header lines
-asn1-kludge Output the 'request' in a format that is wrong but some CA's
have been reported as requiring
-extensions .. specify certificate extension section (override value in config file)
-reqexts .. specify request extension section (override value in config file )
-utf8 input characters are UTF8 (default ASCII)
-nameopt arg - various certificate name options
-reqopt arg - various request text options
Was bitte mache ich falsch ?
ich installiere für einen Kunden von B1G Software und Server. In der FAQ wird folgendes angegeben:
1. Loggen Sie sich per SSH auf Ihrem Server ein
2. Erstellen Sie Ihr SSL-Zertifikat und Ihren privaten SSL-Schlüssel. Folgen
Sie den Anweisungen und beantworten Sie die Fragen. Das Passwort-Feld
muss freigelassen werden.
openssl req –new –nodes –out req.pem –keyout key.pem
3. Signieren Sie Ihr SSL-Zertifikat:
openssl rsa –in key.pem –out new-key.pem
openssl x509 –in req.pem –out server.cert –req –signkey
new-key.pem –days 999
4. Kopieren Sie SSL-Zertifikat und –Schlüssel in das „tls“-Verzeichnis von
b1gMailServer:
cp new-key.pem /opt/b1gmailserver/tls/server.key
cp server.cert /opt/b1gmailserver/tls/server.cert
Alles nicht schlecht beschrieben, jedoch bekomme ich folgende Ausgabe bei SUSE Linux 9.0 Apache2 :
server1#openssl req .new .nodes .out req.pem .keyout key.pem
unknown option .new
req [options] <infile >outfile
where options are
-inform arg input format - DER or PEM
-outform arg output format - DER or PEM
-in arg input file
-out arg output file
-text text form of request
-pubkey output public key
-noout do not output REQ
-verify verify signature on REQ
-modulus RSA modulus
-nodes don't encrypt the output key
-engine e use engine e, possibly a hardware device
-subject output the request's subject
-passin private key password source
-key file use the private key contained in file
-keyform arg key file format
-keyout arg file to send the key to
-rand file:file:...
load the file (or the files in the directory) into
the random number generator
-newkey rsa:bits generate a new RSA key of 'bits' in size
-newkey dsa:file generate a new DSA key, parameters taken from CA in 'file'
-[digest] Digest to sign with (md5, sha1, md2, mdc2, md4)
-config file request template file.
-subj arg set or modify request subject
-new new request.
-batch do not ask anything during request generation
-x509 output a x509 structure instead of a cert. req.
-days number of days a certificate generated by -x509 is valid for.
-set_serial serial number to use for a certificate generated by -x509.
-newhdr output "NEW" in the header lines
-asn1-kludge Output the 'request' in a format that is wrong but some CA's
have been reported as requiring
-extensions .. specify certificate extension section (override value in config file)
-reqexts .. specify request extension section (override value in config file )
-utf8 input characters are UTF8 (default ASCII)
-nameopt arg - various certificate name options
-reqopt arg - various request text options
Was bitte mache ich falsch ?
