Home
last modified time | relevance | path

Searched refs:cleartext (Results 1 – 25 of 52) sorted by relevance

123

/netbsd/src/crypto/external/bsd/libsaslc/dist/ref/
Drfc2195.txt28 cleartext, reusable passwords across the network nor requires either
48 access to the shared secret in cleartext form. CRAM offers a method
49 for avoiding such cleartext storage while retaining the algorithmic
65 AUTH] is a presumably cleartext username and password, supported
105 of intermediate results make it possible to avoid explicit cleartext
202 Accordingly, a server that implements both a cleartext password
207 marginally better than saving the shared secrets in cleartext as is
222 of permanent cleartext passwords in IMAP. This document has been
Drfc4752.txt191 GSS_Unwrap and interprets the first octet of resulting cleartext as a
195 resulting cleartext is not 4 octets long, the client fails the
310 interpret the first octet of resulting cleartext as the bit-mask for
/netbsd/src/crypto/external/bsd/openssl/dist/test/
Dmodes_internal_test.c194 unsigned char cleartext[64], ciphertext[64], vector[64]; in execute_cts128() local
212 size = fixture->decrypt_block(ciphertext, cleartext, len, in execute_cts128()
216 || !TEST_mem_eq(cleartext, len, test_input, len) in execute_cts128()
232 if (!TEST_size_t_eq(fixture->decrypt_stream(ciphertext, cleartext, len, in execute_cts128()
236 || !TEST_mem_eq(cleartext, len, test_input, len) in execute_cts128()
/netbsd/src/crypto/external/bsd/netpgp/dist/src/netpgp/
Dnetpgp.c256 const int cleartext = 1; in netpgp_cmd() local
298 (p->cmd == CLEARSIGN) ? cleartext : in netpgp_cmd()
299 !cleartext); in netpgp_cmd()
309 (p->cmd == CLEARSIGN) ? cleartext : in netpgp_cmd()
310 !cleartext, in netpgp_cmd()
/netbsd/src/external/bsd/openldap/dist/tests/progs/
Dslapd-bind.c439 … static struct berval cleartext = BER_BVC( "{CLEARTEXT} " ); in do_base() local
446 … if ( ber_bvcmp( &value, &cleartext ) == 0 ) { in do_base()
447 … value.bv_val += cleartext.bv_len; in do_base()
448 … value.bv_len -= cleartext.bv_len; in do_base()
/netbsd/src/crypto/external/bsd/heimdal/dist/lib/hx509/
Dcrypto.c1215 const heim_octet_string *cleartext, in _hx509_public_encrypt() argument
1250 ret = RSA_public_encrypt(cleartext->length, in _hx509_public_encrypt()
1251 (unsigned char *)cleartext->data, in _hx509_public_encrypt()
1281 heim_octet_string *cleartext) in hx509_private_key_private_decrypt() argument
1285 cleartext->data = NULL; in hx509_private_key_private_decrypt()
1286 cleartext->length = 0; in hx509_private_key_private_decrypt()
1294 cleartext->length = RSA_size(p->private_key.rsa); in hx509_private_key_private_decrypt()
1295 cleartext->data = malloc(cleartext->length); in hx509_private_key_private_decrypt()
1296 if (cleartext->data == NULL) { in hx509_private_key_private_decrypt()
1301 cleartext->data, in hx509_private_key_private_decrypt()
[all …]
Dcert.c1623 heim_octet_string *cleartext) in _hx509_cert_private_decrypt() argument
1625 cleartext->data = NULL; in _hx509_cert_private_decrypt()
1626 cleartext->length = 0; in _hx509_cert_private_decrypt()
1638 cleartext); in _hx509_cert_private_decrypt()
1643 const heim_octet_string *cleartext, in hx509_cert_public_encrypt() argument
1649 cleartext, p->data, in hx509_cert_public_encrypt()
/netbsd/src/crypto/external/bsd/netpgp/dist/bindings/lua/
Dglue.c232 const int cleartext = 1; in l_clearsign_file() local
245 f, __UNCONST(output), armour, cleartext, in l_clearsign_file()
/netbsd/src/crypto/external/bsd/netpgp/dist/src/lib/
Dsignature.c1027 const unsigned cleartext, in pgp_sign_file() argument
1087 if (cleartext) { in pgp_sign_file()
1188 const unsigned cleartext)
1216 ld_type = (cleartext) ? PGP_LDT_TEXT : PGP_LDT_BINARY;
1233 if (cleartext) {
Dnetpgp.c1395 int cleartext, in netpgp_sign_file() argument
1472 (unsigned)armored, (unsigned)cleartext, in netpgp_sign_file()
1526 const unsigned cleartext) in netpgp_sign_memory() argument
1595 hashalg, armored, cleartext); in netpgp_sign_memory()
/netbsd/src/external/bsd/elftosb/dist/bdfiles/
Dcomplex.bd168 section(0xbeef; alignment=32K, cleartext=false) <= binfile2;
217 section ('five'; alignment=8K, cleartext=1, sectionFlags=0x1000) <= binfile1;
/netbsd/src/external/bsd/ppp/dist/
DREADME.MSCHAP8013 Authentication Protocol (CHAP) which avoids storing cleartext
17 the password were stored in cleartext.) The details of the Microsoft
144 A site using only MS-CHAP to authenticate has no need to store cleartext
DREADME.eap-srp16 require the server to keep a cleartext copy of the secret (as in
64 On the EAP SRP-SHA1 client side, access to the cleartext secret is
/netbsd/src/etc/pam.d/
DREADME53 use_mapped_pass: convert cleartext password to a crypto key.
/netbsd/src/external/bsd/openldap/dist/contrib/slapd-modules/passwd/sha2/
DREADME29 in production, as it prints passwords in cleartext).
/netbsd/src/crypto/external/bsd/openssl/lib/libdes/
Ddes.pod162 (cleartext) is encrypted in to the I<output> (ciphertext) using the
165 ciphertext) is decrypted into the I<output> (now cleartext). Input
181 routine cipher-block-chain encrypts the cleartext data pointed to by
/netbsd/src/external/bsd/openldap/dist/doc/guide/admin/
Dsecurity.sdf233 to know the cleartext form. Both forms of {{crypt}} include salt so
246 Although safer than cleartext storage, this is not a very secure
/netbsd/src/crypto/external/bsd/netpgp/dist/ref/
Ddraft-ietf-openpgp-rfc2440bis-12.txt2754 cleartext signatures. Note that PGP 2.x uses BEGIN PGP MESSAGE
2764 particularly important when computing a cleartext signature (see
2812 message. This is used only in cleartext signed messages.
2965 cleartext, this framework is used. (Note that RFC 3156 defines
2966 another way to sign cleartext messages for environments that support
2973 The cleartext signed message consists of:
2975 - The cleartext header '-----BEGIN PGP SIGNED MESSAGE-----' on a
2982 - The dash-escaped cleartext that is included into the message
3001 The cleartext content of the message must also be dash-escaped.
3003 Dash escaped cleartext is the ordinary cleartext where every line
[all …]
Ddraft-ietf-openpgp-rfc2440bis-12-ben.txt2738 cleartext signatures. Note that PGP 2.x uses BEGIN PGP MESSAGE
2748 particularly important when computing a cleartext signature (see
2796 message. This is used only in cleartext signed messages.
2949 cleartext, this framework is used. (Note that RFC 3156 defines
2950 another way to sign cleartext messages for environments that support
2957 The cleartext signed message consists of:
2959 - The cleartext header '-----BEGIN PGP SIGNED MESSAGE-----' on a
2966 - The dash-escaped cleartext that is included into the message
2985 The cleartext content of the message must also be dash-escaped.
2987 Dash escaped cleartext is the ordinary cleartext where every line
[all …]
Ddraft-ietf-openpgp-rfc2440bis-15.txt2769 cleartext signatures. Note that PGP 2.x uses BEGIN PGP MESSAGE
2779 particularly important when computing a cleartext signature (see
2825 message. This is used only in cleartext signed messages.
2978 cleartext, this framework is used. (Note that RFC 3156 defines
2979 another way to sign cleartext messages for environments that support
2982 The cleartext signed message consists of:
2984 - The cleartext header '-----BEGIN PGP SIGNED MESSAGE-----' on a
2991 - The dash-escaped cleartext that is included into the message
3010 The cleartext content of the message must also be dash-escaped.
3012 Dash escaped cleartext is the ordinary cleartext where every line
[all …]
Ddraft-ietf-openpgp-rfc2440bis-14.txt2769 cleartext signatures. Note that PGP 2.x uses BEGIN PGP MESSAGE
2779 particularly important when computing a cleartext signature (see
2825 message. This is used only in cleartext signed messages.
2978 cleartext, this framework is used. (Note that RFC 3156 defines
2979 another way to sign cleartext messages for environments that support
2982 The cleartext signed message consists of:
2984 - The cleartext header '-----BEGIN PGP SIGNED MESSAGE-----' on a
2991 - The dash-escaped cleartext that is included into the message
3010 The cleartext content of the message must also be dash-escaped.
3012 Dash escaped cleartext is the ordinary cleartext where every line
[all …]
Ddraft-ietf-openpgp-rfc2440bis-13.txt2769 cleartext signatures. Note that PGP 2.x uses BEGIN PGP MESSAGE
2779 particularly important when computing a cleartext signature (see
2825 message. This is used only in cleartext signed messages.
2972 cleartext, this framework is used. (Note that RFC 3156 defines
2973 another way to sign cleartext messages for environments that support
2976 The cleartext signed message consists of:
2978 - The cleartext header '-----BEGIN PGP SIGNED MESSAGE-----' on a
2985 - The dash-escaped cleartext that is included into the message
3004 The cleartext content of the message must also be dash-escaped.
3006 Dash escaped cleartext is the ordinary cleartext where every line
[all …]
Drfc4880.txt3051 cleartext signatures. Note that PGP 2.x uses BEGIN PGP MESSAGE
3061 is particularly important when computing a cleartext signature (see
3119 message. This is used only in cleartext signed messages.
3298 such a cleartext, this framework is used. (Note that this framework
3300 way to sign cleartext messages for environments that support MIME.)
3311 The cleartext signed message consists of:
3313 - The cleartext header '-----BEGIN PGP SIGNED MESSAGE-----' on a
3320 - The dash-escaped cleartext that is included into the message
3336 An implementation SHOULD add a line break after the cleartext, but
3337 MAY omit it if the cleartext ends with a line break. This is for
[all …]
Ddraft-ietf-openpgp-rfc2440bis-22.txt2922 cleartext signatures. Note that PGP 2.x uses BEGIN PGP MESSAGE
2932 is particularly important when computing a cleartext signature (see
2987 message. This is used only in cleartext signed messages.
3133 such a cleartext, this framework is used. (Note that this framework
3139 sign cleartext messages for environments that support MIME.)
3141 The cleartext signed message consists of:
3143 - The cleartext header '-----BEGIN PGP SIGNED MESSAGE-----' on a
3150 - The dash-escaped cleartext that is included into the message
3167 An implementation SHOULD add a line break after the cleartext, but
3168 MAY omit it if the cleartext ends with a line break. This is for
[all …]
Drfc2440.txt2600 special software. In order to bind a signature to such a cleartext,
2604 The cleartext signed message consists of:
2606 - The cleartext header '-----BEGIN PGP SIGNED MESSAGE-----' on a
2613 - The dash-escaped cleartext that is included into the message
2630 The cleartext content of the message must also be dash-escaped.
2639 Dash escaped cleartext is the ordinary cleartext where every line
2642 recognizing armor headers of the cleartext itself. The message digest
2643 is computed using the cleartext itself, not the dash escaped form.
2645 As with binary signatures on text documents, a cleartext signature is
2652 any line is ignored when the cleartext signature is calculated.

123