Passman backup passwords as files

[massimiliano-roehrig]

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

---

Feature request

**Which Nextcloud Version are you currently using: Nextcloud Hub 10 (31.0.7)

Is your feature request related to a problem? Please describe.
We cant backup de passwords or the vaults in user context other than doing an backup of the whole database

Describe the solution you'd like
A backup of the passwords as file backup into the users accounts, so you could sync it to other locations.

Describe alternatives you've considered
We tried to do an export via Passman, but this process consumes too much time for every password.

Additional context
/

[binsky08]

Thanks for the feature request.

May consider some of my thoughts:

• We already support import / export for a vault in user context. Just login to it, open vault setting and go to the export tab. This will create a decrypted full vault backup (as json or csv) with all "active" credentials (not the deleted ones, nor revisions). Since the decryption process in done on the client side (browser JS), the decryption takes some time for big vaults.
• atm a user's credential is technically protected by the user login (access protection that doesn't exist for admins with backend / server access), that's needed to enter a vault password (that's needed to decrypt the credentials itself), while the credentials are stored in the database with a server side encryption based on the app secret in the Nextcloud config.php - so the server side encryption protects them in DB backups, but accessing them using the corresponding models automatically decrypts them (so that we still have the e2e-encrypted data)
• I think adding a console command and an admin frontend option to backup vaults could be interesting, but shouldn't lower the security. So we never do e2e credential decryption (with a users password) on the server side.
• Since the server decrypted credential data still contains non-encrypted user data (like the non-e2e-encrypted labels ...) we should think about a server side encryption to add to the backup or just pretending the encryption of the data in the DB. (but would need the current nextcloud app secret to be backed-up also in a second way)
• adding a secure checksum to the backup over the backup data (using the nextcloud app secret as shared secret key) or something like that could be interesting (https://www.php.net/manual/en/function.hash-hmac.php)
• Another option could be a user sided backup for all its vaults, together. But to be able to restore them into another instance, they don't need to be e2e-decrypted, so we could save a lot of CPU time here.