Re: [ECOS] racoon working with eCos

["sandeep" <sandeep at codito dot com>]

Thanks Andrew,

> As i said earlier, because of American legal requirements, the
> encryption algorithms themselves cannot go into CVS. The rest of it
> probably can. So there needs to be a clean separation and the
> appropriate CDL to control this.
>
> I suggest you make them available for comments. Put it up on a server
> somewhere since i suspect the changes are quite big. We will then take
> a look and make some suggestions for changes that need to be made
> before the code can be included in the CVS.
Will do some cleanup/separation in coming week and find a way to share it for
your comments.

> > are there some formalities to be done for making the stuff available?
>
> You will need a copyright assignment for the parts that go into
> CVS. See http://ecos.sourceware.org/ecos/assign.html
I didn't get need for this part. We didn't write the code, just ported it to
eCos. I can assign copyright only for something that is my work. right!

regards
sandeep



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.515 / Virus Database: 313 - Release Date: 9/1/2003


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss