SSL_get_current_cipher(3SSL) OpenSSL SSL_get_current_cipher(3SSL)NAME
SSL_get_current_cipher, SSL_get_cipher, SSL_get_cipher_name, SSL_get_cipher_bits, SSL_get_cipher_version - get SSL_CIPHER of a connection
SYNOPSIS
#include <openssl/ssl.h>
SSL_CIPHER *SSL_get_current_cipher(const SSL *ssl);
#define SSL_get_cipher(s)
SSL_CIPHER_get_name(SSL_get_current_cipher(s))
#define SSL_get_cipher_name(s)
SSL_CIPHER_get_name(SSL_get_current_cipher(s))
#define SSL_get_cipher_bits(s,np)
SSL_CIPHER_get_bits(SSL_get_current_cipher(s),np)
#define SSL_get_cipher_version(s)
SSL_CIPHER_get_version(SSL_get_current_cipher(s))
DESCRIPTION
SSL_get_current_cipher() returns a pointer to an SSL_CIPHER object containing the description of the actually used cipher of a connection
established with the ssl object.
SSL_get_cipher() and SSL_get_cipher_name() are identical macros to obtain the name of the currently used cipher. SSL_get_cipher_bits() is a
macro to obtain the number of secret/algorithm bits used and SSL_get_cipher_version() returns the protocol name. See
SSL_CIPHER_get_name(3) for more details.
RETURN VALUES
SSL_get_current_cipher() returns the cipher actually used or NULL, when no session has been established.
SEE ALSO ssl(3), SSL_CIPHER_get_name(3)1.0.0e 2005-03-30 SSL_get_current_cipher(3SSL)
Check Out this Related Man Page
SSL_get_current_cipher(3SSL) OpenSSL SSL_get_current_cipher(3SSL)NAME
SSL_get_current_cipher, SSL_get_cipher, SSL_get_cipher_name, SSL_get_cipher_bits, SSL_get_cipher_version - get SSL_CIPHER of a connection
SYNOPSIS
#include <openssl/ssl.h>
SSL_CIPHER *SSL_get_current_cipher(const SSL *ssl);
#define SSL_get_cipher(s)
SSL_CIPHER_get_name(SSL_get_current_cipher(s))
#define SSL_get_cipher_name(s)
SSL_CIPHER_get_name(SSL_get_current_cipher(s))
#define SSL_get_cipher_bits(s,np)
SSL_CIPHER_get_bits(SSL_get_current_cipher(s),np)
#define SSL_get_cipher_version(s)
SSL_CIPHER_get_version(SSL_get_current_cipher(s))
DESCRIPTION
SSL_get_current_cipher() returns a pointer to an SSL_CIPHER object containing the description of the actually used cipher of a connection
established with the ssl object.
SSL_get_cipher() and SSL_get_cipher_name() are identical macros to obtain the name of the currently used cipher. SSL_get_cipher_bits() is a
macro to obtain the number of secret/algorithm bits used and SSL_get_cipher_version() returns the protocol name. See
SSL_CIPHER_get_name(3) for more details.
RETURN VALUES
SSL_get_current_cipher() returns the cipher actually used or NULL, when no session has been established.
SEE ALSO ssl(3), SSL_CIPHER_get_name(3)1.0.1e 2013-02-11 SSL_get_current_cipher(3SSL)
The UNIX and Linux Forums have a number of active members that have published books or papers related to shell programming and scripting. You can check out their publications here:
Link Removed
Please note, as you can imagine, our forum experts can be quite busy! You will get a response... (0 Replies)
Emergency UNIX and Linux Support !! Help Me! Forum (Request Urgent Help)
README FIRST: How to Request Emergency or Urgent Help:
You may post emergency work-related questions in the emergency forum. To post in this forum you will need to use your Bits. All questions answered on a "best... (0 Replies)
Homework Help:
On Posting Questions:
Any and all high school and undergraduate homework assignments or textbook style exercises for which you are seeking assistance are to be posted only in our Homework & Coursework Questions area--not in blogs, visitor messages, PMs, or the main technical... (0 Replies)
Dear Forum Members,
The UNIX and Linux Forums are working directly with the Red Cross to provide ad banners on our site to support Earthquake and Tsunami Relief in Japan. Registered users do not see these banners. However, if you wish to contribute directly on behalf of yourself and the... (8 Replies)
How to Use Code Tags in The UNIX and Linux Forums
Developer: This video tutorial was created by scott for forum users. Everyone should use code tags when posting code and command line logic in the forums.
cPF45jjWe7Q
A full list of BB codes is available here. (8 Replies)
RULES OF THE UNIX AND LINUX FORUMS
For the latest version of the community rules (the official community rules page), please visit here.
No flames, shouting (all caps), sarcasm, bullying, profanity or arrogant posts.
No negative comments about others or impolite remarks. Be patient. No... (1 Reply)
I see lot of ad-hoc shell scripts in our servers which don't have a shebang at the beginning .
Does this mean that it will run on any shell ?
Is it a good practice to create scripts (even ad-hoc ones) without shebang ? (16 Replies)
Having spent a lot of time over the past year taking a legacy vBulletin site (this forum) and making the site responsive on mobile; I've happy with the results; but it will soon be time to move on.
Basically, at our core, we are a LAMP (Linux, Apache2, MySQL and PHP) site, and vBulletin was... (6 Replies)
Here are some answers to some of the recent questions I have received about UNIX.COM. So, I thought I would take time to answer them here in this post:
Is it expected that the original poster "thank" everyone who responds to his / her discussion thread?
It is always a good practice in all... (7 Replies)
By special request, and long overdue, I have updated our "code tags" video and so now we have:
How to Use Code Tags and Format Posts @UNIX.com in 4K
https://youtu.be/4BuPvWJV__k (3 Replies)
Here is a quick EOY report for 2019.
2019 has been a year of "downward trend reversal" for UNIX.com. In fact, if we compare total Google search impressions from the peak days in December 2019 to the peak days in mid December 2018, traffic is up 43% percent. That is a very respectable growth... (0 Replies)