Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8246613

Choose the default SecureRandom algo based on registration ordering

    Details

    • Subcomponent:
    • Resolved In Build:
      b28
    • CPU:
      generic
    • OS:
      generic
    • Verification:
      Verified

      Backports

        Description

        Before the perf enhancement of JDK-7092821, the ordering of provider registration is maintained in a separate collection and consulted when constructing default SecureRandom objects when algorithm isn't supplied.

        As part of JDK-7092821, this separate collection is cleaned up as the parent stores the same set of values. The ordering isn't documented anywhere and is not considered part of specification. JDK-8228613 is filed and fixed so that same default SecureRandom algorithm is picked when using SUN provider.

        As it turns out, quite some 3rd party providers are affected by this default SecureRandom change as a different default algorithm is chosen when they are the most preferred providers, e.g. JDK-8246383. Thus, the default SecureRandom algo should remain the same.

        However, for long term, it'd be nice to have an official mechanism for providers to indicate which one is the default instead of relying on the ordering which is fragile.

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  valeriep Valerie Peng
                  Reporter:
                  valeriep Valerie Peng
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  10 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: