On Thu, Apr 20, 2006 at 11:44:07AM +0300, Alexey E. Suslikov wrote:
> Camellia was certified as the IETF standard cipher (Proposed
> Standard) for SSL/TLS cipher suites (RFC4132) and IPsec (RFC4312).
but there's no reason to add more ciphers. there are more then enough already.
so? we don't need more symmetric ciphers...
On Thu, 20 Apr 2006, Alexey E. Suslikov wrote:
> Camellia was certified as the IETF standard cipher (Proposed
> Standard) for SSL/TLS cipher suites (RFC4132) and IPsec (RFC4312).
>
> Source:
> https://info.isl.ntt.co.jp/crypt/eng/camellia/source_s.htm
On Thursday 20 April 2006 07:45, Dimitry Andric wrote:
> Alexey E. Suslikov wrote:
> > Camellia was certified as the IETF standard cipher (Proposed
> > Standard) for SSL/TLS cipher suites (RFC4132) and IPsec (RFC4312).
> >
> > Source:
> > https://info.isl.ntt.co.jp/crypt/eng/camellia/source_s.html
>Hmm, isn't the notice on that page incompatible with the BSD license?
*cut*
As far as I can see the COde has MANY licenses. THe BSD-License is clear
and clean.
I downloaded the SRC:
README contained:
---
This is a Crypto engine for Camellia.
Licence: BSD
version: 1.0
For inquires regarding
Alexey E. Suslikov wrote:
> Camellia was certified as the IETF standard cipher (Proposed
> Standard) for SSL/TLS cipher suites (RFC4132) and IPsec (RFC4312).
>
> Source:
> https://info.isl.ntt.co.jp/crypt/eng/camellia/source_s.html
Hmm, isn't the notice on that page incompatible with the BSD lice
Camellia was certified as the IETF standard cipher (Proposed
Standard) for SSL/TLS cipher suites (RFC4132) and IPsec (RFC4312).
Source:
https://info.isl.ntt.co.jp/crypt/eng/camellia/source_s.html
Introduction:
http://info.isl.ntt.co.jp/crypt/eng/camellia/intro.html
6 matches
Mail list logo