Sponsored Content
Full Discussion: SSL certificate
Special Forums Cybersecurity SSL certificate Post 302485144 by majid.merkava on Tuesday 4th of January 2011 11:20:05 AM
Old 01-04-2011
SSL certificate

Hi guys.

I have some questions about ssl certificates.
I looked at SSL providers and saw that they are providing 2 types of certificates: per server or per domain.

my server host name is: srv1.example.com
I have a smtp, imap, web server on this box. but all services accessed by different FQDN:
smtp.example.com
imap.example.com
webmail.example.com

1. I have a single certificate(per server). can i use that for multiple services on a single machine? for example web server and mail server.

2. when creating certificate request it asks me the host name. can i use "smtp.example.com" instead of "srv1.example.com"?
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Installing an SSL certificate in Blue Quartz

My current SSL certificate is about to expire in a couple days so I got a new one via Godaddy and need to install the new one. My server is running Centos 4.x with Blue quartz as the backend. Now BQ does have an SSL import option via the GUI but I'm not sure what route to take to import the... (1 Reply)
Discussion started by: mcraul
1 Replies

2. Web Development

SSL Certificate Installation problem

Hello everybody Hope somebody can help me I'm trying to install SSL Certificate on Apache/mod_ssl on Linux with Zend for Oracle. I bought and downloaded certificate from certificate from Network Solutions. Than I followed the instructions to the dot. I created a directory for certificate... (2 Replies)
Discussion started by: Trusevich
2 Replies

3. Web Development

SSL certificate

Dear All Anyone know how to issue two different certification on apache virtualhost fyi i have one virtualhost eg 69.192.1.25:443 already signed with verisign how can i configure another virtualhost 69.192.1.25:443 which signing with another certificate which self signing. i search net not... (1 Reply)
Discussion started by: netxus
1 Replies

4. AIX

Installing SSL certificate on AIX

Hello, I am new in UNIX, and some one asks me to install SSL certificates to allow exchange with an external system. Can someone tell how to install certificate (ex : verisignxxx.cer) on a UNIX server? Many thanks. Tibo (4 Replies)
Discussion started by: tibo51
4 Replies

5. Web Development

export SSL certificate

we are doing TCP for our systems. I have a working SSL certificate on prodction webserver. Im planning to export it to our DR server for TCP purposes. However when I export based on the procedure below, it doesn't work. When I restart the DR webserver, it still says the certifcate is expired.Any... (1 Reply)
Discussion started by: lhareigh890
1 Replies

6. Red Hat

SSL Certificate Renewal on Tomcat

Hi, I want to renew the ssl certificate for one of my application on tomcat without down time. I want to know what would the possible impacts for the users who currently have sessions to the app. Regards, Arumon (1 Reply)
Discussion started by: arumon
1 Replies

7. Red Hat

SSL certificate generation error 8016

Hi guys, I'm trying to generate a key using the genkey command in centos 6.4 and RHEL6.4, Every thing seems to go cool but I get this error message bad certificate request error -8016 and no key/cert is generated. I don't want use the many openssl(s) commands instead since genkey is a shourtcut... (4 Replies)
Discussion started by: leo_ultra_leo
4 Replies

8. Cybersecurity

SSL Certificate Stores

Hey everyone, I'm trying to get a lay of the land for OS and Application Certificate Stores. Can someone confirm that I have this concept right? If the application you're using say Firefox has it's own trusted CA store, it uses that exclusively. So if you're running firefox in Windows, Firefox... (4 Replies)
Discussion started by: Lost in Cyberia
4 Replies

9. Web Development

CronJobs issues after SSL certificate

Hello! I had a cron job running on my website, activating a php script every friday. The Php script just activated another photo to add in the gallery. It worked fine until I got an SSL certificate for my website, then everything broke. This was the command before: lynx -source... (0 Replies)
Discussion started by: AGDesign
0 Replies
COURIERTLS(1)						      Double Precision, Inc.						     COURIERTLS(1)

NAME
couriertls - the Courier mail server TLS/SSL protocol wrapper SYNOPSIS
couriertls [option...] {program} {arg...} DESCRIPTION
The couriertls program is used by applications to encrypt a network connection using SSL/TLS, without having the application deal with the gory details of SSL/TLS. couriertls is used by the Courier mail server IMAP and ESMTP servers. couriertls is not usually run directly from the commandline. An application typically creates a network connection, then runs couriertls with appropriate options to encrypt the network connection with SSL/TLS. OPTIONS
-host=host, -port=port These options are used instead of -remotefd, mostly for debugging purposes. couriertls connects to the specified server and immediately starts SSL/TLS negotation when the connection is established. -localfd=n Read and write data to encrypt via SSL/TLS from file descriptor n. -statusfd=n Write SSL negotiation status to file descriptor n, then close this file descriptor. If SSL starts succesfully, reading on n gets an immediate EOF. Otherwise, a single line of text - the error message - is read; the file descriptor is closed; and couriertls terminates. -printx509=n Print the x509 certificate on file descriptor n then close it. The x509 certificate is printed before SSL/TLS encryption starts. The application may immediately read the certificate after running couriertls, until the file descriptor is closed. -remotefd=n File descriptor n is the network connection where SSL/TLS encryption is to be used. -server Negotiate server side of the SSL/TLS connection. If this option is not used the client side of the SSL/TLS connection is negotiated. -tcpd couriertls is being called from couriertcpd, and the remote socket is present on descriptors 0 and 1. -tcpd means, basically, the same as -remotefd=0, but couriertls closes file descriptor 1, and redirects file descriptor 1 to file descriptor 2. -verify=domain Verify that domain is set in the CN field of the trusted X.509 certificate presented by the SSL/TLS peer. TLS_TRUSTCERTS must be initialized (see below), and the certificate must be signed by one of the trusted certificates. The CN field can contain a wildcard: CN=*.example will match -verify=foo.example.com. For SSL/TLS clients, TLS_VERIFYPEER must be set to PEER (see below). -protocol=proto Send proto protocol commands before enabling SSL/TLS on the remote connection. proto is either "smtp" or "imap". This is a debugging option that can be used to troubleshoot SSL/TLS with a remote IMAP or SMTP server. If the -remotefd=n option is not specified, the rest of the command line specifies the program to run -- and its arguments -- whose standard input and output is encrypted via SSL/TLS over the network connection. If the program is not specified, the standard input and output of couriertls itself is encrypted. ENVIRONMENT VARIABLES
couriertls reads the following environment variables in order to configure the SSL/TLS protocol: TLS_PROTOCOL=proto Set the protocol version. The possible versions are: SSL2, SSL3, TLS1. TLS_CIPHER_LIST=cipherlist Optionally set the list of protocol ciphers to be used. See OpenSSL's documentation for more information. TLS_TIMEOUT=seconds Currently not implemented, and reserved for future use. This is supposed to be an inactivity timeout, but it's not yet implemented. TLS_DHCERTFILE=filename PEM file that stores our Diffie-Hellman cipher pair. When OpenSSL is compiled to use Diffie-Hellman ciphers instead of RSA you must generate a DH pair that will be used. In most situations the DH pair is to be treated as confidential, and filename must not be world-readable. TLS_CERTFILE=filename The certificate to use. TLS_CERTFILE is required for SSL/TLS servers, and is optional for SSL/TLS clients. filename must not be world-readable. TLS_TRUSTCERTS=pathname Load trusted root certificates from pathname. pathname can be a file or a directory. If a file, the file should contain a list of trusted certificates, in PEM format. If a directory, the directory should contain the trusted certificates, in PEM format, one per file and hashed using OpenSSL's c_rehash script. TLS_TRUSTCERTS is used by SSL/TLS clients (by specifying the -domain option) and by SSL/TLS servers (TLS_VERIFYPEER is set to PEER or REQUIREPEER). TLS_VERIFYPEER=level Whether to verify peer's X.509 certificate. The exact meaning of this option depends upon whether couriertls is used in the client or server mode. In server mode: NONE - do not request an X.509 certificate from the client; PEER - request an optional X.509 certificate from the client, if the client returns one, the SSL/TLS connection is shut down unless the certificate is signed by a trusted certificate authority (see TLS_TRUSTCERTS); REQUIREPEER - same as PEER, except that the SSL/TLS connects is also shut down if the client does not return the optional X.509 certificate. In client mode: NONE - ignore the server's X.509 certificate; PEER - verify the server's X.509 certificate according to the -domain option, (see above). SEE ALSO
couriertcpd(1)[1], courier(8)[2]. AUTHOR
Sam Varshavchik Author NOTES
1. couriertcpd(1) [set $man.base.url.for.relative.links]/couriertcpd.html 2. courier(8) [set $man.base.url.for.relative.links]/courier.html Courier Mail Server 04/04/2011 COURIERTLS(1)
All times are GMT -4. The time now is 07:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy