Derby
  1. Derby
  2. DERBY-2409

Connecting to an already booted database with (re)encryption attributes gives no error or warning

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Duplicate
    • Affects Version/s: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0
    • Fix Version/s: None
    • Component/s: Store
    • Urgency:
      Normal
    • Issue & fix info:
      Repro attached

      Description

      If a database is shutdown and booted with (re)encryption,
      the (re)encryption boot will silently fail (i.e. no (re)encryption takes place), if another
      connection has booted the database in the meantime.

      Presumably, if the database was encrypted at creation time, only the dba will
      have the bootpassword and the above scenario is less likely.

      If it was created unencrypted, is is more of a hole, IMHO: Any other connection
      can then foil the encryption boot, even one which can not be authenticated,
      cf DERBY-2407. To further exacerbate this issue; when the database is shutdown
      and rebooted, using the boot password supplied (and the database was not encrypted),
      no error is given, since a boot password is not required. This can lull a dba
      into thinking the encryption took place!

      We may want to generate a warning or an error in these cases.

      This issue may affect upgrade boots as well?

      1. ij-repro.log
        0.8 kB
        Dag H. Wanvik

        Issue Links

          Activity

          Hide
          Dag H. Wanvik added a comment -

          The last tidbit may merit its own issue: A superfluous bootPassword
          (in a plain boot of an existing, already encrypted database) is also ignored.
          Data point: In contrast, a superfluous 'create=true' will give a warning.

          Show
          Dag H. Wanvik added a comment - The last tidbit may merit its own issue: A superfluous bootPassword (in a plain boot of an existing, already encrypted database) is also ignored. Data point: In contrast, a superfluous 'create=true' will give a warning.
          Hide
          Dag H. Wanvik added a comment -

          A small ij repro attached.

          Show
          Dag H. Wanvik added a comment - A small ij repro attached.
          Hide
          Rick Hillegas added a comment -

          Triaged for 10.5.2: assigned normal urgency and noted that a repro is available.

          Show
          Rick Hillegas added a comment - Triaged for 10.5.2: assigned normal urgency and noted that a repro is available.
          Hide
          Mike Matrigali added a comment -

          derby 10.9 triage.

          Show
          Mike Matrigali added a comment - derby 10.9 triage.
          Hide
          Knut Anders Hatlen added a comment -

          This is fixed on trunk as DERBY-5969. Resolving this issue as a duplicate.

          Show
          Knut Anders Hatlen added a comment - This is fixed on trunk as DERBY-5969 . Resolving this issue as a duplicate.
          Hide
          Knut Anders Hatlen added a comment -

          [bulk update] Close all resolved issues that haven't been updated for more than one year.

          Show
          Knut Anders Hatlen added a comment - [bulk update] Close all resolved issues that haven't been updated for more than one year.

            People

            • Assignee:
              Unassigned
              Reporter:
              Dag H. Wanvik
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development