Sponsored Content
Operating Systems Solaris Solaris v Ubuntu using OpenSSL paste problem Post 302684393 by bitlord on Thursday 9th of August 2012 02:04:19 PM
Old 08-09-2012
I would look in the man pages. As I said I'm not an expert on ssl. I work on mostly Solaris servers but I also work on RHEL and SUSE servers. Linux will do this differently then Solaris. I can't think of an example at this time.

If your in the ssl prompt the switch should be the same for the most part.
 

2 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

solaris 9 openssl make problem with ld

i've seen a few posts regarding this issue, and i've tried the resolutions, but i keep running into the same problem. i'm trying to compile OpenSSL with the use of rsaref-2.0 (i'm running through this tutorial... (1 Reply)
Discussion started by: xyyz
1 Replies

2. Shell Programming and Scripting

Openssl scripting problem

im trying to make sure the openssl password does not show up in the output of ps. so i'm trying to do something like this: MAST=yup echo "U2FsdGVkX19wH9LrQhuRZes45BM9rfiRpdhTCi+gLls=" | openssl <<HERE 2>&1 >/dev/null aes-128-cbc -a -d -salt -k "${MAST}" HERE But this isn't working.. I... (10 Replies)
Discussion started by: SkySmart
10 Replies
SSL_set_connect_state(3)					      OpenSSL						  SSL_set_connect_state(3)

NAME
SSL_set_connect_state, SSL_get_accept_state - prepare SSL object to work in client or server mode SYNOPSIS
#include <openssl/ssl.h> void SSL_set_connect_state(SSL *ssl); void SSL_set_accept_state(SSL *ssl); DESCRIPTION
SSL_set_connect_state() sets ssl to work in client mode. SSL_set_accept_state() sets ssl to work in server mode. NOTES
When the SSL_CTX object was created with SSL_CTX_new(3), it was either assigned a dedicated client method, a dedicated server method, or a generic method, that can be used for both client and server connections. (The method might have been changed with SSL_CTX_set_ssl_version(3) or SSL_set_ssl_method().) When beginning a new handshake, the SSL engine must know whether it must call the connect (client) or accept (server) routines. Even though it may be clear from the method chosen, whether client or server mode was requested, the handshake routines must be explicitly set. When using the SSL_connect(3) or SSL_accept(3) routines, the correct handshake routines are automatically set. When performing a transparent negotiation using SSL_write(3) or SSL_read(3), the handshake routines must be explicitly set in advance using either SSL_set_connect_state() or SSL_set_accept_state(). RETURN VALUES
SSL_set_connect_state() and SSL_set_accept_state() do not return diagnostic information. SEE ALSO
ssl(3), SSL_new(3), SSL_CTX_new(3), SSL_connect(3), SSL_accept(3), SSL_write(3), SSL_read(3), SSL_do_handshake(3), SSL_CTX_set_ssl_version(3) 1.0.1e 2013-02-11 SSL_set_connect_state(3)
All times are GMT -4. The time now is 05:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy