Browse Source
Bitwarden cloud rejects SSH key ciphers (type 5) where privateKey, publicKey, or keyFingerprint is null or empty, returning a validation error. Vaultwarden previously accepted such payloads and returned a success response, but the read path (src/db/models/cipher.rs) would silently nullify the invalid sshKey object, causing silent data loss. This adds matching validation on the create/update path so invalid ciphers are rejected with an error rather than appearing to succeed while losing data on reload. Fixes #7514pull/7833/head
1 changed files with 13 additions and 0 deletions
Loading…
Reference in new issue