Matt Bertapelle | 14 Nov 2003 20:10

v1.6 Enhanced SNACC Freeware Now Available


All,

DigitalNet Government Solutions has delivered the v1.6 eSNACC Abstract Syntax Notation.1 (ASN.1)
Compiler, C++ library and C library source code compilable for Linux, Sun Solaris 2.8 and Microsoft (MS)
Windows NT/98/2000/XP.  The eSNACC software 
is freely available to everyone from:
<http://digitalnet.com/knowledge/snacc_home.htm>

The eSNACC ASN.1 software can be used to ASN.1 encode and decode
objects.  In past releases, DigitalNet improved the eSNACC C++ 
library to implement the Distinguished Encoding Rules (DER), 
support large ASN.1 INTEGERs, and improve memory usage.    

v1.6 eSNACC enhancements (compared to v1.5 release):

1) Remove string checks on decode, while keeping them onencode.

2) Interpret name space, tag type definitions, and integer names.

We successfully tested the v1.6 eSNACC ASN.1 C++ and C libraries
using the Simple Network Management Protocol (SNMP) v1 test
suite (18,000 test cases) developed by the University of Oulu.    

We tested the v1.6 eSNACC release with the v2.3 S/MIME
Freeware Library (SFL) available from 
<http://www.digitalnet.com/knowledge/sfl_home.htm> that 
uses the eSNACC ASN.1 software to encode and decode the IETF 
S/MIME v3 Cryptographic Message Syntax (RFC 3369) and Enhanced
Security Services for S/MIME (RFC 2634) security protocol.  
(Continue reading)

Matt Bertapelle | 14 Nov 2003 20:10

v2.3 Certificate Management Library (CML) Now Available

All, DigitalNet Government Solutions has delivered the Version 2.3 Certificate Management Library (CML) for Microsoft Windows, Sun Solaris and Linux. The v2.3 CML and documentation is freely available at: <http://www.digitalnet.com/knowledge/cml_home.htm>. Applications requiring Public Key Infrastructure (PKI) security services can use the CML to meet their X.509 certificate and Certificate Revocation List (CRL) processing requirements. The v2.3 CML is described in the v2.3 CML Application Programming Interface (API) document. It implements the 2000 X.509 Recommendation certification path verification processing rules and SDN.706 profile. It meets the majority of the IETF PKIX RFC 3280 Certificate/CRL Profile requirements. There are some unsupported features such as Delta CRLs. The v2.3 CML Abstract Syntax Notation One (ASN.1) decodes X.509 Certificates and CRLs. It requires the v1.6 Enhanced SNACC ASN.1 software that is freely available from: <http://www.digitalnet.com/knowledge/snacc_home.htm>. The CML provides robust certification path building capabilities such as using cross certificates. The CML uses the accompanying Storage and Retrieval Library (SRL) (optionally) to provide local certificate and CRL storage management functions. The SRL (optionally) provides remote directory retrieval capabilities using the Lightweight Directory Access Protocol (LDAP). The CML has been thoroughly tested including validating X.509 Certificates and CRLs created by a variety of Certification Authority (CA) products, and signed using the Digital Signature Algorithm (DSA) and RSA algorithms. Further enhancements, ports and testing of the CML are still in process. Further releases of the CML will be provided as significant capabilities are added. CML v2.3 includes the following enhancements (compared to v2.2 CML release): 1) Added optional bitmask field to the InitSettings_struct to allow the application to specify which CTILs the CML should load during CM_CreateSessionExt().  The application can use this bitmask field rather than pass in a pointer to a valid CTIL::CSM_CtilMgr object in the pTokenObj field of the InitSettings_struct.


2) Created new C++ function, CML::SetTrustAnchors(), to allow an application to specify the trusted public keys for a CML session even when the trusted keys don't appear in certificates.



3) Created new C++ class, TrustAnchor, that allows the the application to optionally specify additional path validation constraints on each trust anchor when calling CML::SetTrustAnchors().  The additional constraints that may be specified are the maximum path length to accept and the name constraints to apply. 



4) Enhanced the CML cache and session code to be thread-safe.  Applications may now safely share a single CML session amongst multiple threads. 


5) Enhanced CML to check name constraints of email addresses included in DNs.



6) Optimized CML path building algorithm for use with the Federal Bridge Certification Authority (FBCA) hierarchy.



7) Added two new fields to the C++ CertMatchData structure, canSignCerts and canSignCrls.  These new fields enable callers of the CML::RequestCerts() C++ function to optionally restrict the certificates returned to having those key usage privileges.



8) Fixed bug in the policy mapping processing of path validation.  The CML wasn't properly rejecting paths when the special any-policy value appeared in a policy mappings extension.



9) Enhanced CRL retrieval and validation code so the CML will now retrieve and validate multiple CRLs if necessary to check all revocation reasons, even when no distribution point is present in the certificate.  Previous versions of the CML would only check a single complete CRL if no distribution point was present.



10) Added ECDSA-with-SHA256 and ECDSA-with-SHA384 to list of CML supported signature algorithms.




v2.3 SRL includes the following enhancements (compared to v2.2 SRL release):
1) Enhanced SRL to perform HTTP and FTP URL retrievals.

2) Removed SRL code that caused some UNIX systems to hang under certain circumstances when performing an LDAP bind.  With the removal of the offending code, the SRL now relies completely on the LDAP library to timeout when an LDAP server is unreachable during a bind operation.  During testing, some LDAP libraries would take up to 3 minutes to return from an LDAP bind when the server was down or unreachable.

All source code for the CML is being provided at no cost and with no financial limitations regarding its use and distribution. Organizations can use the CML without paying any royalties or licensing fees. The CML was originally developed by the U.S. Government. DigitalNet is enhancing and supporting the CML under contract to the U.S. Government. The U.S. Government is furnishing the CML software at no cost to the vendor subject to the conditions of the CML Public License provided with the CML software. The CML makes calls to an algorithm-independent CTIL API that provides
access to a variety of external crypto libraries. There is a CTIL for
each crypto library that maps the generic CTIL API calls to the
specific calls for that crypto library. DigitalNet provides CTILs for
the Microsoft CAPI v2.0, Crypto++, RSA BSAFE, Spyrus SPEX/ and
FORTEZZA Cryptologic Interface libraries. DigitalNet also provides a
PKCS #11 CTIL that enables PKCS #11-compliant libraries to be used
with the CML. The underlying, external crypto libraries are not
distributed as part of the CML software.


The CML has been successfully tested with the v2.3 S/MIME Freeware
Library (SFL) that is freely available from
<http://www.DigitalNet.com/knowledge/sfl_home.htm>.

The CML has been successfully tested with the v2.3 Access Control
Library (ACL) that is freely available to everyone from:
<http://www.DigitalNet.com/knowledge/acl_home.htm>.

The CML has been successfully used to build and verify
certificate paths used in the Bridge Certification Authority (BCA)
demonstration which includes cross-certified hierarchical and non-
hierarchical PKIs. The BCA Interoperability Test Suite (BITS)
is a free and openly available test resource provided to
facilitate vendor development of secure, interoperable Public
Key Enabled applications. The CML has been used to successfully
develop and verify the BITS X.509 certification paths available
from <http://bcatest.atl.DigitalNet.com>.

The National Institute of Standards and Technology (NIST) is
providing a standard test suite of X.509 certificate paths
<http://csrc.nist.gov/pki/testing/x509paths.html> that can be
used for testing applications against RFC 2459. The CML was
used to successfully process the NIST test data.

The CML meets the requirements stated in the SDN.706 Certificate/
CRL Profile required by the U.S. Defense Message System (DMS)
project.

The Internet Mail Consortium (IMC) has established a CML web page
<http://www.imc.org/imc-cml> and a CML mail list which is used to:
distribute information regarding CML releases; discuss CML-related
issues; and allow CML users to provide feedback, comments, bug
reports, etc. Subscription information for the imc-cml mailing list
is at the IMC web site listed above.

All comments regarding the CML source code and documents are welcome.
This CML release announcement was sent to several mail lists, but
please send all messages regarding the CML to the imc-cml mail list
ONLY. Please do not send messages regarding the CML to any of the IETF
mail lists. We will respond to all messages sent to the imc-cml mail
list. -- -- Matthew J. Bertapelle DigitalNet Government Solution, LLC www.DigitalNet.com
Matt Bertapelle | 14 Nov 2003 20:10

v2.3 S/MIME Freeware Library (SFL) Now Available

All, DigitalNet Government Solutions has delivered the Version 2.3 S/MIME Freeware Library (SFL) source code. The SFL source code files and documents are freely available at <http://www.digitalnet.com/knowledge/sfl_home.htm>. The SFL implements the IETF S/MIME v3 RFC 3369 Cryptographic Message Syntax (CMS) and RFC 2634 Enhanced Security Services (ESS) specifications. It implements portions of the RFC 2633 Message Specification, RFC 2632 Certificate Handling, and RFC 3370 CMS Algorithms specifications. When used in conjunction with the Crypto++ freeware library, the SFL implements the RFC 2631 Diffie-Hellman (D-H) Key Agreement Method specification. It has been successfully tested using the Microsoft (MS) Windows 2000/XP, Linux and Sun Solaris 2.8 operating systems. Further enhancements, ports and testing of the SFL are still in process. Further releases of the SFL will be provided as significant capabilities are added. The SFL has been successfully used to sign, verify, encrypt and decrypt CMS/ESS objects using: DSA, E-S D-H, 3DES algorithms provided by the Crypto++ library; RSA suite of algorithms provided by the RSA BSAFE 6.0 Crypto-C and Crypto++ libraries; and Fortezza suite of algorithms provided by the Fortezza Crypto Card. The v2.3 SFL uses the v2.3 Certificate Management Library (CML) and v1.6 Enhanced SNACC (eSNACC) ASN.1 C++ Library to encode/decode objects. The v2.3 SFL release includes: SFL High-level library; Free (a.k.a. Crypto++) Crypto Token Interface Library (CTIL); BSAFE CTIL; Fortezza CTIL; SPEX/ CTIL; PKCS #11 CTIL; Microsoft CAPI v2.0 CTIL; test utilities; test drivers; and test data. All CTILs were tested as Dynamically Linked Libraries (DLL) using MS Windows. The Fortezza, BSAFE and Crypto++ CTILs were tested with the respective security libraries as shared objects using Linux and Solaris 2.8. The SFL has been successfully used to exchange signedData and envelopedData messages with the MS Internet Explorer Outlook Express v4.01, Netscape Communicator 4.X, Entrust and Baltimore S/MIME products. Signed messages have been exchanged with the RSA S/MAIL and WorldTalk S/MIME v2 products. The SFL has also been used to perform S/MIME v3 interoperability testing with Microsoft that exercised the majority of the features specified by RFCs 3369, 3370, 2631 and 2634. This testing included the RSA, DSA, E-S D-H, 3DES, SHA and Fortezza algorithms. We used the SFL to successfully process the SFL-supported sample data included in the S/MIME WG "Examples of S/MIME Messages" document. We also used the SFL to generate S/MIME v3 sample messages that were included in the "Examples" document. The use of the v2.3 SFL is described in the v2.3 SFL Application Programming Interface (API) and v2.3 SFL Software Design Description documents. The use of the v2.3 CTIL API is described in the v2.3 CTIL API document. v2.3 SFL includes the following enhancements (compared to v2.2 SFL and CTIL releases):
1) The SFL library now provides Compressed Data Content Type for CMS.  This is implemented as a new ContentInfo type and is an extension to the types currently defined in CMS.  Compressed data can be performed on the SignedData and EnvelopedData items without application interaction, by providing the appropriate compressDataFlag flag during the session.



2) There is a major change in how the content is stored in the CSM_CommonData object.   With the addition of Compressed Data Content Type for CMS, it was necessary to distinguish between clear content and unclear content.  CSM_CommonData now stores both clear and unclear content making the application determine which content to use according to desired processing.  See the CSM_CommonData section for the changes.


 


3) The SFL library now provides Password-Based Encryption for CMS.  This provides a method of encrypting data using user-supplied passwords. It is implemented as a RecipientInfo type and is an extension to the RecipientInfo Types currently defined in CMS.



4) The thread support logic was updated in the SFL and libCtilMgr.  Specifically, the CSM_CSInst::AccessCertificates() method has been removed to eliminate thread access problems. This does not affect the CSM_CtilInst class, used by the CML.  The "AccessCertificcates()" and "AccessCRLs()" methods have been removed due to thread issues.  They are described more fully in the CSM_CSInst class description.


v2.3 CTILs include the following enhancements (compared to v2.2 release): 1) Elliptic Curve functionality has been added to the sm_free3 CTIL crypto library.  This includes ECDSA and ECDH processing.

v2.3 Certificate Builder include the following enhancements since v2.2: 1) Certificate Builder has been enhanced with ECDSA certificate public/private key generation. 2) Certificate Builder has been enhanced with PKCS#12 generation logic. 3) Certificate Builder has been enhanced to generate UTF-8 strings. The SFL is developed to maximize portability to 32-bit operating systems. In addition to testing on MS Windows, Linux and Solaris 2.8, we may port the SFL to other operating systems. All source code for the SFL is being provided at no cost and with no financial limitations regarding its use and distribution. Organizations can use the SFL without paying any royalties or licensing fees. DigitalNet is developing the SFL under contract to the U.S. Government. The U.S. Government is furnishing the SFL source code at no cost to the vendor subject to the conditions of the "SFL Public License". On 14 January 2000, the U.S. Department of Commerce, Bureau of Export Administration published a new regulation implementing an update to the U.S. Government's encryption export policy <http://www.bxa.doc.gov/Encryption/Default.htm>. In accordance with the revisions to the Export Administration Regulations (EAR) of 14 Jan 2000, the downloading of the SFL source code is not password controlled. The SFL is composed of a high-level library that performs generic CMS and ESS processing independent of the crypto algorithms used to protect a specific object. The SFL high-level library makes calls to an algorithm-independent CTIL API. The underlying, external crypto token libraries are not distributed as part of the SFL source code. The application developer must independently obtain these libraries and then link them with the SFL. The SFL uses the CML and eSNACC ASN.1 Library to encode/decode certificates, ACs, CRLs and components thereof. The CML is freely available at: <http://www.DigitalNet.com/knowledge/cml_home.htm>. The SFL has been successfully tested in conjunction with the Access Control Library (ACL) that is freely available to everyone from: <http://www.DigitalNet.com/knowledge/acl_home.htm>. The National Institute of Standards and Technology (NIST) is providing test S/MIME messages (created by DigitalNet) at <http://csrc.nist.gov/pki/testing/x509paths.html>. DigitalNet used the SFL to successfully process the NIST test data. NIST is using the SFL and CML as part of the NIST S/MIME Test Facility (NSMTF) that they are planning to host (see <http://csrc.ncsl.nist.gov/pki/smime/>). Vendors will be able to use the NSMTF to help determine if their products comply with the IETF S/MIME v3 specifications and the Federal S/MIME v3 Client Profile. The SFL has been integrated into many applications to provide CMS/ESS security services. For example, the SFL was integrated into a security plug-in for a commercial e-mail application that enabled the application to meet the Bridge Certification Authority Demonstration Phase II requirements including implementing ESS features such as security labels. The Internet Mail Consortium (IMC) has established an SFL web page <http://www.imc.org/imc-sfl>. The IMC has also established an SFL mail list which is used to: distribute information regarding SFL releases; discuss SFL-related issues; and provide a means for SFL users to provide feedback, comments, bug reports, etc. Subscription information for the imc-sfl mailing list is at the IMC web site listed above. All comments regarding the SFL source code and documents are welcome. This SFL release announcement was sent to several mail lists, but please send all messages regarding the SFL to the imc-sfl mail list ONLY. Please do not send messages regarding the SFL to any of the IETF mail lists. We will respond to all messages sent to the imc-sfl mail list. -- -- Matthew J. Bertapelle DigitalNet Government Solution, LLC www.DigitalNet.com
Andrew Marlow | 15 Nov 2003 00:24
Picon
Picon

Re: v1.6 Enhanced SNACC Freeware Now Available


Matt Bertapelle <matt.bertapelle <at> digitalnet.com> writes:
>
>All,
>
>DigitalNet Government Solutions has delivered the v1.6 eSNACC Abstract
>Syntax Notation.1 (ASN.1) Compiler, C++ library and C library source code

Thw web page
http://www.digitalnet.com/knowledge/snacc_lib.htm
refers to v1.6 release notes but the link is to the release notes for v1.5.

Regards,

Andrew Marlow
----
There is an emerald here the size of a plover's egg!

W. Borgert | 15 Nov 2003 21:43
Picon
Favicon

Re: GPL violation? (Was: v1.6 Enhanced SNACC Freeware)


[Resent mail, because I wasn't on the mailing lists.]

On Fri, Nov 14, 2003 at 08:38:16PM +0000, W. Borgert wrote:
> Hello,
> 
> On Fri, Nov 14, 2003 at 02:10:30PM -0500, Matt Bertapelle wrote:
> > The eSNACC ASN.1 library is totally unencumbered as stated 
> > in the Enhanced SNACC Software Public License.  All source code
> > for the eSNACC software is being provided at no cost and with no
> > financial limitations regarding its use and distribution.  
> > Organizations can use the eSNACC software without paying
> > any royalties or licensing fees.  
> 
> One question about the license: The original SNACC software
> has been released by it's authors under the terms of the GNU
> General Public License.  I am not a lawyer, but if I
> understand the GNU GPL correctly, you cannot change the
> license or apply an arbitrary license to a GPL software, if
> you are not the author/copyright holder.  The GPL also
> covers any new code by you, that is linked with SNACC
> ("derived work").  How does your license relate to the GNU
> GPL?  Is the license change legally OK?
> 
> Btw.: I very much appreciate, that you are working on SNACC
> and that you giving the code to the free software community.
> However, I must be 100% sure about the legal status of your
> efforts.  Please don't be annoyed!
> 
> Best regards,
> W. Borgert

Andrew Marlow | 15 Nov 2003 21:47
Picon
Picon

Re: GPL violation? (Was: v1.6 Enhanced SNACC Freeware)


debacle <at> debian.org writes:
>
>[Resent mail, because I wasn't on the mailing lists.]
>
>On Fri, Nov 14, 2003 at 08:38:16PM +0000, W. Borgert wrote:
>> One question about the license: The original SNACC software
>> has been released by it's authors under the terms of the GNU
>> General Public License.  I am not a lawyer, but if I
>> understand the GNU GPL correctly, you cannot change the
>> license or apply an arbitrary license to a GPL software, if
>> you are not the author/copyright holder.  The GPL also
>> covers any new code by you, that is linked with SNACC
>> ("derived work").  How does your license relate to the GNU
>> GPL?  Is the license change legally OK?

Wow, I hadn't realised that SNACC was released under the GPL.
eSNACC looks like a derivative work to me (IANAL).
So it looks to me like eSNACC violates the GPL.
This would be a great pity because I think the world needs
a decent ASN.1 environment that does not prohibit commercial
development, and eSNACC is definately getting there.

I note that a long while ago an annoucement was made that SNACC
was considered to be an orphan project and appeals were made
for someone to adopt SNACC. No-one did. Then sometime later
I found out about eSNACC which whilst clearly related to SNACC,
does not (AFAIK) consider itself to be adopting SNACC.
But I'm sure there is a lot of common code, and there's the original
SNACC manual.

I hope that eSNACC can continue, maybe under the LGPL.
After all, it seems to me that it is a bit like using GCC on a
commercial project. GCC makes special provision (IIRC) for
projects that compile with GCC such that they are not
considered to be deriative works. Maybe we need something
similar so that people can compile and parse ASN.1 without
their program being considered a derivate work. Then eSNACC
can safely be considered a derivate of SNACC without harm
because it won't stop people using it as one uses GCC.
The API could be considered to be on a par with using the
STL that comes with GCC.

Regards,

Andrew Marlow
----
There is an emerald here the size of a plover's egg!

W. Borgert | 16 Nov 2003 12:38
Picon
Favicon

Re: GPL violation? (Was: v1.6 Enhanced SNACC Freeware)


On Sat, Nov 15, 2003 at 08:47:31PM +0000, Andrew Marlow wrote:
> I hope that eSNACC can continue, maybe under the LGPL.
> After all, it seems to me that it is a bit like using GCC on a
> commercial project. GCC makes special provision (IIRC) for
> projects that compile with GCC such that they are not
> considered to be deriative works. Maybe we need something
> similar so that people can compile and parse ASN.1 without
> their program being considered a derivate work. Then eSNACC

As far as I know, the original authors of SNACC allowed
always, that SNACC can be used for everything, including
closed source.  I.e. they have a similar licensing as bison.
While the ASN.1 compiler is GPL, the generated code is not
"viral".  In snacc.tex it is made clear:

"This program, Snacc, is free software; you can redistribute
it and/or modify it under the terms of the GNU General
Public License as published by the Free Software Foundation;
either version 2 of the License, or (at your option) any
later version.

The runtime libraries are copyright to the University of
British Columbia and Michael Sample.  They are free
software; you can redistribute them and/or modify them as
long as the original, unmodified copyright information
with/in them.  The GNU Library Public License has been
removed as of version 1.1."

The next paragraph says:

"What we're trying to say is: you can't sell the compiler
but you can sell products that use the code generated by the
compiler and the runtime libraries."

Which is nonsense, because nobody prohibits selling of GPL
software.

Cheers,
--

-- 
W. Borgert <debacle <at> debian.org>

Richard Stallman | 17 Nov 2003 02:37
Picon
Picon

Re: GPL violation? (Was: v1.6 Enhanced SNACC Freeware)


    I hope that eSNACC can continue, maybe under the LGPL.

The copyright holders of SNACC would have to agree to the change in license.

    GCC makes special provision (IIRC) for
    projects that compile with GCC such that they are not
    considered to be deriative works.

This is not entirely accurate.  In general, code compiled by any
compiler is not a derivative work of the compiler.  That general rule
applies to GCC like any other compiler.

What you are thinking of is that we make a special exception for some
small libraries that accompany GCC, giving permission to include them
in combinations with non-free software.  I decided to make this
exception because the libraries are small.

It would be a grave mistake to think that this is appropriate for all
libraries.  See http://www.gnu.org/philosophy/why-not-lgpl.html
for a general discussion of the issue.

    This would be a great pity because I think the world needs
    a decent ASN.1 environment that does not prohibit commercial
    development,

The GNU GPL does not prohibit commercial development.  It says that
extended versions of the program must be free software.  Including
GPL-covered code in a commercial program is permitted as long as that
commercial program is released under the GPL.  Perhaps when you wrote
"commercial" you really meant "proprietary".

Proprietary, non-free software is designed to deny the user crucial
freedoms.  It does not deserve our help or cooperation.

Richard Stallman | 17 Nov 2003 02:36
Picon
Picon

Re: GPL violation? (Was: v1.6 Enhanced SNACC Freeware)


    One question about the license: The original SNACC software
    has been released by it's authors under the terms of the GNU
    General Public License.  I am not a lawyer, but if I
    understand the GNU GPL correctly, you cannot change the
    license or apply an arbitrary license to a GPL software, if
    you are not the author/copyright holder.

A change in the license requires permission from essentially all the
copyright holders of the code that is actually used.

Pawling, John | 17 Nov 2003 13:57

RE: GPL violation? (Was: v1.6 Enhanced SNACC Freeware)

W. Borgert,

As stated in the attached Enhanced SNACC public license (also available
from http://digitalnet.com/knowledge/snacc_lib.htm), the original SNACC
software is composed of the SNACC Compiler and the SNACC Library.
Michael Sample and the University of British Columbia developed the
original SNACC Compiler and Library.  

According to Michael Sample, the original SNACC Compiler is covered by
the GNU General Public License (GPL), Version 2, June 1991.  

According to Michael Sample, the original SNACC Library software is
completely unencumbered.  None of the GNU public licenses apply to the
original SNACC Library software. 

In summary, the Enhanced SNACC compiler and library are being
distributed properly as per Michael Sample and the University of British
Columbia.

Please see the attached Enhanced SNACC public license for futher
information.

======================================
John Pawling, DigitalNet
DigitalNet KATSIPP Team Program Manager  
John.Pawling <at> DigitalNet.com
141 National Business Pkwy, Suite 210     
Annapolis Junction, MD  USA  20701 
(301) 939-2739 or (410) 880-6095  
www.DigitalNet.com 
======================================

_________________
The information contained herein is for the exclusive use of Government
and Contractor personnel with a need-to-know KATSIPP information.  Such
information is specifically prohibited from posting on unrestricted
bulletin boards or other unlimited access applications.

-----Original Message-----
From: W. Borgert [mailto:debacle <at> debian.org] 
Sent: Saturday, November 15, 2003 3:43 PM
To: Bertapelle, Matt
Cc: imc-snacc; imc-cml; imc-sfl; rms <at> gnu.org
Subject: Re: GPL violation? (Was: v1.6 Enhanced SNACC Freeware)

[Resent mail, because I wasn't on the mailing lists.]

On Fri, Nov 14, 2003 at 08:38:16PM +0000, W. Borgert wrote:
> Hello,
> 
> On Fri, Nov 14, 2003 at 02:10:30PM -0500, Matt Bertapelle wrote:
> > The eSNACC ASN.1 library is totally unencumbered as stated 
> > in the Enhanced SNACC Software Public License.  All source code
> > for the eSNACC software is being provided at no cost and with no
> > financial limitations regarding its use and distribution.  
> > Organizations can use the eSNACC software without paying
> > any royalties or licensing fees.  
> 
> One question about the license: The original SNACC software
> has been released by it's authors under the terms of the GNU
> General Public License.  I am not a lawyer, but if I
> understand the GNU GPL correctly, you cannot change the
> license or apply an arbitrary license to a GPL software, if
> you are not the author/copyright holder.  The GPL also
> covers any new code by you, that is linked with SNACC
> ("derived work").  How does your license relate to the GNU
> GPL?  Is the license change legally OK?
> 
> Btw.: I very much appreciate, that you are working on SNACC
> and that you giving the code to the free software community.
> However, I must be 100% sure about the legal status of your
> efforts.  Please don't be annoyed!
> 
> Best regards,
> W. Borgert
21 February 2003

           	    ENHANCED SNACC SOFTWARE PUBLIC LICENSE

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Original SNACC Software:

The SNACC software is composed of the SNACC Compiler and the SNACC
Library.  Michael Sample and the University of British Columbia 
developed the original SNACC Compiler and Library.  According to 
Michael Sample, the original SNACC Compiler is covered by the 
attached GNU General Public License (GPL), Version 2, June 1991.
According to Michael Sample, the original SNACC Library 
software is completely unencumbered.  None of the GNU public 
licenses apply to the original SNACC Library software.  Each 
SNACC Library source code file includes the following text:

"// Copyright (C) 1992 Michael Sample and the University of British Columbia
//
// This library is free software; you can redistribute it and/or
// modify it provided that this copyright/license information is retained
// in original form.
//
// If you modify this file, you must clearly indicate your changes.
//
// This source code is distributed in the hope that it will be
// useful, but WITHOUT ANY WARRANTY; without even the implied warranty
// of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Enhanced SNACC Software:

Under contract to the U.S. Government, DigitalNet Government Solutions
has enhanced the original SNACC Compiler and Library to
produce the Enhanced SNACC Compiler and Library. 

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Enhanced SNACC Compiler License Information:

The Enhanced SNACC Compiler is covered by the attached GNU GPL.  DigitalNet
has clearly marked all enhancements made to the original SNACC Compiler
as required by the GNU GPL.  DigitalNet has met the requirements of the GNU GPL 
including: providing all source code for the Enhanced SNACC Compiler;
freely distributing the Enhanced SNACC Compiler; and providing a copy
of the GPL along with the Enhanced SNACC Compiler.  

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Enhanced SNACC Library License Information:

DigitalNet has clearly marked all enhancements made to the original SNACC
Library as required by the license information included in each source code 
file.  DigitalNet has retained the license information in original form in 
each source code file.  None of the GNU public licenses apply to the Enhanced 
SNACC Library software.  

The United States Government/Department of Defense/National Security 
Agency/Office of Network Security (collectively "the U.S. Government") 
hereby grants permission to any person obtaining a copy of the Enhanced
SNACC Library source and object files (the "Enhanced SNACC Library
Software"), or any portions thereof, to do the following, subject to the 
following license conditions:

1. You may, free of charge and without additional permission from the 
U.S. Government, use, copy, modify, sublicense and otherwise distribute the
Enhanced SNACC Library Software or components of the Enhanced SNACC Library
Software, with or without modifications developed by you and/or by others.

2. Furthermore, if you distribute the Enhanced SNACC Library Software or
parts of the Enhanced SNACC Library Software, with or without modifications 
developed by you and/or others, then you must either make available the 
source code to all portions of the Enhanced SNACC Library Software (exclusive
of any modifications made by you and/or by others) upon request, or instead
you may notify anyone requesting the Enhanced SNACC Library Software source 
code that it is freely available from the U.S. Government.

3. Transmission of this Enhanced SNACC Software Public License must accompany
whatever portions of the Enhanced SNACC Library Software you redistribute.  
If you do not redistribute the Enhanced SNACC Compiler Software, or any
portion thereof, you do not need to include the GNU General Public License.

4. The Enhanced SNACC Library Software is provided without warranty or 
guarantee of any nature, express or implied, including without limitation
the warranties of merchantability and fitness for a particular purpose.

5. The U.S. Government cannot be held liable for any damages either 
directly or indirectly caused by the use of the Enhanced SNACC Library 
Software.

6. It is not permitted to copy, sublicense, distribute or transfer any of 
the Enhanced SNACC Library Software except as expressly indicated herein. 
Any attempts to do otherwise will be considered a violation of this 
License and your rights to the Enhanced SNACC Library Software will be voided.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

GNU General Public License

(retrieved from http://www.gnu.org/copyleft/gpl.html)


		    GNU GENERAL PUBLIC LICENSE
		       Version 2, June 1991

 Copyright (C) 1989, 1991 Free Software Foundation, Inc.
                       59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

			    Preamble

  The licenses for most software are designed to take away your
freedom to share and change it.  By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it.  (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.)  You can apply it to
your programs, too.

  When we speak of free software, we are referring to freedom, not
price.  Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

  For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have.  You must make sure that they, too, receive or can get the
source code.  And you must show them these terms so they know their
rights.

  We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

  Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software.  If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

  Finally, any free program is threatened constantly by software
patents.  We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary.  To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

  The precise terms and conditions for copying, distribution and
modification follow.

		    GNU GENERAL PUBLIC LICENSE
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License.  The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language.  (Hereinafter, translation is included without limitation in
the term "modification".)  Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope.  The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

  1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

  2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

    a) You must cause the modified files to carry prominent notices
    stating that you changed the files and the date of any change.

    b) You must cause any work that you distribute or publish, that in
    whole or in part contains or is derived from the Program or any
    part thereof, to be licensed as a whole at no charge to all third
    parties under the terms of this License.

    c) If the modified program normally reads commands interactively
    when run, you must cause it, when started running for such
    interactive use in the most ordinary way, to print or display an
    announcement including an appropriate copyright notice and a
    notice that there is no warranty (or else, saying that you provide
    a warranty) and that users may redistribute the program under
    these conditions, and telling the user how to view a copy of this
    License.  (Exception: if the Program itself is interactive but
    does not normally print such an announcement, your work based on
    the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole.  If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works.  But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

  3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

    a) Accompany it with the complete corresponding machine-readable
    source code, which must be distributed under the terms of Sections
    1 and 2 above on a medium customarily used for software interchange; or,

    b) Accompany it with a written offer, valid for at least three
    years, to give any third party, for a charge no more than your
    cost of physically performing source distribution, a complete
    machine-readable copy of the corresponding source code, to be
    distributed under the terms of Sections 1 and 2 above on a medium
    customarily used for software interchange; or,

    c) Accompany it with the information you received as to the offer
    to distribute corresponding source code.  (This alternative is
    allowed only for noncommercial distribution and only if you
    received the program in object code or executable form with such
    an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it.  For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable.  However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

  4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License.  Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

  5. You are not required to accept this License, since you have not
signed it.  However, nothing else grants you permission to modify or
distribute the Program or its derivative works.  These actions are
prohibited by law if you do not accept this License.  Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

  6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions.  You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

  7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all.  For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

  8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded.  In such case, this License incorporates
the limitation as if written in the body of this License.

  9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time.  Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number.  If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation.  If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

  10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission.  For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this.  Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.

			    NO WARRANTY

  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

		     END OF TERMS AND CONDITIONS

	    How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

    <one line to give the program's name and a brief idea of what it does.>
    Copyright (C) 19yy  <name of author>

    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; either version 2 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program; if not, write to the Free Software
    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA


Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

    Gnomovision version 69, Copyright (C) 19yy name of author
    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License.  Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary.  Here is a sample; alter the names:

  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
  `Gnomovision' (which makes passes at compilers) written by James Hacker.

  <signature of Ty Coon>, 1 April 1989
  Ty Coon, President of Vice

This General Public License does not permit incorporating your program into
proprietary programs.  If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library.  If this is what you want to do, use the GNU Library General
Public License instead of this License.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
For further information, contact:

John Pawling, John.Pawling <at> DigitalNet.com
DigitalNet Government Solutions, LLC

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Gmane