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.

1 files changed, 0 insertions, 71 deletions

diff --git a/lib/asn1/test/asn1_SUITE_data/x420/GULSProtectionMappings.asn b/lib/asn1/test/asn1_SUITE_data/x420/GULSProtectionMappings.asn
deleted file mode 100644
index 9b6a426ca2..0000000000
--- a/lib/asn1/test/asn1_SUITE_data/x420/GULSProtectionMappings.asn
+++ /dev/null
@@ -1,71 +0,0 @@
--- Module GULSProtectionMappings (X.830:04/1995)
-
-GULSProtectionMappings {joint-iso-itu-t genericULS(20) modules(1)
-  gulsProtectionMappings(5)} DEFINITIONS AUTOMATIC TAGS ::=
-BEGIN
-
--- These protection mappings are more versatile that the
--- preceding protection mappings which were specifically designed
--- to generate identical bit-encodings as the Directory
--- Authentication Framework parameterized types.
--- EXPORTS All 
-IMPORTS
-  notation, gulsSecurityTransformations
-    FROM ObjectIdentifiers {joint-iso-itu-t genericULS(20) modules(1)
-      objectIdentifiers(0)}
-  PROTECTION-MAPPING
-    FROM Notation notation
-  dirEncryptedTransformation, gulsSignedTransformation{},
-    gulsSignatureTransformation, symmetricKeyInformation,
-    asymmetricKeyInformation
-    FROM GulsSecurityTransformations gulsSecurityTransformations;
-
--- ********************************** 
--- confidentiality Protection Mapping 
--- ********************************** 
--- This protection mapping enables the notation
--- PROTECTED {BaseType, confidentiality}
--- to map to either dirEncryptedTransformation or to no transformation
--- at the choice of the encoding system, dependent upon local security
--- policy and other local environment considerations.
--- Security Service:  confidentiality
-confidentiality PROTECTION-MAPPING ::= {
-  SECURITY-TRANSFORMATION  {dirEncryptedTransformation}
-  BYPASS-PERMITTED         TRUE
-}
-
--- ****************************** 
--- GULS signed Protection Mapping 
--- ****************************** 
--- This protection mapping causes the notation
--- PROTECTED {BaseType, signed}
--- to map to the gulsSignedTransformation.
--- Security Service:  data origin authentication, data integrity and
--- (in certain situations) non-repudiation.
-signed PROTECTION-MAPPING ::= {
-  SECURITY-TRANSFORMATION
-    {gulsSignedTransformation
-       {{symmetricKeyInformation | asymmetricKeyInformation}}}
-}
-
--- ********************************* 
--- GULS signature Protection Mapping 
--- ********************************* 
--- This protection mapping causes the notation
--- PROTECTED {BaseType, signature}
--- to map to the gulsSignatureTransformation.
--- Security Service:  data origin authentication, data integrity and
--- (in certain situations) non-repudiation.
-signature PROTECTION-MAPPING ::= {
-  SECURITY-TRANSFORMATION
-    {gulsSignatureTransformation
-       {{symmetricKeyInformation | asymmetricKeyInformation}}}
-}
-
-END
-
--- Generated by Asnp, the ASN.1 pretty-printer of France Telecom R&D
-
-
--- content of stack:
---