Home
last modified time | relevance | path

Searched refs:tickets (Results 1 – 25 of 46) sorted by relevance

12

/freebsd-13-stable/crypto/openssl/doc/man3/
HDSSL_CTX_set_num_tickets.pod9 - control the number of TLSv1.3 session tickets that are issued
23 application and set the number of TLSv1.3 session tickets that will be sent to
28 The default number of tickets is 2. Following a resumption the number of tickets
31 0 then no tickets will be issued for either a normal connection or a resumption.
35 L<SSL_verify_client_post_handshake(3)>. These new tickets will be associated
37 verification status). The number of tickets issued will normally be the same as
40 SSL_verify_client_post_handshake() to update the number of tickets that will be
44 tickets set by a previous call to SSL_CTX_set_num_tickets() or
52 SSL_CTX_get_num_tickets() and SSL_get_num_tickets() return the number of tickets
HDSSL_CTX_set_options.pod149 session tickets.
156 When using stateless session tickets the server uses a session ticket encryption
163 The TLSv1.3 protocol only supports tickets and does not directly support session
165 and stateless. Stateless tickets work the same way as in TLSv1.2 and below.
166 Stateful tickets mimic the session id behaviour available in TLSv1.2 and below.
169 presents a ticket in the same way as for stateless tickets. The server can then
173 By default OpenSSL will use stateless tickets. The SSL_OP_NO_TICKET option will
174 cause stateless tickets to not be issued. In TLSv1.2 and below this means no
178 In TLSv1.3 it is possible to suppress all tickets (stateful and stateless) from
HDSSL_CTX_set_timeout.pod46 tickets. It is also used as the timeout value within the ticket itself.
51 For TLSv1.2, tickets generated during an initial handshake use the value
HDSSL_CTX_set_tlsext_ticket_key_cb.pod19 session tickets for the ssl context I<sslctx>. Session tickets, defined in
43 For new sessions tickets, when the client doesn't present a session ticket, or
HDSSL_CTX_set_session_ticket_cb.pod52 tickets. It can be called at any time before a session ticket is created to
54 and tickets are created by the handshake, the B<gen_cb> is provided to notify
HDSSL_get_session.pod43 sent, or if no session tickets were sent then the session for the current
HDSSL_CTX_set_security_level.pod95 tickets are disabled.
/freebsd-13-stable/crypto/heimdal/lib/krb5/
HDget_for_creds.c267 ALLOC_SEQ(&cred.tickets, 1); in krb5_get_forwarded_creds()
268 if (cred.tickets.val == NULL) { in krb5_get_forwarded_creds()
275 cred.tickets.val, &len); in krb5_get_forwarded_creds()
HDget_cred.c982 krb5_creds **tickets; in get_cred_kdc_referral() local
1019 tickets = *ret_tgts; in get_cred_kdc_referral()
1024 while(tickets && *tickets){ in get_cred_kdc_referral()
1028 *tickets)) in get_cred_kdc_referral()
1038 tickets++; in get_cred_kdc_referral()
HDkrb_err.et51 ec INTK_W_NOTALL, "Kerberos 4: not all tickets returned"
HDrd_cred.c271 &cred.tickets.val[i], &len, ret); in krb5_rd_cred()
HDdigest.c787 Ticket **tickets) in krb5_digest_get_tickets() argument
789 *tickets = NULL; in krb5_digest_get_tickets()
/freebsd-13-stable/crypto/heimdal/lib/asn1/
HDdigest.asn163 tickets [1] SEQUENCE OF OCTET STRING OPTIONAL,
100 tickets [3] SEQUENCE OF OCTET STRING OPTIONAL
HDkrb5.asn1463 additional-tickets[11] SEQUENCE OF Ticket OPTIONAL
579 tickets[2] SEQUENCE OF Ticket,
/freebsd-13-stable/crypto/heimdal/appl/login/
HDChangeLog45 v4 authentication or done a 5to4 conversion of tickets. This is to
144 decide whether to get kerberos 4 tickets
202 * login.c: allow conversion of v5 -> v4 tickets when logging in
203 with forwarded tickets
/freebsd-13-stable/crypto/heimdal/kuser/
HDkcc-commands.in37 help = "List kerberos tickets"
54 help = "test for having tickets"
HDkdigest-commands.in179 help = "Where the the credential cache is created when the KDC returns tickets"
/freebsd-13-stable/crypto/heimdal/
HDNEWS375 * kdc: stop clients from renewing tickets into the future
635 * login will get v4 tickets when it receives forwarded tickets
651 * klist supports listing v4 tickets
657 * support for anonymous tickets
724 tickets)
876 * kgetcred: new program for explicitly obtaining tickets
890 * postdated tickets work
HDChangeLog.2006858 * kuser/Makefile.am: Add tool for printing tickets.
860 * kuser/kimpersonate.1: Add tool for printing tickets.
862 * kuser/kimpersonate.c: Add tool for printing tickets.
891 * kdc/kerberos5.c: Signing outgoing tickets.
893 * kdc/krb5tgs.c: Add signing and checking of tickets to s4u2self
944 used to control the address-lessness of the initial tickets
1079 * lib/krb5/krb5_locl.h: Default to address-less tickets.
1231 * lib/krb5/get_cred.c: Allow setting additional tickets in the
/freebsd-13-stable/crypto/heimdal/doc/
HDmisc.texi43 To make the Heimdal KDC produce tickets that the Cisco can decode you
HDapps.texi246 To differentiate between Kerberos 4 tickets and Kerberos 5 tickets, 2b
HDsetup.texi734 authenticate to a server in @samp{OTHER.REALM}? Having valid tickets in
744 service tickets from the Kerberos server in the other realm.
1202 The easiest way to get tickets for a service is to store the key in a
1228 expiration time of the tickets. kinit can run in a mode that refreshes
1229 the tickets before they expire. This is useful for services that write
1313 allowed to get tickets.
1411 use kinit to get yourself tickets. For example:
HDwhatis.texi64 In Kerberos, principals use @dfn{tickets} to prove that they are who
/freebsd-13-stable/crypto/heimdal/lib/hdb/
HDhdb.asn146 trusted-for-delegation(14), -- Trusted to print forwardabled tickets
/freebsd-13-stable/contrib/elftoolchain/
HDREADME.rst111 .. _`bug tracker`: https://sourceforge.net/p/elftoolchain/tickets/

12