On Tue, 30 Nov 2021 02:40:22 GMT, Valerie Peng <valer...@openjdk.org> wrote:
>> src/java.base/share/classes/java/security/Provider.java line 832: >> >>> 830: // NOTE: may need extra mechanism for providers to indicate their >>> 831: // preferred ordering of SecureRandom algorithms since registration >>> 832: // ordering info is lost once serialized >> >> Why is the ordering info lost once serialized? Weren't all entries re-added >> again in their original order? > > The serialized bytes are just the mappings, i.e. key + value pairs. There are > no ordering info associated with the key + value pair. IIRC, the particular > thing about SecureRandom is that the first registration of SecureRandom is > deemed to be the most preferred. However, if given only the serialized bytes, > the entries are added based on the resulting order stored by the parent > class, not necessarily the ordering of the initial insertion/add calls. I see. How about serializing `prngAlgos` as a list? ------------- PR: https://git.openjdk.java.net/jdk/pull/6513
