On 09/15/2009 07:47 AM, Andreev Konstantin wrote:
Hello.
I am currently in the process of adding support for GOST algorithms
(RFC 4357,4490,4491) into the NSS.
At this moment I implemented GOST hashing and GOST signature
verification algorithms in the NSS. This works throughout the whole
st
On 2009-09-15 07:47 PDT, Andreev Konstantin wrote:
> Hello.
>
> I am currently in the process of adding support for GOST algorithms (RFC
> 4357,4490,4491) into the NSS.
>
> At this moment I implemented GOST hashing and GOST signature verification
> algorithms in the NSS. This works throughout the
Frank Hecker writes:
> Nelson B Bolyard wrote:
>> Today, I see the FSF web site talks about "copyright assignment". I don't
>> know all the implications of that, but I presume that it is essentially
>> a relinquishment, except that you keep your own name on the copyrighted
>> work.
>
> One last c
On 14 сен, 03:45, Frank Hecker wrote:
> Nelson B Bolyard wrote:
> > Today, I see the FSF web site talks about "copyright assignment". I don't
> > know all the implications of that, but I presume that it is essentially
> > a relinquishment, except that you keep your own name on the copyrighted
> >
Nelson B Bolyard wrote:
Today, I see the FSF web site talks about "copyright assignment". I don't
know all the implications of that, but I presume that it is essentially
a relinquishment, except that you keep your own name on the copyrighted
work.
One last comment on this: Typical copyright ass
Owen Shepherd wrote:
Copyright assignment is, and always has been, orthogonal to GPL licensing. The
FSF
requires that you assign copyright to them for any non-trivial contributions to
their projects (Presumably so they have the ability to handle legal actions,
such
as infringement lawsuits, for
On Sep 13, 2009, at 9:29, Nelson B Bolyard wrote:
On 2009-09-13 06:26 PDT, Frank Hecker wrote:
However since all the relevant code was contributed by Cryptocom,
all we
need to do is to ask permission from Cryptocom to be able to use the
source files in NSS under the NSS licensing arrangeme
Nelson B Bolyard wrote:
> Today, I see the FSF web site talks about "copyright assignment". I don't
> know all the implications of that, but I presume that it is essentially
> a relinquishment, except that you keep your own name on the copyrighted
> work.
>
> http://www.gnu.org/licenses/why-assign.
On 2009-09-13 06:26 PDT, Frank Hecker wrote:
> However since all the relevant code was contributed by Cryptocom, all we
> need to do is to ask permission from Cryptocom to be able to use the
> source files in NSS under the NSS licensing arrangements (i.e., the
> MPL/GPL/LGPL tri-license). Since Cry
Nelson Bolyard wrote:
Can I use the library with GOST from OpenSSL (libgost.so) for
integration into the NSS?
Any software contributed to NSS must be licensed under the Mozilla
public "tri-license". If you are the sole author of a piece of code
that you have previously contributed to another p
On 2009-09-12 03:52 PDT, Martin Paljak wrote:
>
> On 12.09.2009, at 2:43, Nelson Bolyard wrote:
>> 3. The PKCS#11 crypto API standard must be amended to have one or more
>> "mechanisms" defined for doing GOST encryption and decryption in CBC
>> mode. This definition must be proposed to the PK
On 12.09.2009, at 2:43, Nelson Bolyard wrote:
3. The PKCS#11 crypto API standard must be amended to have one or more
"mechanisms" defined for doing GOST encryption and decryption in CBC
mode. This definition must be proposed to the PKCS#11 ("cryptoki")
working group as a proposed amendme
On 2009-09-10 23:14 , nsk yatree wrote:
> Hi.
>
> Most likely I will not be the first person who asks such questions.
I think you might well be the first to ask how to add GOST.
Others have asked the NSS team to do it. You've asked how to do it
yourself. That's a much better question. :)
> Mo
13 matches
Mail list logo
