| /freebsd/crypto/openssl/test/ssl-tests/ |
| H A D | 06-sni-ticket.cnf | 5 test-0 = 0-sni-session-ticket
6 test-1 = 1-sni-session-ticket
7 test-2 = 2-sni-session-ticket
8 test-3 = 3-sni-session-ticket
9 test-4 = 4-sni-session-ticket
10 test-5 = 5-sni-session-ticket
11 test-6 = 6-sni-session-ticket
12 test-7 = 7-sni-session-ticket
13 test-8 = 8-sni-session-ticket
14 test-9 = 9-sni-session-ticket
[all …]
|
| H A D | 27-ticket-appdata.cnf | 5 test-0 = 0-session-ticket-app-data12
6 test-1 = 1-session-ticket-app-data12
7 test-2 = 2-session-ticket-app-data13
8 test-3 = 3-session-ticket-app-data13
11 [0-session-ticket-app-data12]
12 ssl_conf = 0-session-ticket-app-data12-ssl
14 [0-session-ticket-app-data12-ssl]
15 server = 0-session-ticket-app-data12-server
16 client = 0-session-ticket-app-data12-client
17 resume-server = 0-session-ticket-app-data12-server
[all …]
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | SSL_CTX_set_session_cache_mode.pod | 5 SSL_CTX_set_session_cache_mode, SSL_CTX_get_session_cache_mode - enable/disable session caching
16 SSL_CTX_set_session_cache_mode() enables/disables session caching
28 In order to reuse a session, a client must send the session's id to the
30 agrees to reuse the session or it starts a full handshake (to create a new
31 session).
33 A server will look up the session in its internal session storage. If the
34 session is not found in internal storage or lookups for the internal storage
38 Since a client may try to reuse a session intended for use in a different
39 context, the session id context must be set by the server (see
42 The following session cache modes and modifiers are available:
[all …]
|
| H A D | SSL_CTX_set_generate_session_id.pod | 7 - manipulate generation of SSL session IDs (server only)
24 new session ids for SSL/TLS sessions for B<ctx> to be B<cb>.
27 new session ids for SSL/TLS sessions for B<ssl> to be B<cb>.
29 SSL_has_matching_session_id() checks, whether a session with id B<id>
30 (of length B<id_len>) is already contained in the internal session cache
35 When a new session is established between client and server, the server
36 generates a session id. The session id is an arbitrary sequence of bytes.
37 The length of the session id is between 1 and 32 bytes. The session id is not
38 security critical but must be unique for the server. Additionally, the session id is
39 transmitted in the clear when reusing the session so it must not contain
[all …]
|
| H A D | SSL_CTX_sess_set_get_cb.pod | 5 …e_cb, SSL_CTX_sess_get_get_cb - provide callback functions for server side external session caching
32 called whenever a new session was negotiated.
35 called whenever a session is removed by the SSL engine. For example,
36 this can occur because a session is considered faulty or has become obsolete
40 whenever a TLS client proposed to resume a session but the session
41 could not be found in the internal session cache (see
52 In order to allow external session caching, synchronization with the internal
53 session cache is realized via callback functions. Inside these callback
54 functions, session can be saved to disk or put into a database using the
57 The new_session_cb() is called whenever a new session has been negotiated and
[all …]
|
| H A D | SSL_get_session.pod | 5 SSL_get_session, SSL_get0_session, SSL_get1_session - retrieve TLS/SSL session data
28 The ssl session contains all information required to re-establish the
31 main handshake has occurred. The server will send the session information to the
34 in TLSv1.3 before the session has been established will still return an
35 SSL_SESSION object but that object cannot be used for resuming the session. See
40 session for a single connection. In that case, on the client side, the above
41 functions will only return information on the last session that was received. On
42 the server side they will only return information on the last session that was
43 sent, or if no session tickets were sent then the session for the current
47 to use a new session callback as described in L<SSL_CTX_sess_set_new_cb(3)>.
[all …]
|
| H A D | SSL_CTX_add_session.pod | 5 SSL_CTX_add_session, SSL_CTX_remove_session - manipulate session cache
17 SSL_CTX_add_session() adds the session B<c> to the context B<ctx>. The
18 reference count for session B<c> is incremented by 1. If a session with
19 the same session id already exists, the old session is removed by calling
22 SSL_CTX_remove_session() removes the session B<c> from the context B<ctx> and
27 When adding a new session to the internal session cache, it is examined
28 whether a session with the same session id already exists. In this case
29 it is assumed that both sessions are identical. If the same session is
30 stored in a different SSL_SESSION object, The old session is
31 removed and replaced by the new session. If the session is actually
[all …]
|
| H A D | SSL_CTX_set_session_id_context.pod | 5 SSL_CTX_set_session_id_context, SSL_set_session_id_context - set context within which session can b…
19 B<sid_ctx_len> within which a session can be reused for the B<ctx> object.
22 B<sid_ctx_len> within which a session can be reused for the B<ssl> object.
28 to re-import a session generated from another context (e.g. another
30 must set its own session id context B<sid_ctx> which is used to distinguish
36 The session id context becomes part of the session. The session id context
41 OpenSSL clients will check the session id context returned by the server
42 when reusing a session.
49 If the session id context is not set on an SSL/TLS server and client
54 If a server returns a different session id context to an OpenSSL client
[all …]
|
| H A D | SSL_CTX_set_tlsext_ticket_key_cb.pod | 7 - set a callback for session ticket processing
30 session tickets for the ssl context I<sslctx>. Session tickets, defined in
31 RFC5077 provide an enhanced session resumption capability where the server
32 implementation is not required to maintain per session state. It only applies
36 session when session ticket extension is presented in the TLS hello
41 ticket construction state according to RFC5077 Section 4 such that per session
45 In order to reuse a session, a TLS client must send the session ticket
46 extension to the server. The client must send exactly one session ticket.
47 The server, through the callback function, either agrees to reuse the session
48 ticket information or it starts a full TLS handshake to create a new session
[all …]
|
| H A D | SSL_set_session.pod | 5 SSL_set_session - set a TLS/SSL session to be used during TLS/SSL connect
11 int SSL_set_session(SSL *ssl, SSL_SESSION *session);
15 SSL_set_session() sets B<session> to be used when the TLS/SSL connection
17 When the session is set, the reference count of B<session> is incremented
18 by 1. If the session is not reused, the reference count is decremented
19 again during SSL_connect(). Whether the session was reused can be queried
22 If there is already a session set inside B<ssl> (because it was set with
24 a connection), SSL_SESSION_free() will be called for that session.
25 This is also the case when B<session> is a NULL pointer. If that old
26 session is still B<open>, it is considered bad and will be removed from the
[all …]
|
| H A D | SSL_CTX_set_session_ticket_cb.pod | 9 SSL_CTX_decrypt_session_ticket_fn - manage session ticket application data
32 with a session, and placed into a session ticket. Either callback function may
35 B<gen_cb> is the application defined callback invoked when a session ticket is
37 at this time to add application data to the session ticket. The value of B<arg>
41 B<dec_cb> is the application defined callback invoked after session ticket
42 decryption has been attempted and any session ticket application data is
44 the session data. The B<keyname> and B<keyname_len> arguments identify the key
45 used to decrypt the session ticket. The B<status> argument is the result of the
51 B<data> and B<len> into B<ss> which is then placed into any generated session
52 tickets. It can be called at any time before a session ticket is created to
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | SSL_CTX_set_session_cache_mode.3 | 64 SSL_CTX_set_session_cache_mode, SSL_CTX_get_session_cache_mode \- enable/disable session caching
75 \&\fBSSL_CTX_set_session_cache_mode()\fR enables/disables session caching
86 In order to reuse a session, a client must send the session's id to the
88 agrees to reuse the session or it starts a full handshake (to create a new
89 session).
91 A server will look up the session in its internal session storage. If the
92 session is not found in internal storage or lookups for the internal storage
96 Since a client may try to reuse a session intended for use in a different
97 context, the session id context must be set by the server (see
100 The following session cache modes and modifiers are available:
[all …]
|
| H A D | SSL_CTX_set_generate_session_id.3 | 66 \&\- manipulate generation of SSL session IDs (server only)
83 new session ids for SSL/TLS sessions for \fBctx\fR to be \fBcb\fR.
86 new session ids for SSL/TLS sessions for \fBssl\fR to be \fBcb\fR.
88 \&\fBSSL_has_matching_session_id()\fR checks, whether a session with id \fBid\fR
89 (of length \fBid_len\fR) is already contained in the internal session cache
93 When a new session is established between client and server, the server
94 generates a session id. The session id is an arbitrary sequence of bytes.
95 The length of the session id is between 1 and 32 bytes. The session id is not
96 security critical but must be unique for the server. Additionally, the session id is
97 transmitted in the clear when reusing the session so it must not contain
[all …]
|
| H A D | SSL_CTX_sess_set_get_cb.3 | 64 …_cb, SSL_CTX_sess_get_get_cb \- provide callback functions for server side external session caching
91 called whenever a new session was negotiated.
94 called whenever a session is removed by the SSL engine. For example,
95 this can occur because a session is considered faulty or has become obsolete
99 whenever a TLS client proposed to resume a session but the session
100 could not be found in the internal session cache (see
110 In order to allow external session caching, synchronization with the internal
111 session cache is realized via callback functions. Inside these callback
112 functions, session can be saved to disk or put into a database using the
115 The \fBnew_session_cb()\fR is called whenever a new session has been negotiated and
[all …]
|
| H A D | SSL_get_session.3 | 64 SSL_get_session, SSL_get0_session, SSL_get1_session \- retrieve TLS/SSL session data
86 The ssl session contains all information required to re-establish the
89 main handshake has occurred. The server will send the session information to the
92 in TLSv1.3 before the session has been established will still return an
93 SSL_SESSION object but that object cannot be used for resuming the session. See
98 session for a single connection. In that case, on the client side, the above
99 functions will only return information on the last session that was received. On
100 the server side they will only return information on the last session that was
101 sent, or if no session tickets were sent then the session for the current
105 to use a new session callback as described in \fBSSL_CTX_sess_set_new_cb\fR\|(3).
[all …]
|
| H A D | SSL_CTX_set_tlsext_ticket_key_cb.3 | 66 \&\- set a callback for session ticket processing
91 session tickets for the ssl context \fIsslctx\fR. Session tickets, defined in
92 RFC5077 provide an enhanced session resumption capability where the server
93 implementation is not required to maintain per session state. It only applies
97 session when session ticket extension is presented in the TLS hello
102 ticket construction state according to RFC5077 Section 4 such that per session
106 In order to reuse a session, a TLS client must send the session ticket
107 extension to the server. The client must send exactly one session ticket.
108 The server, through the callback function, either agrees to reuse the session
109 ticket information or it starts a full TLS handshake to create a new session
[all …]
|
| H A D | SSL_CTX_add_session.3 | 64 SSL_CTX_add_session, SSL_CTX_remove_session \- manipulate session cache
76 \&\fBSSL_CTX_add_session()\fR adds the session \fBc\fR to the context \fBctx\fR. The
77 reference count for session \fBc\fR is incremented by 1. If a session with
78 the same session id already exists, the old session is removed by calling
81 \&\fBSSL_CTX_remove_session()\fR removes the session \fBc\fR from the context \fBctx\fR and
85 When adding a new session to the internal session cache, it is examined
86 whether a session with the same session id already exists. In this case
87 it is assumed that both sessions are identical. If the same session is
88 stored in a different SSL_SESSION object, The old session is
89 removed and replaced by the new session. If the session is actually
[all …]
|
| /freebsd/crypto/openssl/test/recipes/ |
| H A D | 70-test_tlsextms.t | 70 # Test 3: same as 1 but with session tickets disabled.
79 # Test 4: same as 2 but with session tickets disabled.
88 #Test 5: Session resumption extended master secret test
95 (undef, my $session) = tempfile();
97 $proxy->clientflags("-no_tls1_3 -sess_out ".$session);
100 $proxy->clientflags("-no_tls1_3 -sess_in ".$session);
102 checkmessages(5, "Session resumption extended master secret test", 1, 1, 0);
103 unlink $session;
105 #Test 6: Session resumption extended master secret test original session
106 # omits extension. Server must not resume session.
[all …]
|
| H A D | 70-test_sslsessiontick.t | 46 #Test 1: By default with no existing session we should get a session ticket
52 checkmessages(1, "Default session ticket test", 1, 1, 1, 1);
55 #with no session tickets
62 checkmessages(2, "No server support session ticket test", 1, 0, 0, 1);
65 #with no session tickets
71 checkmessages(3, "No client support session ticket test", 0, 0, 0, 1);
73 #Test 4: Test session resumption with session ticket
77 (undef, my $session) = tempfile();
79 $proxy->clientflags("-no_tls1_3 -sess_out ".$session);
82 $proxy->clientflags("-no_tls1_3 -sess_in ".$session);
[all …]
|
| /freebsd/sys/dev/qat/qat_api/common/crypto/sym/include/ |
| H A D | lac_session.h | 8 * @defgroup LacSym_Session Session
12 * Definition of symmetric session descriptor structure
17 * A session is required for each symmetric operation. The session descriptor
18 * holds information about the session from when the session is initialised to
19 * when the session is removed. The session descriptor is used in the
21 * receiving the response. The session descriptor and any other state
26 * The user allocates the memory for the session using the size returned from
29 * the first bytes (size of void *) of the session memory. This address
30 * is then dereferenced in subsequent performs to get access to the session
33 * <b>LAC Session Init</b>\n The session descriptor is re-aligned and
[all …]
|
| /freebsd/secure/usr.bin/openssl/man/ |
| H A D | openssl-sess_id.1 | 64 openssl\-sess_id \- SSL/TLS session handling command
79 This command processes the encoded version of the SSL session
80 structure and optionally prints out SSL session details (for example
81 the SSL session master key) in human readable format. Since this is a
97 For \fBNSS\fR output, the session ID and master key are reported in NSS "keylog"
101 This specifies the input filename to read session information from or standard
105 This specifies the output filename to write session information to or standard
113 If a certificate is present in the session it will be output using this option,
117 This option prevents output of the encoded version of the session.
120 This option can set the session id so the output session information uses the
[all …]
|
| /freebsd/crypto/openssl/doc/man1/ |
| H A D | openssl-sess_id.pod.in | 6 openssl-sess_id - SSL/TLS session handling command
23 This command processes the encoded version of the SSL session
24 structure and optionally prints out SSL session details (for example
25 the SSL session master key) in human readable format. Since this is a
45 For B<NSS> output, the session ID and master key are reported in NSS "keylog"
50 This specifies the input filename to read session information from or standard
55 This specifies the output filename to write session information to or standard
65 If a certificate is present in the session it will be output using this option,
70 This option prevents output of the encoded version of the session.
74 This option can set the session id so the output session information uses the
[all …]
|
| /freebsd/sys/opencrypto/ |
| H A D | cryptodev_if.m | 42 * @brief Probe to see if a crypto driver supports a session.
45 * creating a session for symmetric crypto operations to determine if
47 * session.
49 * If the driver does not support a session with the requested
52 * If the driver does support a session with the requested parameters,
63 * @param csp crypto session parameters
65 * @retval negative if the driver supports this session - the
67 * driver for the session
68 * @retval EINVAL if the driver does not support the session
77 * @brief Initialize a new crypto session object
[all …]
|
| /freebsd/crypto/heimdal/doc/doxyout/ntlm/man/man3/ |
| H A D | ntlm_core.3 | 46 .RI "int \fBheim_ntlm_build_ntlm1_master\fP (void *key, size_t len, struct \fBntlm_buf\fP *session,…
49 …id *key, size_t len, struct \fBntlm_buf\fP *blob, struct \fBntlm_buf\fP *session, struct \fBntlm_b…
52 … \fBntlm_buf\fP *baseKey, struct \fBntlm_buf\fP *encryptedSession, struct \fBntlm_buf\fP *session)"
72 .SS "int heim_ntlm_build_ntlm1_master (void * key, size_t len, struct \fBntlm_buf\fP * session, str…
74 Generates an NTLMv1 session random with assosited session master key.
82 \fIsession\fP generated session nonce, should be freed with \fBheim_ntlm_free_buf()\fP.
84 \fImaster\fP calculated session master key, should be freed with \fBheim_ntlm_free_buf()\fP.
93 …* key, size_t len, struct \fBntlm_buf\fP * blob, struct \fBntlm_buf\fP * session, struct \fBntlm_b…
95 Generates an NTLMv2 session random with associated session master key.
105 \fIsession\fP generated session nonce, should be freed with \fBheim_ntlm_free_buf()\fP.
[all …]
|
| /freebsd/contrib/llvm-project/llvm/lib/DebugInfo/PDB/Native/ |
| H A D | NativeExeSymbol.cpp | 23 static DbiStream *getDbiStreamPtr(NativeSession &Session) { in getDbiStreamPtr() argument
24 Expected<DbiStream &> DbiS = Session.getPDBFile().getPDBDbiStream(); in getDbiStreamPtr()
32 NativeExeSymbol::NativeExeSymbol(NativeSession &Session, SymIndexId SymbolId) in NativeExeSymbol() argument
33 : NativeRawSymbol(Session, PDB_SymType::Exe, SymbolId), in NativeExeSymbol()
34 Dbi(getDbiStreamPtr(Session)) {} in NativeExeSymbol()
40 return std::unique_ptr<IPDBEnumSymbols>(new NativeEnumModules(Session)); in findChildren()
44 return Session.getSymbolCache().createTypeEnumerator(codeview::LF_ARRAY); in findChildren()
46 return Session.getSymbolCache().createTypeEnumerator(codeview::LF_ENUM); in findChildren()
48 return Session.getSymbolCache().createTypeEnumerator(codeview::LF_POINTER); in findChildren()
50 return Session.getSymbolCache().createTypeEnumerator( in findChildren()
[all …]
|