Privacy-first password manager with built-in email aliasing. Fully encrypted and self-hostable.
Update models (#2159)
Leendert de Borstc08df0be916a
diff --git a/apps/browser-extension/src/utils/dist/core/models/vault/index.d.ts b/apps/browser-extension/src/utils/dist/core/models/vault/index.d.tsindex 2de9d7db1..8c1411f99 100644--- a/apps/browser-extension/src/utils/dist/core/models/vault/index.d.ts+++ b/apps/browser-extension/src/utils/dist/core/models/vault/index.d.ts@@ -1,8 +1,5 @@/**- * Encryption key SQLite database type: a manifest's email delivery keypair, stamped with the id of- * the manifest that carries it (the root manifest's own id for personal keys — resolve it from the- * Manifests bookkeeping table; there is no NULL-scope convention). Only nullable as write tolerance:- * the Rust codec adopts and restamps unstamped rows at the next sync boundary.+ * Encryption key SQLite database type.*/type EncryptionKey = {Id: string;diff --git a/apps/browser-extension/src/utils/dist/core/models/webapi/index.d.ts b/apps/browser-extension/src/utils/dist/core/models/webapi/index.d.tsindex 19b7c6bff..d30760d24 100644--- a/apps/browser-extension/src/utils/dist/core/models/webapi/index.d.ts+++ b/apps/browser-extension/src/utils/dist/core/models/webapi/index.d.ts@@ -444,36 +444,19 @@ type MobileLoginPollResponse = {/*** Vault key response type (account-key model). Returned by GET /v2/VaultKey/{type}.- * Carries the whole unwrap chain for one unlock method: the client derives the KEK from the unlock secret,- * unwraps the Account Key (AK), and with it unwraps the root VEK and the account (tier-1) private key.- * The SRP verifier is never returned.*/type VaultKeyResponse = {- /** The unlock method type, e.g. "password". */type: string;- /** The Account Key wrapped with this method's KEK: base64(IV ‖ ciphertext ‖ authTag), AES-256-GCM. */encryptedAccountKey: string;- /**- * The root VEK wrapped under the Account Key, or null for a transitional account converted from the- * pre-AK model — there the Account Key IS the VEK until the client performs the account-key split.- */- encryptedVek: string | null;- /** The account public key (tier-1, grant wrapping), or null before the account-key split. */- accountPublicKey: string | null;- /** The account private key wrapped under the Account Key, or null before the account-key split. */encryptedAccountPrivateKey: string | null;- /** The salt used for KEK derivation (same value as the SRP salt for the password key type). */+ accountPublicKey: string | null;+ encryptedVek: string | null;salt: string;- /** The key derivation type, e.g. "Argon2Id". */encryptionType: string;- /** The key derivation settings as a JSON string. */encryptionSettings: string;};/**- * Envelope returned by GET /v2/VaultKey/{type} with HTTP 200. A null vaultKey means the user has no vault key- * of the requested type (legacy user). An HTTP 404 on the endpoint itself means the server does not implement- * vault keys at all (older server version) and must be treated differently: fall back to any locally cached- * encrypted VEK instead of assuming a legacy account.+ * Envelope returned by GET /v2/VaultKey/{type} with HTTP 200.*/type VaultKeyGetResponse = {vaultKey: VaultKeyResponse | null;diff --git a/apps/mobile-app/android/app/src/main/java/net/aliasvault/app/vaultstore/models/VaultDataBucketCategory.kt b/apps/mobile-app/android/app/src/main/java/net/aliasvault/app/vaultstore/models/VaultDataBucketCategory.ktindex c7123076c..e97c474d5 100644--- a/apps/mobile-app/android/app/src/main/java/net/aliasvault/app/vaultstore/models/VaultDataBucketCategory.kt+++ b/apps/mobile-app/android/app/src/main/java/net/aliasvault/app/vaultstore/models/VaultDataBucketCategory.kt@@ -14,13 +14,8 @@ object VaultDataBucketCategory {*/const val SETTINGS = "Settings"- /**- * The user's asymmetric keypairs, which are used for both email decryption and to unwrap shared-folder VEKs.- */- const val ENCRYPTION_KEYS = "EncryptionKeys"-/*** All known data bucket categories.*/- val all = listOf(SETTINGS, ENCRYPTION_KEYS)+ val all = listOf(SETTINGS)}diff --git a/apps/mobile-app/ios/VaultModels/VaultDataBucketCategory.swift b/apps/mobile-app/ios/VaultModels/VaultDataBucketCategory.swiftindex 8b77228fe..b2d20b742 100644--- a/apps/mobile-app/ios/VaultModels/VaultDataBucketCategory.swift+++ b/apps/mobile-app/ios/VaultModels/VaultDataBucketCategory.swift@@ -10,9 +10,6 @@ public struct VaultDataBucketCategory {/// User client settings (sort order, autofill prefs, identity defaults, etc.).public static let settings = "Settings"- /// The user's asymmetric keypairs, which are used for both email decryption and to unwrap shared-folder VEKs.- public static let encryptionKeys = "EncryptionKeys"-/// All known data bucket categories.- public static let all = [settings, encryptionKeys]+ public static let all = [settings]}diff --git a/apps/mobile-app/utils/dist/core/models/vault/index.d.ts b/apps/mobile-app/utils/dist/core/models/vault/index.d.tsindex 2de9d7db1..8c1411f99 100644--- a/apps/mobile-app/utils/dist/core/models/vault/index.d.ts+++ b/apps/mobile-app/utils/dist/core/models/vault/index.d.ts@@ -1,8 +1,5 @@/**- * Encryption key SQLite database type: a manifest's email delivery keypair, stamped with the id of- * the manifest that carries it (the root manifest's own id for personal keys — resolve it from the- * Manifests bookkeeping table; there is no NULL-scope convention). Only nullable as write tolerance:- * the Rust codec adopts and restamps unstamped rows at the next sync boundary.+ * Encryption key SQLite database type.*/type EncryptionKey = {Id: string;diff --git a/apps/mobile-app/utils/dist/core/models/webapi/index.d.ts b/apps/mobile-app/utils/dist/core/models/webapi/index.d.tsindex 19b7c6bff..d30760d24 100644--- a/apps/mobile-app/utils/dist/core/models/webapi/index.d.ts+++ b/apps/mobile-app/utils/dist/core/models/webapi/index.d.ts@@ -444,36 +444,19 @@ type MobileLoginPollResponse = {/*** Vault key response type (account-key model). Returned by GET /v2/VaultKey/{type}.- * Carries the whole unwrap chain for one unlock method: the client derives the KEK from the unlock secret,- * unwraps the Account Key (AK), and with it unwraps the root VEK and the account (tier-1) private key.- * The SRP verifier is never returned.*/type VaultKeyResponse = {- /** The unlock method type, e.g. "password". */type: string;- /** The Account Key wrapped with this method's KEK: base64(IV ‖ ciphertext ‖ authTag), AES-256-GCM. */encryptedAccountKey: string;- /**- * The root VEK wrapped under the Account Key, or null for a transitional account converted from the- * pre-AK model — there the Account Key IS the VEK until the client performs the account-key split.- */- encryptedVek: string | null;- /** The account public key (tier-1, grant wrapping), or null before the account-key split. */- accountPublicKey: string | null;- /** The account private key wrapped under the Account Key, or null before the account-key split. */encryptedAccountPrivateKey: string | null;- /** The salt used for KEK derivation (same value as the SRP salt for the password key type). */+ accountPublicKey: string | null;+ encryptedVek: string | null;salt: string;- /** The key derivation type, e.g. "Argon2Id". */encryptionType: string;- /** The key derivation settings as a JSON string. */encryptionSettings: string;};/**- * Envelope returned by GET /v2/VaultKey/{type} with HTTP 200. A null vaultKey means the user has no vault key- * of the requested type (legacy user). An HTTP 404 on the endpoint itself means the server does not implement- * vault keys at all (older server version) and must be treated differently: fall back to any locally cached- * encrypted VEK instead of assuming a legacy account.+ * Envelope returned by GET /v2/VaultKey/{type} with HTTP 200.*/type VaultKeyGetResponse = {vaultKey: VaultKeyResponse | null;