RMI secure transport provider doesn't check for expired certificates

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: P4
    • None
    • Affects Version/s: 1.4.0
    • Component/s: core-libs
    • generic
    • generic

      The JSSE-based secure RMI transport provider doesn't check whether
      the certificates in the subject's public credentials have expired.
      It needs to be updated to make this check at the start of each call,
      both on the client and server sides, and to permit calls again if
      expired certificates are replaced with valid ones.

            Assignee:
            J. Duke
            Reporter:
            J. Duke
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: