| /third_party/node/test/parallel/ |
| D | test-tls-securepair-server.js | 51 assert.ok(pair.cleartext.writable);
60 pair.cleartext.write('hello\r\n');
61 log(pair.cleartext.getPeerCertificate());
62 log(pair.cleartext.getCipher());
65 pair.cleartext.on('data', function(data) {
67 pair.cleartext.write(data);
74 pair.cleartext.on('error', function(err) {
|
| D | test-tls-timeout-server-2.js | 36 const server = tls.createServer(options, common.mustCall(function(cleartext) { argument
37 const s = cleartext.setTimeout(50, function() {
38 cleartext.destroy();
|
| D | test-https-timeout-server-2.js | 40 server.on('secureConnection', function(cleartext) { argument
41 const s = cleartext.setTimeout(50, function() {
42 cleartext.destroy();
|
| D | test-tls-ocsp-callback.js | 61 const server = tls.createServer(options, common.mustCall((cleartext) => {
62 cleartext.on('error', function(er) {
69 cleartext.end();
|
| D | test-tls-session-cache.js | 59 const server = tls.createServer(options, function(cleartext) { argument
60 cleartext.on('error', function(er) {
68 cleartext.end('');
|
| D | test-tls-peer-certificate-encoding.js | 38 const server = tls.createServer(options, (cleartext) => {
39 cleartext.end('World');
|
| D | test-tls-peer-certificate-multi-keys.js | 36 const server = tls.createServer(options, function(cleartext) { argument
37 cleartext.end('World');
|
| /third_party/node/test/sequential/ |
| D | test-tls-securepair-client.js | 52 assert.strictEqual(pair.cleartext.getPeerCertificate().ext_key_usage.length,
54 assert.strictEqual(pair.cleartext.getPeerCertificate().ext_key_usage[0],
130 assert.ok(pair.cleartext.writable);
140 pair.cleartext.write('hello\r\n', function() {
149 pair.cleartext.getPeerCertificate());
151 pair.cleartext.getCipher());
155 pair.cleartext.on('data', function(d) {
|
| D | test-tls-session-timeout.js | 112 const server = tls.createServer(options, (cleartext) => {
113 cleartext.on('error', (er) => {
117 cleartext.end();
|
| /third_party/openssl/test/recipes/ |
| D | 15-test_mp_rsa.t | 42 my $cleartext = data_file("plain_text");
67 '-encrypt', '-in', $cleartext,
82 '-encrypt', '-in', $cleartext,
91 '-encrypt', '-in', $cleartext,
109 open(my $fh, "<", $cleartext) or return 0;
|
| /third_party/openssl/test/ |
| D | modes_internal_test.c | 194 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()
|
| /third_party/node/lib/ |
| D | tls.js | 365 this.cleartext = new exports.TLSSocket(socket2, {
372 this.cleartext.once('secure', () => this.emit('secure'));
376 this.cleartext.destroy();
|
| /third_party/nghttp2/doc/sources/ |
| D | h2load-howto.rst | 35 cleartext connection, the default protocol is HTTP/2. To change the
36 protocol in cleartext connection, use :option:`--no-tls-proto` option.
38 cleartext and SSL/TLS connections.
|
| /third_party/openssl/doc/man3/ |
| D | SMIME_write_CMS.pod | 26 If B<CMS_DETACHED> is set then cleartext signing will be used, this option only
37 If cleartext signing is being used and B<CMS_STREAM> not set then the data must
|
| D | SMIME_write_PKCS7.pod | 26 If B<PKCS7_DETACHED> is set then cleartext signing will be used,
38 If cleartext signing is being used and B<PKCS7_STREAM> not set then
|
| D | SMIME_write_ASN1.pod | 43 If B<CMS_DETACHED> is set then cleartext signing will be used, this option only
54 If cleartext signing is being used and B<CMS_STREAM> not set then the data must
|
| D | SMIME_read_PKCS7.pod | 20 If cleartext signing is used then the content is saved in
|
| D | SMIME_read_ASN1.pod | 34 If cleartext signing is used then the content is saved in a memory bio which is
|
| D | SMIME_read_CMS.pod | 21 If cleartext signing is used then the content is saved in a memory bio which is
|
| D | DES_random_key.pod | 146 (cleartext) is encrypted in to the I<output> (ciphertext) using the
149 ciphertext) is decrypted into the I<output> (now cleartext). Input
165 routine cipher-block-chain encrypts the cleartext data pointed to by
|
| D | SSL_CTX_dane_enable.pod | 333 even cleartext.
342 application must avoid cleartext, but cannot authenticate the peer,
|
| /third_party/openssl/doc/man1/ |
| D | openssl-passwd.pod.in | 85 In the output list, prepend the cleartext password and a TAB character
90 When the B<-table> option is used, reverse the order of cleartext and hash.
|
| /third_party/node/benchmark/tls/ |
| D | secure-pair.js | 92 serverPair.cleartext.pipe(client);
|
| /third_party/python/Doc/library/ |
| D | crypt.rst | 162 cleartext = getpass.getpass()
163 return compare_hash(crypt.crypt(cleartext, cryptedpasswd), cryptedpasswd)
|
| /third_party/mbedtls/docs/proposed/ |
| D | psa-driver-developer-guide.md | 20 * **Transparent** drivers implement cryptographic operations on keys that are provided in cleartext…
|