Home
last modified time | relevance | path

Searched refs:traditional (Results 1 – 20 of 20) sorted by relevance

/openssl/apps/
H A Dpkey.c80 int private = 0, traditional = 0, check = 0, pub_check = 0; in pkey_main() local
138 traditional = 1; in pkey_main()
181 if (traditional && (noout || outformat != FORMAT_PEM)) in pkey_main()
276 if (traditional) { in pkey_main()
H A Dgenrsa.c90 int traditional = 0; in genrsa_main() local
146 traditional = 1; in genrsa_main()
228 if (traditional) { in genrsa_main()
H A Drsa.c136 int traditional = 0; in rsa_main() local
215 traditional = 1; in rsa_main()
353 if (traditional) in rsa_main()
H A Dpkcs8.c92 int private = 0, traditional = 0; in pkcs8_main() local
142 traditional = 1; in pkcs8_main()
367 if (traditional) in pkcs8_main()
H A Dopenssl-vms.cnf99 # Comment out the following two lines for the "traditional"
H A Dopenssl.cnf99 # Comment out the following two lines for the "traditional"
/openssl/doc/man1/
H A Dopenssl-pkcs8.pod.in22 [B<-traditional>]
64 unencrypted private key in PKCS#8 format. If the B<-traditional> option is
65 used then a traditional format private key is written instead.
68 unencrypted private key in traditional DER format.
75 =item B<-traditional>
77 When this option is present and B<-topk8> is not a traditional format private
180 counts are more secure that those encrypted using the traditional
186 level whereas the traditional format includes them at a PEM level.
249 Convert a private key from any PKCS#8 encrypted format to traditional format:
251 openssl pkcs8 -in pk8.pem -traditional -out key.pem
H A Dopenssl-genrsa.pod.in32 [B<-traditional>]
87 =item B<-traditional>
89 Write the key using the traditional PKCS#1 format instead of the PKCS#8 format.
H A Dopenssl-pkey.pod.in27 [B<-traditional>]
132 =item B<-traditional>
135 with the appropriate encryption algorithm (if any). If the B<-traditional>
136 option is specified then the older "traditional" format is used instead.
H A Dopenssl-rsa.pod.in37 [B<-traditional>]
71 =item B<-traditional>
73 When writing a private key, use the traditional PKCS#1 format
H A Dopenssl-dsa.pod.in48 traditional SSLeay compatible format for private key encryption: newer
/openssl/doc/man3/
H A DPEM_read_bio_PrivateKey.pod233 handle traditional and PKCS#8 format encrypted and unencrypted keys.
236 "traditional" format with a simple private key marker and should only
258 RSA structure. The write routines uses traditional format. The read
272 DSA structure. The write routines uses traditional format. The read
391 the traditional routines use a count of 1) unless compatibility with older
518 Write a private key (using traditional format) to a BIO using
H A DSSL_set_default_stream_mode.pod25 allows legacy applications to use QUIC similarly to a traditional TLS
H A DRSA_get0_key.pod157 in use, which is 0 for traditional RSA and the number of extra primes for
H A DSSL_CTX_dane_enable.pod90 and authentication will be based on any configured traditional trust-anchors;
/openssl/doc/internal/man3/
H A Devp_pkey_export_to_provider.pod37 best to get "traditional" PEM output even if the input B<EVP_PKEY> has a
H A Dossl_rcu_lock_new.pod38 In addition to more traditional Read/Write locks, OpenSSL provides
/openssl/doc/designs/quic-design/
H A Dquic-io-arch.md47 instead of bytestream semantics as has been the case with traditional TLS
513 default for parity with traditional Berkeley sockets APIs and to make things
/openssl/crypto/engine/
H A DREADME.md111 EVP storage, nor is it returned to applications from traditional API functions,
/openssl/
H A DCHANGES.md10503 traditional format. This form is standardised, more secure and doesn't
18423 if a DER encoded private key is RSA or DSA traditional format. Changed
18424 d2i_PrivateKey_bio() to use it. This is only needed for the "traditional"
18472 traditional format into an EVP_PKEY structure.

Completed in 80 milliseconds