From 8a39672af4d9becac56ca069ecc107d68b202dcb Mon Sep 17 00:00:00 2001
From: Dan Gudmundsson <dgud@erlang.org>
Date: Fri, 17 Oct 2014 10:26:02 +0200
Subject: Add the other PKCS files to the rfcs test case

Changed the following from the original copies:

PKCS-5 (renamed from PKCS-v21)

PKCS-9 Import from CryptographicMessageSyntax-2009 instead
of CryptographicMessageSyntax

Since most of the files from the x420 directory are needed,
copy all of them into the rfcs directory and remove the
x420 directory and test case. Copy the test of OTP-7759 to
the testRfcs test case.
---
 .../rfcs/DirectoryProtectionMappings.asn1          | 70 ++++++++++++++++++++++
 1 file changed, 70 insertions(+)
 create mode 100644 lib/asn1/test/asn1_SUITE_data/rfcs/DirectoryProtectionMappings.asn1

(limited to 'lib/asn1/test/asn1_SUITE_data/rfcs/DirectoryProtectionMappings.asn1')

diff --git a/lib/asn1/test/asn1_SUITE_data/rfcs/DirectoryProtectionMappings.asn1 b/lib/asn1/test/asn1_SUITE_data/rfcs/DirectoryProtectionMappings.asn1
new file mode 100644
index 0000000000..37c6cac261
--- /dev/null
+++ b/lib/asn1/test/asn1_SUITE_data/rfcs/DirectoryProtectionMappings.asn1
@@ -0,0 +1,70 @@
+-- Module DirectoryProtectionMappings (X.830:04/1995)
+
+DirectoryProtectionMappings {joint-iso-itu-t genericULS(20) modules(1)
+  dirProtectionMappings(4)} DEFINITIONS AUTOMATIC TAGS ::=
+BEGIN
+
+-- These protection mappings generate bit-compatible encodings
+-- to the parameterized types in the Directory Authentication
+-- Framework
+-- EXPORTS All 
+IMPORTS
+  notation, gulsSecurityTransformations
+    FROM ObjectIdentifiers {joint-iso-itu-t genericULS(20) modules(1)
+      objectIdentifiers(0)}
+  PROTECTION-MAPPING
+    FROM Notation notation
+  dirEncryptedTransformation, dirSignedTransformation,
+    dirSignatureTransformation
+    FROM GulsSecurityTransformations gulsSecurityTransformations;
+
+-- ************************************** 
+-- Directory encrypted Protection Mapping 
+-- ************************************** 
+-- This protection mapping enables the notation
+-- PROTECTED {BaseType, encrypted}
+-- to replace the notation
+-- ENCRYPTED {BaseType}
+-- as provided by ITU-T Rec. X.509 | ISO/IEC 9594-8:1994, and to
+-- generate an identical bit-encoding.
+-- Security Service:  confidentiality
+encrypted PROTECTION-MAPPING ::= {
+  SECURITY-TRANSFORMATION  {dirEncryptedTransformation}
+}
+
+-- *********************************** 
+-- Directory signed Protection Mapping 
+-- *********************************** 
+-- This protection mapping enables the notation
+-- PROTECTED {BaseType, signed}
+-- to replace the notation
+-- SIGNED {BaseType}
+-- as provided by ITU-T Rec. X.509 | ISO/IEC 9594-8:1994, and to
+-- generate an identical bit-encoding.
+-- Security Service:  data origin authentication, data integrity and
+-- (in certain situations) non-repudiation.
+signed PROTECTION-MAPPING ::= {
+  SECURITY-TRANSFORMATION  {dirSignedTransformation}
+}
+
+-- ************************************** 
+-- Directory signature Protection Mapping 
+-- ************************************** 
+-- This protection mapping enables the notation
+-- PROTECTED {BaseType, signature}
+-- to provide a functionally-equivalent replacement of the notation
+-- SIGNATURE BaseType
+-- as provided by ITU-T Rec. X.509 | ISO/IEC 9594-8.
+-- Security Service:  data origin authentication, data integrity and
+-- (in certain situations) non-repudiation.
+signature PROTECTION-MAPPING ::= {
+  SECURITY-TRANSFORMATION  {dirSignatureTransformation}
+}
+
+END
+
+-- Generated by Asnp, the ASN.1 pretty-printer of France Telecom R&D
+
+
+-- content of stack:
+-- 
-- 
cgit v1.2.3