Passphrase not shown in the new user interface

1

On a new pc I’ve imported a backup job from a file. When modifying it in the new UI, no trace of the passphrase I was able to find. I spent more than an hour trying in vain to append it as an advanced option to the backup job before recognizing that in the old UI the passphrase is present.

Is it possible?

2

Well, I’ve understood that the passphrase has been imported but not shown. In the first page of the backup job I can only see an “encrypted backup” advice.

3

For the ngclient UI we decided to not support changing the encryption passphrase, for the reason that this will not work if you already have encrypted volumes.

There is an edge case where you create the backup and want to edit the passhrase before making a backup that is not possible with ngclient.

Does this mean that it works as you want or is it still confusing/wrong?

4

Yes, it works. Thank you for your reply. Without the password being shown on screen, I kept wondering whether the job import had actually inherited it correctly.

5

Hi Kenneth

Here’s another not-so-edge (IMHO) case.

I export my configs without the passphrase (which is only in my head, zero trust principle).

In case of a total crash, I can easily restore the config, then recreate the DB. With the new UI I can no longer do this.

Therefore, I think we need this option, maybe with a nice big warning if you change it.

Alternatively, it would be wonderful if the configs were automatically backed up to the backup destination. Then, in case of a total crash, you just point Duplicati to the destination, input the passphrase, and then it automatically restores the config and rebuilds the DB.

Hope it makes sense :slight_smile:

Cheers,

Gaston

6

Clarify why not, and what happens there?

What I’m seeing is that Submit gets refused. To make it worse, the possible
workaround of adding passphrase in Advanced options still sends it blank:

  {
    "Name": "encryption-module",
    "Value": "aes"
  },
  {
    "Name": "passphrase",
    "Value": ""
  },

The workaround of using old UI to type passphrase on screen 1 seems OK.

7

Hi ts678

Because the new UI does not have a field to input the passphrase when you import the config.

Best regards,

Gaston