Where does UUID that duplicacy uses to encrypt master password come from?

Since version 1.4.1 duplicacy stores master password encrypted with UUID if keyring is not available which is awesome because it absolves the users from specifying DWE_PASSWORD, instead users need to login to UI once when the installation is moved to a new machine (or container instance) to re-encrypt the credentials.

What UUID is used and how is it determined? I would like to fake and persist it in the docker container, the same way we now persist machine-id.

This UUID is basically machine-id + hostname. So if you have machine-id it should work.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.