09-09-2014
Thanks for the reply. This will be only for server-to-server communications, no clients will connect to the Unix box. Does that make a difference? Can you point me to any documentation on this?
Thanks,
Joe
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi. One of my company's customers requires mails to be sent to them to use TLS. Thanks to some good documentation on the web, I've got this mostly figured out, but now I'm stuck at generating the CSR.
My company's mail domain is sg.bunny.com (not real address, obviously), but the email gateway... (0 Replies)
Discussion started by: pierreery
0 Replies
2. Solaris
Hello guys,
I have been trying to set up my DSEE 6.3 on Solaris 10 using proxy with tls:simple authentication. I follow all the steps mentioned in the Installation Guide on Sun's site but there is a problem with ldapclient init when I use hostname instead of IP address in the Default Server... (12 Replies)
Discussion started by: niyazi
12 Replies
3. Cybersecurity
Hey Guys,
I have a couple servers that are getting flagged by by our network security team. How do I disable TLS 1.0 protocol within Solaris? The vulnerability is :
CVE-2011-3389
TLS-SSL Server Blockwise Chosen-Boundary Browser Weakness (2 Replies)
Discussion started by: s ladd
2 Replies
4. UNIX for Advanced & Expert Users
Hello to all,
I'm beguinner in Linux instalations and I'm trying to Communicate from Web Sites that i have running under apache with openLDAP for users authentication using SSL mediation that seems to be connected with LDAPS.
Can someone advise me how to do this, I have already installed... (1 Reply)
Discussion started by: CPMarco
1 Replies
5. UNIX for Advanced & Expert Users
Here are the essentials:
un: myuser
pw: mypasswd
site: sftp.somesite.com
port: 990
type: FTPS
enc: FTP over implicit TLS
program used:
Curl 7.1.x on Hpux 11.31
I would like to "put" 1 file on there server.
Here is my syntax, what am I doing wrong?
curl -3 -v --cacert... (4 Replies)
Discussion started by: olyanderson
4 Replies
6. UNIX for Dummies Questions & Answers
Greetings.
I desperately need help to get my sendmail configuration working again.
I followed this guide:
Unmemorable Memories » Blog Archive » Enabling SMTP-AUTH for Sendmail on Debian Linux 3.1
to enable TLS and AUTH in sendmail and now I get an error I just cannot find any information... (1 Reply)
Discussion started by: Mr.Glaurung
1 Replies
7. AIX
The situation
Version AIX7.1/8.14.4
Compiled with: DNSMAP LDAPMAP LDAP_REFERRALS LOG MAP_REGEX MATCHGECOS
MILTER MIME7TO8 MIME8TO7 NAMED_BIND NDBM NETINET NETINET6
NETUNIX NEWDB NIS NISPLUS PIPELINING SCANF STARTTLS USERDB
USE_LDAP_INIT XDEBUG... (2 Replies)
Discussion started by: Linusolaradm1
2 Replies
8. UNIX for Advanced & Expert Users
:rolleyes:I am trying to setup all certificate based client-server environment in Linux using vsftpd and curl with openssl.
I would like to make a user access with vsftpd certificate and user own client certificate (self-signed) with private/public key.
I don't see google posts about the my plan... (4 Replies)
Discussion started by: gogogo
4 Replies
9. Solaris
We are implementing CUPS on a new Solaris 11.3 system. The same system will run an application where users can print to networked printers inside our organisation, or to a printer outside of our organisation over the internet.
For users printing to internal network printers, no encryption is... (0 Replies)
Discussion started by: SallyB
0 Replies
LEARN ABOUT CENTOS
ssl_connect
SSL_connect(3) OpenSSL SSL_connect(3)
NAME
SSL_connect - initiate the TLS/SSL handshake with an TLS/SSL server
SYNOPSIS
#include <openssl/ssl.h>
int SSL_connect(SSL *ssl);
DESCRIPTION
SSL_connect() initiates the TLS/SSL handshake with a server. The communication channel must already have been set and assigned to the ssl
by setting an underlying BIO.
NOTES
The behaviour of SSL_connect() depends on the underlying BIO.
If the underlying BIO is blocking, SSL_connect() will only return once the handshake has been finished or an error occurred.
If the underlying BIO is non-blocking, SSL_connect() will also return when the underlying BIO could not satisfy the needs of SSL_connect()
to continue the handshake, indicating the problem by the return value -1. In this case a call to SSL_get_error() with the return value of
SSL_connect() will yield SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE. The calling process then must repeat the call after taking
appropriate action to satisfy the needs of SSL_connect(). The action depends on the underlying BIO. When using a non-blocking socket,
nothing is to be done, but select() can be used to check for the required condition. When using a buffering BIO, like a BIO pair, data must
be written into or retrieved out of the BIO before being able to continue.
RETURN VALUES
The following return values can occur:
0 The TLS/SSL handshake was not successful but was shut down controlled and by the specifications of the TLS/SSL protocol. Call
SSL_get_error() with the return value ret to find out the reason.
1 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been established.
<0 The TLS/SSL handshake was not successful, because a fatal error occurred either at the protocol level or a connection failure occurred.
The shutdown was not clean. It can also occur of action is need to continue the operation for non-blocking BIOs. Call SSL_get_error()
with the return value ret to find out the reason.
SEE ALSO
SSL_get_error(3), SSL_accept(3), SSL_shutdown(3), ssl(3), bio(3), SSL_set_connect_state(3), SSL_do_handshake(3), SSL_CTX_new(3)
1.0.1e 2014-06-17 SSL_connect(3)