From d2bb32bb0ebb4fb62edaaba5a75c4bcd8c8678f1 Mon Sep 17 00:00:00 2001
From: Ian Grigg .x will change to .1 in the first approved instance.
@@ -573,8 +564,6 @@ for these applications:
in any application that requires or expects identity.
-
-
@@ -1213,8 +1202,6 @@ Email addresses are verified according to
§4.2.2.
@@ -1550,10 +1537,6 @@ Each Member is assured according to Assurance Policy
(COD13).
Certificates.
Based on the total number of Assurance Points
@@ -1992,8 +1975,6 @@ and the Organisation Handbook.
@@ -2409,7 +2390,6 @@ or servers within that organisation,
but the Organisation is the responsible person.
Software Agent.
If a Member is relying on a CAcert root embedded in
@@ -2612,8 +2592,6 @@ No stipulation.
@@ -2758,7 +2736,6 @@ Roles strive in general for separation of duties, either along the lines of
Refer to Security Policy 9.1.3 (COD8).
No stipulation.
@@ -274,14 +273,6 @@ for each class of certificate.
and must disappear in the POLICY.
1.4.4. Limited certificate uses
3.1.3. Anonymity or pseudonymity of subscribers
4.3. Certificate issuance
-
-
4.3.1. CA actions during certificate issuance
5. FACILITY, MANAGEMENT, AND OPERATIONAL CONTROLS
-
-
5.1. Physical controls
5.3.3. Training requirements
6. TECHNICAL SECURITY CONTROLS
-
-
6.1. Key Pair Generation and Installation
6.1.1. Key Pair Generation
@@ -3050,8 +3025,6 @@ This is effected by means of the 'template' system.
-
-
6.2. Private Key Protection and Cryptographic Module Engineering Controls
@@ -3426,8 +3399,6 @@ networks, law (including multijurisdictional issues),
identity systems, fraud, IT management.
Code Auditors. See Security Policy, sections 7, 9.1. @@ -3622,7 +3593,6 @@ or rulings by Arbitrator.
Privacy is covered by the CCA (COD9) @@ -3697,8 +3667,6 @@ and the commitment to security of Members, some deviations are necessary.
- -