From owner-imc-snacc Mon Apr 17 06:37:14 2000 Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id GAA02013 for imc-snacc-bks; Mon, 17 Apr 2000 06:37:14 -0700 (PDT) Received: from wfhqex05.wangfed.com (netva01.wangfed.com [206.137.100.2]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id GAA02009 for ; Mon, 17 Apr 2000 06:37:12 -0700 (PDT) Received: by wfhqex05.wangfed.com with Internet Mail Service (5.5.2650.21) id ; Mon, 17 Apr 2000 09:40:48 -0400 Message-ID: <33BD629222C0D211B6DB0060085ACF31965D93@wfhqex01.wangfed.com> From: "Pawling, John" To: "'imc-snacc@imc.org'" Subject: SNACC ASN.1 Freeware Release & Mail List Date: Mon, 17 Apr 2000 09:40:43 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-imc-snacc@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: All, J. G. Van Dyke and Associates (VDA), a Wang Government Services Company, has delivered an enhanced version of the freeware SNACC v1.3 rev 0.07 Abstract Syntax Notation.1 (ASN.1) Compiler and Library. In past releases, VDA enhanced the C++ version of the SNACC library to implement the Distinguished Encoding Rules (DER). In the new release, VDA enhanced the C and C++ versions of the SNACC library to support PrintableString, TeletexString, NumericString, IA5String, VisibileString, BMPString, UniversalString and UTF8String character string types. We added an optional function to SNACC that can be used to convert ASN.1 OCTET STRINGs to single- or multi-byte character strings (as appropriate). This is needed to support the RFC 2459 PKIX requirements. The SNACC enhancement is completely optional and does not impact existing code that uses SNACC. The SNACC library decodes an object as it always has. If the application/library needs the ASN.1 OCTET STRINGs converted to character strings, then it calls the new SNACC function/class to perform the conversion. If an application/library does not need the ASN.1 OCTET STRINGs converted, then it does not need to call the conversion function/classes and can use the SNACC-generated structures/classes as always. The VDA-enhanced SNACC compiler and C++ library is available along with the S/MIME Freeware Library (SFL) that uses SNACC to implement the S/MIME v3 set of specifications. The snacc1_6VDA.zip file contains the SNACC v1.3 rev 0.07 ASN.1 Compiler and C++ Library source code compilable for Unix and MS Windows NT/95/98/2000. The VDA-enhanced SNACC C library is available along with the freeware Certificate Management Library (CML) that uses SNACC to implement the 1997 X.509 Recommendation and RFC 2459. The CML17sr.tar.Z file includes the source code for the CML and VDA-enhanced SNACC C library compilable for Unix and MS Windows NT/95/98/2000. We plan to consolidate the enhancements made by VDA to the C and C++ versions of the SNACC source code into a single baseline that can be delivered in a single tar/zip file. In the new release, we also corrected a bug in the DEC_LOAD_ANYBUF macro. We changed "bytesDecoded" to "bytesDecodedXX" to avoid conflict other SNACC uses of the "bytesDecoded" variable. We also enhanced the AsnOid method so that it accepts a dynamic number of components within an object identifier. SNACC implements the majority of ASN.1 encoding/decoding rules. SNACC does not support all of the latest ASN.1 features, but there are work-arounds that allow SNACC to be used to produce ASN.1 hex encodings that are identical to those produced by ASN.1 libraries that do support the latest ASN.1 features. Also note that many of the PKIX specs, such as RFC 2459, include 1988-compliant ASN.1 syntax modules which can be directly compiled using SNACC. The SNACC ASN.1 library is totally unencumbered as stated in the SFL Public License. All source code for the VDA-enhanced SNACC software is being provided at no cost and with no financial limitations regarding its use and distribution. Organizations can use the VDA-enhanced SNACC software without paying any royalties or licensing fees. The Internet Mail Consortium (IMC) has established a SNACC web page . The IMC has also established a SNACC mail list which is used to: distribute information regarding SNACC releases; discuss SNACC-related issues; and provide a means for SNACC users to provide feedback, comments, bug reports, etc. Subscription information for the imc-snacc mail list is at the IMC web site listed above. VDA welcomes all feedback regarding the VDA-enhanced SNACC software. If bugs are reported, then VDA will investigate each reported bug and, if required, will produce a patch or an updated release of the software to repair the bug. We recommend that comments should be sent to the imc-snacc mail list. We will respond to all messages on that list. ============================================ John Pawling, Director - Systems Engineering J.G. Van Dyke & Associates, Inc; a Wang Government Services Company john.pawling@wang.com ============================================ From owner-imc-snacc Tue Apr 18 10:02:51 2000 Received: by ns.secondary.com (8.9.3/8.9.3) id KAA06449 for imc-snacc-bks; Tue, 18 Apr 2000 10:02:51 -0700 (PDT) Received: from wfhqex05.wangfed.com (netva01.wangfed.com [206.137.100.2]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA06445 for ; Tue, 18 Apr 2000 10:02:50 -0700 (PDT) Received: by wfhqex05.wangfed.com with Internet Mail Service (5.5.2650.21) id ; Tue, 18 Apr 2000 13:06:32 -0400 Message-ID: <33BD629222C0D211B6DB0060085ACF31965DBA@wfhqex01.wangfed.com> From: "Pawling, John" To: "Pawling, John" Subject: v1.6 SFL/SNACC Patch Files Date: Tue, 18 Apr 2000 13:06:21 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-imc-snacc@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: All, A bug has been reported in the v1.6 S/MIME Freeware Library (SFL) and accompanying SNACC C++ library. We strongly recommend that the patch files (described below) should be immediately incorporated into your local version of the SFL and SNACC C++ software. Much thanks to Dan Teodosescu, Foliage Software Systems, for reporting this bug. We encourage all feedback related to the SFL and SNACC software. We made the changes in the SFL and SNACC C++ baseline software as described below and successfully tested the corrected software. The corrected SFL and SNACC C++ source code files are stored on the Fortezza Developer's S/MIME Page under "sflpatch 4/18/00". We do not plan to deliver a new release of the SFL and SNACC C++ software solely to fix this bug. This bug does not impact the Certificate Management Library. We added the following text to the SFL Problem Report File available in the "sflpatch 4/18/00" zip file: SFL PROBLEM REPORT FILE 17 April 2000 This file documents errors in the v1.6 S/MIME Freeware Library (SFL) that have not yet been included in a new release of the SFL. ====================================================================== Problem Report #1 File(s) Affected: sm_buffer.h, sm_vdasnacc.cpp, sm_buffer.cpp, vdatest.cpp Date Reported: 12 April 2000 Problem Description: When the v1.6 SFL is used to create a signedData object larger than 16K bytes, then temporary files containing the signedData object are not removed from the root directory of the working drive. Platform(s) affected: All Resolution: SNACC was leaving temporary files in the root directory when any object larger than 16K was ASN.1 encoded. The sm_buffer.h, sm_vdasnacc.cpp, sm_buffer.cpp, vdatest.cpp patch files fix the problem. These files belong in the SNACC release c++-lib inc and src directories. The file "sm_buffer.h" MUST also be copied to the sfl directory "./include/snacc/c++" to be effective. There will be a few SFL baseline build errors due to the CSM_Buffer update; on each error add "(size_t)" override on the CSM_Buffer constructor parameter (there are only 8 or so errors). Baseline Source Code Fixed and Tested: 17 April 2000 For more information, contact: ============================================ John Pawling, Director - Systems Engineering J.G. Van Dyke & Associates, Inc; a Wang Government Services Company john.pawling@wang.com ============================================ From owner-imc-snacc Fri Jul 14 14:06:37 2000 Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id OAA15012 for imc-snacc-bks; Fri, 14 Jul 2000 14:06:37 -0700 (PDT) Received: from wfhqex05.wangfed.com (netva01.wangfed.com [206.137.100.2]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id OAA15008 for ; Fri, 14 Jul 2000 14:06:36 -0700 (PDT) Received: by wfhqex05.wangfed.com with Internet Mail Service (5.5.2650.21) id <3GNFB4P4>; Fri, 14 Jul 2000 17:07:41 -0400 Message-ID: <4B0D36365AD3D2118FF40060972A16C0016D013F@wfhqex01.wangfed.com> From: "Pawling, John" To: "Pawling, John" Subject: v1.3 Enhanced SNACC ASN.1 Freeware Release Date: Fri, 14 Jul 2000 17:07:42 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-imc-snacc@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: All, Wang Government Services, Inc. (WGSI), A Getronics Company, has delivered the v1.3 Enhanced SNACC Abstract Syntax Notation.1 (ASN.1) Compiler, C++ library and C library source code compilable for Sun Solaris 2.7 and Microsoft Windows NT/95/98/2000. The source code and the Enhanced SNACC Software Public License are freely available to everyone from: . In past releases, WGSI enhanced the C++ version of the SNACC library to implement the Distinguished Encoding Rules (DER). In the v1.3 SNACC release, WGSI included the following enhancements in SNACC: 1) Completed merging SNACC C and C++ enhancements made by U.S. Government and WGSI into a single source code baseline that we have delivered in a single tar file. 2) Added DER source code developed by Australian OSCAR project to SNACC C library. 3) Reconstructed and tested SNACC baseline so that all changes are documented using SourceSafe configuration management tool. 4) Resolved inconsistencies in how string types were implemented (imported versus internal) in C and C++ SNACC libraries. Changed SNACC C++ library to use same internal representation used by SNACC C library. 5) Tested C and C++ SNACC libraries on MS Windows and Solaris 2.7. 6) Tested v1.3 SNACC compiler and C++ library with the v1.7 S/MIME Freeware Library (SFL) that uses SNACC to implement the IETF S/MIME v3 set of specifications. 7) Tested v1.3 SNACC compiler, C and C++ libraries with the freeware v1.71 Certificate Management Library (CML) that uses SNACC to implement the 1997 X.509 Recommendation and RFC 2459. 8) Tested v1.3 SNACC compiler and C++ library with the freeware v1.3 Access Control Library (ACL) that uses SNACC to provide automated access control. SNACC implements the majority of ASN.1 encoding/decoding rules. SNACC does not support all of the latest ASN.1 features, but there are work-arounds that allow SNACC to be used to produce ASN.1 hex encodings that are identical to those produced by ASN.1 libraries that do support the latest ASN.1 features. Also note that many of the PKIX specs, such as RFC 2459, include 1988-compliant ASN.1 syntax modules which can be directly compiled using SNACC. The SNACC ASN.1 library is totally unencumbered as stated in the Enhanced SNACC Software Public License. All source code for the Enhanced SNACC software is being provided at no cost and with no financial limitations regarding its use and distribution. Organizations can use the Enhanced SNACC software without paying any royalties or licensing fees. The Internet Mail Consortium (IMC) has established a SNACC web page . The IMC has also established a SNACC mail list which is used to: distribute information regarding SNACC releases; discuss SNACC-related issues; and provide a means for SNACC users to provide feedback, comments, bug reports, etc. Subscription information for the imc-snacc mail list is at the IMC web site listed above. WGSI welcomes all feedback regarding the Enhanced SNACC software. If bugs are reported, then we will investigate each reported bug and, if required, will produce a patch or an updated release of the software to repair the bug. This SNACC release announcement was sent to several mail lists, but please send all messages regarding the Enhanced SNACC software to the imc-snacc mail list ONLY. Please do not send messages regarding the Enhanced SNACC software to any of the IETF mail lists. We will respond to all messages sent to the imc-snacc mail list. ============================================ John Pawling, john.pawling@wang.com Wang Government Services, Inc., A Getronics Company ============================================ From owner-imc-snacc Thu Sep 14 09:31:19 2000 Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id JAA25387 for imc-snacc-bks; Thu, 14 Sep 2000 09:31:19 -0700 (PDT) Received: from exch-bhs-2.redstone.army.mil (exch-bhs-2.redstone.army.mil [136.205.13.50]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA25383 for ; Thu, 14 Sep 2000 09:31:16 -0700 (PDT) Received: by exch-bhs-2.redstone.army.mil with Internet Mail Service (5.5.2448.0) id ; Thu, 14 Sep 2000 11:35:00 -0500 Message-ID: <1345B59AC3C5D211975E00A0C99DAC7A01B67559@exch-msg-6> From: "Nord, John D Contractor/NCCIM" To: "'imc-snacc'" Subject: little endian bug? Date: Thu, 14 Sep 2000 11:34:07 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-imc-snacc@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: I wasn't sure which list to send this to. I was thinking about sending it to all three (SNACC, SFL, and CML), but that would probably make a lot of people get three copies of it. The problem occurs in the SNACC library, but involves the SFL and CML as well. Description of bug: I'm using the DOD PKCS#12 file from the "email" link on web page http://www.disa.mil/infosec/pki-int.html. I'm using the SFL to create P7M files, and the CML to store certificates on a Windows platform. I noticed that the certificate from the P12 file (CN=Nimeh.Jamil.Joseph...) was getting added to the CML database twice. Everything about the two certificates in the CML database looked identical. However, a close inspection reveals that the certificates differ in one byte. The first byte of the certificate signature, which should be a leading '0', is correctly '0' in one certificate, but is '1' in the other certificate. The invalid certificate came from one of the P7M files created by the SFL. When the P7M file is created, the certificate is incorrectly encoded with a leading '1' instead of a leading '0' in front of the certificate signature. When my application opens the P7M, the signer's certificate (the invalid one in the P7M) is added to the CML database, so that both the valid and invalid certificates are now present. The call stack at the point at which the signature is encoded is: AsnBits::BEncContent(AsnBuf & {...}) Certificate::BEncContent(AsnBuf & {...}) CertificateChoices::BEncContent(AsnBuf & {...}) CertificateSet::BEncContent(AsnBuf & {...}) SignedData::BEncContent(AsnBuf & {...}) SignedData::BEnc(AsnBuf & {...}) SignedData::BEncPdu(AsnBuf & {...}, unsigned int &) CSM_DataToSign::Sign(CSMIME *, CSM_MsgCertCrls *, CSM_Buffer * &) CSM_MsgToSign::UpdateSignedDataSIs(CSMIME *) CSM_MsgToSign::Sign(CSMIME *) At the beginning of the function "AsnBits::BEncContent", the 'bitLen' member is 1024, the length of the signature. At line 274 (in snacc13rn\c++-lib\src\asn-bits.cpp) of this function, there is a sequence of statements intended to remove leading '0' bits from the bit sequence. However, the code begins looking at the LEAST significant byte of the signature instead of the most significant byte. To illustrate this, the bottom of the certificate cut from an ASN.1 view looks like: 30 0d 06 09