2010/07/20 7:26, Ted Unangst wrote:
quoted text
> On Sun, Jul 18, 2010 at 11:14 AM, Yoshisato YANAGISAWA
> <yanagisawa@csg.is.titech.ac.jp>  wrote:
>>> Not to mention there are software patent claims againt camellia. That's
>>> a no go right there.
>>
>> OpenBSD has already included Camellia source code as a part of OpenSSL.  It
>> is disabled by default, though.
>> At the time OpenSSL included Camellia, NTT had shown following news release:
>> http://www.ntt.co.jp/news/news01e/0104/010417.html
>>
>> NTT also announced that their Camellia implementation also becomes open
>> source distributed under BSDL, GPL, and so on:
>> http://www.ntt.co.jp/news/news06e/0604/060413a.html
>>
>> Are there any problems?
>
> The first link says "Caution: This statement is valid only for
> implementing Camellia, EPOC, PSEC, and ESIGN, respectively, as is, and
> does not permit modification of said algorithms."
>
> The second link says you no longer need to apply to get a license, but
> still restricts it to only people using Camellia.

Yes, the rule in the first link is overwritten by the second link, and 
everyone can make open source software with Camellia algorithm for free.

quoted text
> Free software you can't modify is not free software.

Yes, but is Camellia code unmodifiable?
I could not find this kind of meaning from second link.
Camellia code in OpenSSL (also included in OpenBSD) is also distributed 
under BSDL, and NTT or Mitsubishi cannot restrict modification under 
this license.

Also note that my code do not include Camellia algorithm itself.  It 
only have a sort of glue code to make Camellia available in OpenSSH. 
For my code, I am willing to distribute this under BSDL :)