|
138 | 138 | import sun.security.provider.NativePRNG; |
139 | 139 | import sun.security.x509.OIDMap; |
140 | 140 |
|
141 | | -/// AR-002-security-providers: Security Provider Architecture |
| 141 | +/// AR-001-security-providers: Security Provider Architecture |
142 | 142 | /// |
143 | 143 | /// The feature records at image build time which security providers the JDK may construct, which |
144 | 144 | /// provider services reflection may instantiate, and which application-created providers JCE may |
|
152 | 152 | /// instantiated Provider subtype -----> application-provider verification only |
153 | 153 | /// ``` |
154 | 154 | /// |
155 | | -/// The registration planner interprets reflection and instantiation signals. The catalog registrar |
156 | | -/// then records provider construction, retained services, and verification results in the layered |
157 | | -/// run-time manifest. Legacy service-driven inclusion bypasses the planner and retains only the |
158 | | -/// reached service type and its provider. |
| 155 | +/// At image build time, {@link SecurityServicesFeature#providerRegistrationPlan} interprets |
| 156 | +/// reflection metadata, and {@link SecurityProviderRegistrationPlanner#processNewProviders} |
| 157 | +/// combines it with instantiation signals. Complete plans go to |
| 158 | +/// {@link SecurityProviderCatalogRegistrar#includeProviderClass}; verification-only plans go to |
| 159 | +/// {@link SecurityProviderCatalogRegistrar#registerApplicationSuppliedProviderClass}. Legacy |
| 160 | +/// {@link SecurityServicesFeature#registerService} inclusion bypasses the planner and goes directly |
| 161 | +/// to {@link SecurityProviderCatalogRegistrar#includeProviderForLegacyService}. |
159 | 162 | /// |
160 | | -/// At run time, JDK-managed provider construction consults the manifest through the acquisition |
161 | | -/// filter. An application-supplied provider object consults the same manifest only for JCE |
162 | | -/// verification; supplying an existing instance does not require reflective provider construction. |
| 163 | +/// At run time, {@link SecurityProviderRuntimeAccess#isJdkAcquirable} gates JDK-managed provider |
| 164 | +/// construction. Application-supplied provider objects instead use |
| 165 | +/// {@link com.oracle.svm.core.jdk.JceProviderVerificationSupport#getVerificationResult |
| 166 | +/// getVerificationResult} for JCE verification; they do not require reflective construction. |
163 | 167 | /// This architecture implements §FS-002-security-providers. |
164 | 168 | /// |
165 | 169 | /// ## 1. Supported Transition Modes |
|
0 commit comments