9 More Discussions You Might Find Interesting
1. What is on Your Mind?
Today, I noticed some errors in our SSL cert renewal log files, mostly related to domains where the IP address had changed. Concerned about this, rebuilt out SSL cert, which normally goes well without a hiccup.
However, for today, for some reason which I cannot explain, there was a PHP error... (0 Replies)
Discussion started by: Neo
0 Replies
2. UNIX for Dummies Questions & Answers
How do I find out the SSL cert info on the local server?
How do I know if an ssl cert is installed on local server?
How it was issued to?
Who was the issuer?
What's the expiration date?
Any other relevant information? (1 Reply)
Discussion started by: scj2012
1 Replies
3. UNIX for Advanced & Expert Users
Hey Guys,
I am trying to setup ldap over tls in our lab. I am generating a self signed cert on the ldap server and importing that into the ldap system so it will use ldap over port 636. The clients will be a mix of solaris and redhat. I am lost on what I need to do on the client side to get... (0 Replies)
Discussion started by: s ladd
0 Replies
4. Linux
Hi,
I have a doubt..whether the SSL/TLS protocol uses the public key of the web server to encrypt data before sending it.
I knew the browser verifies the public key of the web server using the digital certificate (by verifying the signature of the certificate using trusted authority). whether... (2 Replies)
Discussion started by: chaitus.28
2 Replies
5. Solaris
How do I generate an SSL string in solaris 10? (3 Replies)
Discussion started by: Kjons76
3 Replies
6. UNIX for Dummies Questions & Answers
Hi everyone,
I have a quick/newb question:
I know that a public key is used to encrypt data and a private key is used to decrypt data but who keeps the public/private keys??
Does the Web Server hold both?
Does the Web Server have the public key and does the client have the private key? ... (3 Replies)
Discussion started by: tical00
3 Replies
7. Shell Programming and Scripting
Hello,
I need assistance with creating a shell script to generate SSL Certificate Requests on remote hosts. Below is my stab at this, but I cannot figure out how to pass the requested arguments into the openssl command correctly. I have a major problem with redirecting the "answers" into the... (2 Replies)
Discussion started by: azvelocat
2 Replies
8. Solaris
We are running Apache 1.3 on solaris 8 we have renewed our ssl key with verisign. They have confirmed renewel and new ssl certifcate is appended to the end of the email.
out apache config file has two directives
SSLCertificateFile /export/home/apache/conf/ssl.crt/xxxx.crt
SSLCertificationKeyFile... (2 Replies)
Discussion started by: Tirmazi
2 Replies
9. HP-UX
Hi there,
After setup my apache server, I have using mkcert.sh file to generate a SSL key. But when I tried to start my apache server it is prompted me to enter the pass phrase password, in fact I had entered the same correct password which I provided during the key generation and it give me the... (0 Replies)
Discussion started by: e_jeffhang
0 Replies
SESS_ID(1) OpenSSL SESS_ID(1)
NAME
sess_id - SSL/TLS session handling utility
SYNOPSIS
openssl sess_id [-inform PEM|DER] [-outform PEM|DER] [-in filename] [-out filename] [-text] [-noout] [-context ID]
DESCRIPTION
The sess_id process the encoded version of the SSL session structure and optionally prints out SSL session details (for example the SSL
session master key) in human readable format. Since this is a diagnostic tool that needs some knowledge of the SSL protocol to use prop-
erly, most users will not need to use it.
-inform DER|PEM
This specifies the input format. The DER option uses an ASN1 DER encoded format containing session details. The precise format can vary
from one version to the next. The PEM form is the default format: it consists of the DER format base64 encoded with additional header
and footer lines.
-outform DER|PEM
This specifies the output format, the options have the same meaning as the -inform option.
-in filename
This specifies the input filename to read session information from or standard input by default.
-out filename
This specifies the output filename to write session information to or standard output if this option is not specified.
-text
prints out the various public or private key components in plain text in addition to the encoded version.
-cert
if a certificate is present in the session it will be output using this option, if the -text option is also present then it will be
printed out in text form.
-noout
this option prevents output of the encoded version of the session.
-context ID
this option can set the session id so the output session information uses the supplied ID. The ID can be any string of characters. This
option wont normally be used.
OUTPUT
Typical output:
SSL-Session:
Protocol : TLSv1
Cipher : 0016
Session-ID: 871E62626C554CE95488823752CBD5F3673A3EF3DCE9C67BD916C809914B40ED
Session-ID-ctx: 01000000
Master-Key: A7CEFC571974BE02CAC305269DC59F76EA9F0B180CB6642697A68251F2D2BB57E51DBBB4C7885573192AE9AEE220FACD
Key-Arg : None
Start Time: 948459261
Timeout : 300 (sec)
Verify return code 0 (ok)
Theses are described below in more detail.
Protocol
this is the protocol in use TLSv1, SSLv3 or SSLv2.
Cipher
the cipher used this is the actual raw SSL or TLS cipher code, see the SSL or TLS specifications for more information.
Session-ID
the SSL session ID in hex format.
Session-ID-ctx
the session ID context in hex format.
Master-Key
this is the SSL session master key.
Key-Arg
the key argument, this is only used in SSL v2.
Start Time
this is the session start time represented as an integer in standard Unix format.
Timeout
the timeout in seconds.
Verify return code
this is the return code when an SSL client certificate is verified.
NOTES
The PEM encoded session format uses the header and footer lines:
-----BEGIN SSL SESSION PARAMETERS-----
-----END SSL SESSION PARAMETERS-----
Since the SSL session output contains the master key it is possible to read the contents of an encrypted session using this information.
Therefore appropriate security precautions should be taken if the information is being output by a "real" application. This is however
strongly discouraged and should only be used for debugging purposes.
BUGS
The cipher and start time should be printed out in human readable form.
SEE ALSO
ciphers(1), s_server(1)
0.9.7a 2000-02-03 SESS_ID(1)