| /netbsd-src/crypto/external/bsd/heimdal/dist/lib/hx509/ |
| H A D | test_soft_pkcs11.c | 156 CK_MECHANISM mechanism; in main() local 158 memset(&mechanism, 0, sizeof(mechanism)); in main() 159 mechanism.mechanism = CKM_RSA_PKCS; in main() 161 ret = (*func->C_SignInit)(session, &mechanism, private); in main() 173 ret = (*func->C_VerifyInit)(session, &mechanism, public); in main() 188 CK_MECHANISM mechanism; in main() 191 memset(&mechanism, 0, sizeof(mechanism)); in main() 192 mechanism.mechanism = CKM_RSA_PKCS; in main() 194 ret = (*func->C_EncryptInit)(session, &mechanism, public); in main() 206 ret = (*func->C_DecryptInit)(session, &mechanism, private); in main()
|
| H A D | ks_p11.c | 135 CK_MECHANISM mechanism; in p11_rsa_private_encrypt() local 142 memset(&mechanism, 0, sizeof(mechanism)); in p11_rsa_private_encrypt() 143 mechanism.mechanism = CKM_RSA_PKCS; in p11_rsa_private_encrypt() 151 ret = P11FUNC(p11rsa->p, SignInit, (session, &mechanism, key)); in p11_rsa_private_encrypt() 173 CK_MECHANISM mechanism; in p11_rsa_private_decrypt() local 180 memset(&mechanism, 0, sizeof(mechanism)); in p11_rsa_private_decrypt() 181 mechanism.mechanism = CKM_RSA_PKCS; in p11_rsa_private_decrypt() 189 ret = P11FUNC(p11rsa->p, DecryptInit, (session, &mechanism, key)); in p11_rsa_private_decrypt()
|
| /netbsd-src/crypto/external/bsd/libsaslc/dist/ref/ |
| H A D | rfc4422.txt | 39 This document describes how a SASL mechanism is structured, describes 42 document defines one SASL mechanism, the EXTERNAL mechanism. 147 framework allows any protocol to utilize any mechanism. While this 157 form is mechanism specific, and authorization identities, whose form 180 for identifying which mechanism is to be used, a method for exchange 181 of mechanism-specific server-challenges and client-responses, and a 185 Each SASL mechanism defines (amongst other items) a series of 188 SASL mechanism requirements. 191 IANA considerations. Appendix A defines the SASL EXTERNAL mechanism. 200 - mechanism designers that define new SASL mechanisms, and [all …]
|
| H A D | rfc2222.txt | 40 6.1. Comments on SASL mechanism registrations .............. 6 45 7.1. Kerberos version 4 mechanism .......................... 8 46 7.2. GSSAPI mechanism ...................................... 9 50 7.3. S/Key mechanism ....................................... 11 51 7.4. External mechanism .................................... 12 134 The command has a required argument identifying a SASL mechanism. 137 underscores. SASL mechanism names must be registered with the IANA. 141 If a server supports the requested mechanism, it initiates an 144 requested mechanism. The challenges and responses are defined by the 158 During the authentication protocol exchange, the mechanism performs [all …]
|
| H A D | rfc4616.txt | 30 Authentication and Security Layer (SASL) mechanism called the PLAIN 31 mechanism. The PLAIN mechanism is intended to be used, in 68 authentication mechanism. The drawback is that they are unacceptable 73 Layer ([SASL]) mechanism for use in protocols with no clear-text 78 The name associated with this mechanism is "PLAIN". 80 The PLAIN SASL mechanism does not provide a security layer. 82 The PLAIN mechanism should not be used without adequate data security 83 protection as this mechanism affords no integrity or confidentiality 84 protections itself. The mechanism is intended to be used with data 90 PLAIN mechanism only when adequate data security services are in [all …]
|
| H A D | rfc4752.txt | 37 "GSSAPI" SASL mechanism. This document, together with RFC 4422, 83 and Security Layer (SASL [SASL]) mechanism supporting the Kerberos V5 85 ([GSS-API]) mechanism [RFC4121]. The authentication sequence is 106 The SASL mechanism name for the Kerberos V5 GSS-API mechanism 107 [RFC4121] is "GSSAPI". Though known as the SASL GSSAPI mechanism, 108 the mechanism is specifically tied to Kerberos V5 and GSS-API's 109 Kerberos V5 mechanism. 119 The GSSAPI SASL mechanism is a "client goes first" SASL mechanism; 138 GSS-API mechanism [KRB5GSS], chan_binding of NULL, and targ_name 214 A server MUST NOT advertise support for the "GSSAPI" SASL mechanism [all …]
|
| H A D | rfc4505.txt | 31 text password mechanism using "anonymous" as the user name and using 40 This document defines an anonymous mechanism for the Simple 42 associated with this mechanism is "ANONYMOUS". 45 and identify the user to a server, the purpose of this SASL mechanism 48 to the server. That is, this mechanism provides an anonymous login 51 This mechanism does not provide a security layer. 65 The mechanism consists of a single message from the client to the 78 ANONYMOUS mechanism and allow anyone to log in using that mechanism, 188 The ANONYMOUS mechanism grants access to services and/or resources by 197 server can be used as a communication mechanism to exchange [all …]
|
| H A D | rfc2195.txt | 27 described in RFC 1731, it lacks any mechanism that neither passes 39 Existing Proposed Standards specify an AUTHENTICATE mechanism for the 40 IMAP4 protocol [IMAP, IMAP-AUTH] and a parallel AUTH mechanism for 41 the POP3 protocol [POP3-AUTH]. The AUTHENTICATE mechanism is 45 lightweight challenge-response mechanism called APOP. APOP is 67 simple challenge-response mechanism, similar to APOP and PPP CHAP 70 This mechanism also has the advantage over some possible alternatives 119 CRAM does not support a protection mechanism. 123 The examples in this document show the use of the CRAM mechanism with 200 It is conjectured that use of the CRAM authentication mechanism
|
| /netbsd-src/crypto/external/bsd/heimdal/dist/lib/gssapi/ |
| H A D | oid.txt | 76 desc mech GSS_KRB5_MECHANISM "Kerberos 5" "Heimdal Kerberos 5 mechanism" 77 desc mech GSS_NTLM_MECHANISM "NTLM" "Heimdal NTLM mechanism" 78 desc mech GSS_SPNEGO_MECHANISM "SPNEGO" "Heimdal SPNEGO mechanism" 80 desc ma GSS_C_MA_MECH_NAME "GSS mech name" "The name of the GSS-API mechanism" 81 desc ma GSS_C_MA_SASL_MECH_NAME "SASL mechanism name" "The name of the SASL mechanism" 82 desc ma GSS_C_MA_MECH_DESCRIPTION "Mech description" "The long description of the mechanism" 116 …ETE "concrete-mech" "Indicates that a mech is neither a pseudo-mechanism nor a composite mechanism"
|
| /netbsd-src/crypto/external/bsd/libsaslc/dist/test/ |
| H A D | example_client.c | 85 char *mechanism = NULL; in main() local 98 mechanism = optarg; in main() 112 if (mechanism == NULL) { in main() 116 mechanism = input; in main() 124 if ((sess = saslc_sess_init(ctx, mechanism, NULL)) == NULL) in main()
|
| /netbsd-src/crypto/external/bsd/libsaslc/dist/doc/ |
| H A D | library.txt | 15 /etc/saslc/appname.d/mechanism.conf for machanisms which are listed in 30 list of mechanism names. Mechanism used for the authentication is selected 66 to the string contains name of the mechanism used in session. On failure 94 Each mechanism will provide const saslc_mech_t structure describing its 96 type by mechanism is not mandatory and different struct can be defined by a 97 mechanism if necessary. This structure is used only for representing internal 98 state of the mechanism session, and wouldn't be used outside of mechanism 113 Consider ANONYMOUS mechanism as example, its pseudo implementation looks as 143 FLAG_ANONYMOUS, /* mechanism flags */ 144 mech_generic_create; /* create function - creates mechanism [all …]
|
| /netbsd-src/external/bsd/openldap/dist/libraries/libldap/ |
| H A D | vc.c | 205 LDAP_CONST char *mechanism, in ldap_verify_credentials() argument 223 if (mechanism == LDAP_SASL_SIMPLE) { in ldap_verify_credentials() 234 dn, LDAP_AUTH_SASL, mechanism); in ldap_verify_credentials() 237 dn, LDAP_AUTH_SASL, mechanism); in ldap_verify_credentials() 243 dn, LDAP_AUTH_SASL, mechanism, cred); in ldap_verify_credentials() 246 dn, LDAP_AUTH_SASL, mechanism, cred); in ldap_verify_credentials() 300 LDAP_CONST char *mechanism, in ldap_verify_credentials_s() argument 315 rc = ldap_verify_credentials(ld, cookie, dn, mechanism, cred, vcictrls, sctrls, cctrls, &msgid); in ldap_verify_credentials_s()
|
| H A D | sasl.c | 56 LDAP_CONST char *mechanism, in ldap_build_bind_req() argument 65 if( mechanism == LDAP_SASL_SIMPLE ) { in ldap_build_bind_req() 86 if( mechanism == LDAP_SASL_SIMPLE ) { in ldap_build_bind_req() 98 mechanism ); in ldap_build_bind_req() 105 mechanism, cred ); in ldap_build_bind_req() 144 LDAP_CONST char *mechanism, in ldap_sasl_bind() argument 164 ber = ldap_build_bind_req( ld, dn, mechanism, cred, sctrls, cctrls, &id ); in ldap_sasl_bind() 182 LDAP_CONST char *mechanism, in ldap_sasl_bind_s() argument 203 rc = ldap_sasl_bind( ld, dn, mechanism, cred, sctrls, cctrls, &msgid ); in ldap_sasl_bind_s()
|
| /netbsd-src/external/ibm-public/postfix/dist/src/smtp/ |
| H A D | smtp_sasl_glue.c | 318 const char *mechanism; in smtp_sasl_authenticate() local 359 &mechanism, session->sasl_reply); in smtp_sasl_authenticate() 384 && strlen(mechanism) + LEN(session->sasl_reply) + 8 <= 512) { in smtp_sasl_authenticate() 385 smtp_chat_cmd(session, "AUTH %s %s", mechanism, in smtp_sasl_authenticate() 389 smtp_chat_cmd(session, "AUTH %s", mechanism); in smtp_sasl_authenticate() 427 "%s challenge from server %s: %s", mechanism, in smtp_sasl_authenticate()
|
| /netbsd-src/crypto/external/bsd/heimdal/dist/lib/gssapi/krb5/ |
| H A D | inquire_names_for_mech.c | 48 const gss_OID mechanism, in _gsskrb5_inquire_names_for_mech() argument 57 if (gss_oid_equal(mechanism, GSS_KRB5_MECHANISM) == 0 && in _gsskrb5_inquire_names_for_mech() 58 gss_oid_equal(mechanism, GSS_C_NULL_OID) == 0) { in _gsskrb5_inquire_names_for_mech()
|
| /netbsd-src/crypto/external/bsd/heimdal/dist/lib/gssapi/mech/ |
| H A D | gss_inquire_names_for_mech.c | 35 const gss_OID mechanism, in gss_inquire_names_for_mech() argument 39 gssapi_mech_interface m = __gss_get_mechanism(mechanism); in gss_inquire_names_for_mech() 52 mechanism, name_types)); in gss_inquire_names_for_mech()
|
| /netbsd-src/external/bsd/openldap/dist/doc/rfc/ |
| H A D | rfc3673.txt | 29 The Lightweight Directory Access Protocol (LDAP) supports a mechanism 37 X.500 [X.500] provides a mechanism for clients to request all 39 to a search operation. This mechanism is often used by clients to 43 (LDAP) [RFC3377] to provide a simple mechanism which clients may use 44 to request the return of all operational attributes. The mechanism 82 This mechanism is specifically designed to allow users to request all 84 the mechanism is designed to be compatible with existing general 87 The addition of this mechanism to LDAP is not believed to cause any 95 It is also noted that this mechanism is believed to require no 100 This document provides a general mechanism which clients may use to [all …]
|
| H A D | rfc4513.txt | 38 method including the EXTERNAL mechanism. 276 interoperability by identifying a mandatory-to-implement mechanism 360 mechanism of the simple Bind method (Section 5.1.1). 362 LDAP implementations that support any authentication mechanism other 363 than the anonymous authentication mechanism of the simple Bind method 364 MUST support the name/password authentication mechanism of the simple 370 authentication mechanism by default when suitable data security 372 security services for use with this authentication mechanism. 378 authorization identity via the SASL EXTERNAL mechanism (Section 381 LDAP server implementations that support no authentication mechanism [all …]
|
| /netbsd-src/external/bsd/libpcap/dist/testprogs/ |
| H A D | selpolltest.c | 73 const char *mechanism; in main() local 85 mechanism = NULL; in main() 104 mechanism = "select() and pcap_dispatch()"; in main() 109 mechanism = "poll() and pcap_dispatch()"; in main() 173 device, mechanism); in main() 190 mechanism); in main()
|
| /netbsd-src/games/rogue/ |
| H A D | score.c | 69 const char *mechanism = "killed by something unknown (?)"; in killed_by() local 83 mechanism = "died of hypothermia"; in killed_by() 86 mechanism = "died of starvation"; in killed_by() 89 mechanism = "killed by a dart"; in killed_by() 92 mechanism = "quit"; in killed_by() 95 mechanism = "killed by fire"; in killed_by() 107 mechanism = mechanism_buf; in killed_by() 110 "%s with %ld gold", mechanism, rogue.gold); in killed_by()
|
| /netbsd-src/crypto/external/bsd/openssh/dist/ |
| H A D | pkcs11.h | 681 ck_mechanism_type_t mechanism; member 823 struct ck_mechanism *mechanism, 842 struct ck_mechanism *mechanism, 861 struct ck_mechanism *mechanism)); 879 struct ck_mechanism *mechanism, 895 struct ck_mechanism *mechanism, 905 struct ck_mechanism *mechanism, 921 struct ck_mechanism *mechanism, 955 struct ck_mechanism *mechanism, 961 struct ck_mechanism *mechanism, [all …]
|
| /netbsd-src/external/bsd/openldap/dist/doc/guide/admin/ |
| H A D | sasl.sdf | 57 The DIGEST-MD5 mechanism is the mandatory-to-implement authentication 58 mechanism for LDAPv3. Though DIGEST-MD5 is not a strong authentication 59 mechanism in comparison with trusted third party authentication 62 the {{TERM:CRAM-MD5}} mechanism, it prevents chosen plaintext 64 mechanisms. The CRAM-MD5 mechanism is deprecated in favor of 67 The GSSAPI mechanism utilizes {{TERM:GSS-API}} {{TERM:Kerberos}} V 68 to provide secure authentication services. The KERBEROS_V4 mechanism 74 The EXTERNAL mechanism utilizes authentication services provided 99 V4 as an example mechanism. The steps necessary for your site's 100 authentication mechanism will be similar, but a guide to every [all …]
|
| /netbsd-src/external/mpl/dhcp/bind/dist/lib/isc/include/pkcs11/ |
| H A D | pkcs11.h | 892 ck_mechanism_type_t mechanism; member 1114 struct ck_mechanism *mechanism, ck_object_handle_t key)); 1129 struct ck_mechanism *mechanism, ck_object_handle_t key)); 1144 struct ck_mechanism *mechanism)); 1160 struct ck_mechanism *mechanism, ck_object_handle_t key)); 1172 struct ck_mechanism *mechanism, ck_object_handle_t key)); 1180 struct ck_mechanism *mechanism, ck_object_handle_t key)); 1193 struct ck_mechanism *mechanism, ck_object_handle_t key)); 1220 struct ck_mechanism *mechanism, 1225 struct ck_mechanism *mechanism, [all …]
|
| /netbsd-src/crypto/external/bsd/heimdal/dist/lib/hx509/ref/ |
| H A D | pkcs11.h | 868 ck_mechanism_type_t mechanism; member 1139 struct ck_mechanism *mechanism, 1158 struct ck_mechanism *mechanism, 1177 struct ck_mechanism *mechanism)); 1195 struct ck_mechanism *mechanism, 1211 struct ck_mechanism *mechanism, 1221 struct ck_mechanism *mechanism, 1237 struct ck_mechanism *mechanism, 1271 struct ck_mechanism *mechanism, 1277 struct ck_mechanism *mechanism, [all …]
|
| /netbsd-src/external/mpl/bind/dist/bin/plugins/ |
| H A D | filter-a.rst | 47 Note: This mechanism can erroneously cause other servers not to give 50 mechanism via IPv6, it is denied A records even if its client is 72 This mechanism can erroneously cause other servers not to give A 75 mechanism via IPv6, it is denied A records even if its client is
|