diff options
Diffstat (limited to 'openssl/vendor/current/doc')
-rw-r--r-- | openssl/vendor/current/doc/apps/ciphers.pod | 26 | ||||
-rw-r--r-- | openssl/vendor/current/doc/apps/smime.pod | 11 | ||||
-rw-r--r-- | openssl/vendor/current/doc/standards.txt | 13 |
3 files changed, 45 insertions, 5 deletions
diff --git a/openssl/vendor/current/doc/apps/ciphers.pod b/openssl/vendor/current/doc/apps/ciphers.pod index 81a2c438..5a071f5d 100644 --- a/openssl/vendor/current/doc/apps/ciphers.pod +++ b/openssl/vendor/current/doc/apps/ciphers.pod @@ -125,11 +125,11 @@ the cipher suites not enabled by B<ALL>, currently being B<eNULL>. =item B<HIGH> "high" encryption cipher suites. This currently means those with key lengths larger -than 128 bits. +than 128 bits, and some cipher suites with 128-bit keys. =item B<MEDIUM> -"medium" encryption cipher suites, currently those using 128 bit encryption. +"medium" encryption cipher suites, currently some of those using 128 bit encryption. =item B<LOW> @@ -235,6 +235,10 @@ cipher suites using MD5. cipher suites using SHA1. +=item B<Camellia> + +cipher suites using Camellia. + =back =head1 CIPHER SUITE NAMES @@ -330,6 +334,24 @@ e.g. DES-CBC3-SHA. In these cases, RSA authentication is used. TLS_DH_anon_WITH_AES_128_CBC_SHA ADH-AES128-SHA TLS_DH_anon_WITH_AES_256_CBC_SHA ADH-AES256-SHA +=head2 Camellia ciphersuites from RFC4132, extending TLS v1.0 + + TLS_RSA_WITH_CAMELLIA_128_CBC_SHA CAMELLIA128-SHA + TLS_RSA_WITH_CAMELLIA_256_CBC_SHA CAMELLIA256-SHA + + TLS_DH_DSS_WITH_CAMELLIA_128_CBC_SHA Not implemented. + TLS_DH_DSS_WITH_CAMELLIA_256_CBC_SHA Not implemented. + TLS_DH_RSA_WITH_CAMELLIA_128_CBC_SHA Not implemented. + TLS_DH_RSA_WITH_CAMELLIA_256_CBC_SHA Not implemented. + + TLS_DHE_DSS_WITH_CAMELLIA_128_CBC_SHA DHE-DSS-CAMELLIA128-SHA + TLS_DHE_DSS_WITH_CAMELLIA_256_CBC_SHA DHE-DSS-CAMELLIA256-SHA + TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA DHE-RSA-CAMELLIA128-SHA + TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA DHE-RSA-CAMELLIA256-SHA + + TLS_DH_anon_WITH_CAMELLIA_128_CBC_SHA ADH-CAMELLIA128-SHA + TLS_DH_anon_WITH_CAMELLIA_256_CBC_SHA ADH-CAMELLIA256-SHA + =head2 Additional Export 1024 and other cipher suites Note: these ciphers can also be used in SSL v3. diff --git a/openssl/vendor/current/doc/apps/smime.pod b/openssl/vendor/current/doc/apps/smime.pod index 84b673f7..caf2d268 100644 --- a/openssl/vendor/current/doc/apps/smime.pod +++ b/openssl/vendor/current/doc/apps/smime.pod @@ -20,6 +20,9 @@ B<openssl> B<smime> [B<-aes128>] [B<-aes192>] [B<-aes256>] +[B<-camellia128>] +[B<-camellia192>] +[B<-camellia256>] [B<-in file>] [B<-certfile file>] [B<-signer file>] @@ -129,10 +132,10 @@ B<-verify>. This directory must be a standard certificate directory: that is a hash of each subject name (using B<x509 -hash>) should be linked to each certificate. -=item B<-des -des3 -rc2-40 -rc2-64 -rc2-128 -aes128 -aes192 -aes256> +=item B<-des -des3 -rc2-40 -rc2-64 -rc2-128 -aes128 -aes192 -aes256 -camellia128 -camellia192 -camellia256> the encryption algorithm to use. DES (56 bits), triple DES (168 bits), -40, 64 or 128 bit RC2 or 128, 192 or 256 bit AES respectively. If not +40, 64 or 128 bit RC2, 128, 192 or 256 bit AES, or 128, 192 or 256 bit Camellia respectively. If not specified 40 bit RC2 is used. Only used with B<-encrypt>. =item B<-nointern> @@ -354,6 +357,10 @@ alternatively you can base64 decode the signature and use openssl smime -verify -inform DER -in signature.der -content content.txt +Create an encrypted message using 128 bit Camellia: + + openssl smime -encrypt -in plain.txt -camellia128 -out mail.msg cert.pem + =head1 BUGS The MIME parser isn't very clever: it seems to handle most messages that I've thrown diff --git a/openssl/vendor/current/doc/standards.txt b/openssl/vendor/current/doc/standards.txt index f6675b57..bda55d15 100644 --- a/openssl/vendor/current/doc/standards.txt +++ b/openssl/vendor/current/doc/standards.txt @@ -88,10 +88,17 @@ PKCS#12: Personal Information Exchange Syntax Standard, version 1.0. (Format: TXT=143173 bytes) (Obsoletes RFC2437) (Status: INFORMATIONAL) +3713 A Description of the Camellia Encryption Algorithm. M. Matsui, + J. Nakajima, S. Moriai. April 2004. (Format: TXT=25031 bytes) + (Status: INFORMATIONAL) + 3820 Internet X.509 Public Key Infrastructure (PKI) Proxy Certificate Profile. S. Tuecke, V. Welch, D. Engert, L. Pearlman, M. Thompson. June 2004. (Format: TXT=86374 bytes) (Status: PROPOSED STANDARD) +4132 Addition of Camellia Cipher Suites to Transport Layer Security + (TLS). S. Moriai, A. Kato, M. Kanda. July 2005. (Format: TXT=13590 + bytes) (Status: PROPOSED STANDARD) Related: -------- @@ -250,7 +257,11 @@ STARTTLS documents. Protocol. A. Jungmaier, E. Rescorla, M. Tuexen. December 2002. (Format: TXT=16333 bytes) (Status: PROPOSED STANDARD) - "Securing FTP with TLS", 01/27/2000, <draft-murray-auth-ftp-ssl-05.txt> +3657 Use of the Camellia Encryption Algorithm in Cryptographic + Message Syntax (CMS). S. Moriai, A. Kato. January 2004. + (Format: TXT=26282 bytes) (Status: PROPOSED STANDARD) + +"Securing FTP with TLS", 01/27/2000, <draft-murray-auth-ftp-ssl-05.txt> To be implemented: |