Clarify why 0 argument is ignored in SecureRandom::setSeed

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P4
    • 17
    • Affects Version/s: None
    • Component/s: security-libs

      The comment there says "as digest has not yet been initialized at that point" but `digest` is not used anymore now. The current reason is that we call `super(0)` in all SecureRandom constructors and we don't want a SecureRandom object always seeded right at the beginning. For example, when `new SecureRandom()` is called.

            Assignee:
            Weijun Wang
            Reporter:
            Weijun Wang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: