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)
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)
Hi guys, Those who work on Apache may help me on this.
I have following problem
Description:
The remote service encrypts traffic using TLS / SSL and permits clients to renegotiate
connections. The computational requirements for renegotiating a connection are
asymmetrical between the... (3 Replies)
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)
hi guys
I configured my openldap but now I want to implement SSL-TLS
This is my basic slapd.conf configuration
include /etc/openldap/schema/core.schema
include /etc/openldap/schema/cosine.schema
include /etc/openldap/schema/inetorgperson.schema
include ... (2 Replies)
We have a requirement to setup secure ftp between our AIX v5.3 system and
our mainframe. We don't want to use openssh with sftp and scp. Our mainframe uses ftp over ssl/tls so we have to use this on our AIX box. We have openssl on our AIX system but I'm not sure how to setup ssl/tls over ftp
on... (4 Replies)
SSL_accept(3) OpenSSL SSL_accept(3)NAME
SSL_accept - wait for a TLS/SSL client to initiate a TLS/SSL handshake
SYNOPSIS
#include <openssl/ssl.h>
int SSL_accept(SSL *ssl);
DESCRIPTION
SSL_accept() waits for a TLS/SSL client to initiate the TLS/SSL handshake. The communication channel must already have been set and
assigned to the ssl by setting an underlying BIO.
NOTES
The behaviour of SSL_accept() depends on the underlying BIO.
If the underlying BIO is blocking, SSL_accept() will only return once the handshake has been finished or an error occurred, except for SGC
(Server Gated Cryptography). For SGC, SSL_accept() may return with -1, but SSL_get_error() will yield SSL_ERROR_WANT_READ/WRITE and
SSL_accept() should be called again.
If the underlying BIO is non-blocking, SSL_accept() will also return when the underlying BIO could not satisfy the needs of SSL_accept() 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_accept() 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_accept(). 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:
1. The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been established.
2. 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.
3. <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_connect(3), SSL_shutdown(3), ssl(3), bio(3), SSL_set_connect_state(3), SSL_do_handshake(3), SSL_CTX_new(3)POD ERRORS
Hey! The above document had some coding errors, which are explained below:
Around line 52:
You have '=item 0' instead of the expected '=item 2'
Around line 58:
Expected '=item 3'
50 2013-03-05 SSL_accept(3)
