Slaptažodžių tvarkyklės saugyklos blokavimas: pamestas 1 slaptažodžio slaptasis raktas, „Bitwarden 2FA“ atkūrimo kodas arba „KeePass“ raktinis failas (talpykloje esančių vietinių neprisijungus saugyklos seansų ištraukimas)¶

Užrakinimas prie slaptažodžių tvarkytuvės (1Password, Bitwarden, KeePassXC, Proton Pass, arba LastPass) po nešiojamojo kompiuterio pagrindinės plokštės gedimo, telefono gamyklinių parametrų atkūrimo, naršyklės profilio išvalymo arba atsitiktinio praradimo 1Password 34 simbolių slaptasis raktas (A3-XXXXXX-...), Bitwarden Dviejų žingsnių prisijungimo atkūrimo kodas arba KeePass .keyx Keyfile yra rimta skaitmeninės tapatybės krizė. Šiuolaikinės nulinių žinių slaptažodžių tvarkyklės užšifruoja jūsų saugyklą jūsų įrenginyje naudodami AES-256-GCM arba ChaCha20-Poly1305 derived through PBKDF2-HMAC-SHA256 arba Argon2id before a single byte ever touches the cloud. Because the provider never possesses your Master Password, Secret Key, or local keyfile, customer support at AgileBits (1Password) or Bitwarden cannot reset your password or decrypt your vault from their servers under any circumstances.

However, a cloud login lockout almost never means your passwords are gone forever. As long as even one previously logged-in device (an old phone, a secondary tablet, a work laptop, a work browser profile, an iCloud or Google Drive device backup, or a Windows Volume Shadow Copy / macOS Time Machine disk snapshot) still holds a locally cached encrypted database (1Password.sqlite, Bitwarden data.json, arba .kdbx replica) and you still know your Master Password (or have biometric Touch ID / Face ID / Windows Hello configured on that secondary device), you can unlock that local offline cache in Airplane Mode and export 100 percent of your passwords before the cloud server revokes the session token. For related credential emergencies, see password manager lockout and master password recovery, authenticator app TOTP lost during phone upgrade or screen shatter, ir MFA blokavimas ir autentifikatoriaus atkūrimas. If your lockout involves an immediate life-safety or medical crisis, call your local emergency number (911 JAV ir Kanadoje, 112 visoje Europos Sąjungoje, 999 in the United Kingdom) or consult our directory of pagalbos numeriai.

Padarykite tai dabar¶

1. Put EVERY secondary computer, phone, and tablet that has ever accessed your password manager into Airplane Mode (disconnect Wi-Fi and unplug Ethernet) BEFORE waking the screen or opening the app:
2. Why network isolation is your first move: If your account session was deauthorized, your 2FA token was reset, or your subscription lapsed, the moment the 1Password arba Bitwarden app on your secondary laptop or old phone connects to the internet, it polls the remote API (my.1password.com arba identity.bitwarden.com), receives an HTTP 401 Unauthorized or session revocation signal, and automatically purges the local offline cached vault (data.json / 1Password.sqlite) from disk.
3. Keeping the device 100 percent offline forces the desktop app, mobile app, or browser extension to fall back to Offline Cache Unlock Mode, allowing you to unlock the vault using only your Master Password (or biometrics) without needing a 2FA code or new Secret Key handshake.
4. Never click "Log Out", "Remove Account", "Clear Browser Data", arba "Reinstall App" on a locked device: Logging out of the Bitwarden browser extension or 1Password desktop app immediately wipes the locally stored Secret Key property and encrypted vault blob. Leave the locked app untouched and copy its underlying application data folder to a safe backup folder first.
5. Understand which of the three lockout components you are missing:
6. Missing 1Password 34-Character Secret Key (A3-...) (while still knowing your Master Password): The Secret Key is stored in plaintext inside the local configuration database of every device where you ever signed in, inside your downloaded 1Password Emergency Kit.pdf, inside Apple Keychain (iCloud Keychain) on Mac/iOS, or inside any old device backup.
7. Missing Bitwarden 2FA Authenticator / Recovery Code (while still knowing your Master Password): Because Bitwarden's 2FA only gates server authentication (not local vault encryption), any device that already has a cached data.json vault file on disk can be unlocked offline using just your Master Password, or decrypted using open-source offline Bitwarden vault extractors (bitwarden-decrypt).
8. Missing KeePass / KeePassXC Keyfile (.key / .keyx) (while still knowing your Master Password): The keyfile is hashed via SHA-256 into the composite master key; you must recover the exact byte-for-byte file from disk sectors, Volume Shadow Copies, cloud trash, or browser/OS recent-file caches.
9. Prieš atidarydami neprisijungus pasiekiamą saugyklą antriniame įrenginyje, klonuokite jos vietinį saugyklos katalogą į išorinį USB diską: „Windows“, „MacOS“ arba „Linux“ sistemoje nukopijuokite visą %LocalAppData%\1Password, %AppData%\Bitwarden, or browser Local Extension Settings folder to a separate folder so that even if the app misfires and wipes its cache, you still have a pristine copy of the encrypted SQLite/JSON database.
10. If your only remaining logged-in device is a phone or laptop with a biometric unlock (Face ID, Touch ID, Windows Hello) and you forgot the Master Password itself: Do not reboot that device (rebooting clears the biometric key handle in RAM and forces a Master Password prompt on first unlock). Unlock the app via Face ID arba Touch ID while in Airplane Mode, open the highest-priority credentials, and manually view or copy every password immediately.
11. Search every computer, email attachment, Downloads folder, and cloud drive for "Emergency Kit" arba "bitwarden_recovery_code" right now: When 1Password first created your account, it forced a browser download of a file named 1Password Emergency Kit.pdf (or saved a Passkey/Secret Key entry into Apple Keychain Access). Run a system-wide search before assuming the key is gone.

Decision tree: password manager lockout triage and offline vault extraction¶

Follow this forensic recovery workflow based on which password manager and authentication factor you lost:

flowchart TD
    Start["Locked Out of Password Manager Vault (1Password, Bitwarden, KeePassXC, Proton Pass)"] --> IsolateNow["STEP 1: Put All Secondary Laptops, Phones, & Tablets into AIRPLANE MODE Immediately (Before Opening the App or Browser)"]

    IsolateNow --> WhichApp{"Which Password Manager & Credential Factor Is Missing?"}

    WhichApp -->|"1Password: Lost 34-Char Secret Key (A3-XXXXXX...), Still Know Master Password"| OnePassCheck{"Do You Have ANY Device Still Signed In (Or a Mac/iPhone Backup)?"}

    OnePassCheck -->|"YES: Logged-in App on Old Phone, Tablet, or PC"| Extract1PKey["Open Offline App -> Tap Account Icon -> 'Set Up Another Device' or 'View Secret Key' to Reveal Full A3-... Key (OR Extract from 1Password.sqlite / Apple Keychain)"]

    OnePassCheck -->|"NO: Only Have Time Machine, Windows Shadow Copy, or Downloads Folder"| Search1PKit["Search Disk & Backups for '1Password Emergency Kit.pdf', '1Password.sqlite', or 'opvault' / 'b5.sqlite'"]

    WhichApp -->|"Bitwarden: Lost 2FA TOTP App & 2FA Recovery Code, Still Know Master Password"| BitwardenCheck{"Is Bitwarden Desktop or Browser Extension Still Logged In on ANY Device (Offline)?"}

    BitwardenCheck -->|"YES: Cached Vault Exists on Disk"| UnlockBWOffline["Keep Device in Airplane Mode -> Unlock Local Bitwarden App/Extension With Master Password -> Export Vault to .json / .csv -> Then Reset Account & Re-Import"]

    BitwardenCheck -->|"NO: Extension Locked or Logged Out, But 'data.json' Exists on Disk/Backup"| DecryptBWJson["Copy Local 'data.json' from AppData or Browser LevelDB -> Run Offline 'bitwarden-decrypt' Python Script Using Your Master Password"]

    WhichApp -->|"KeePass / KeePassXC: Lost Keyfile (.keyx/.key) or Corrupted .kdbx"| KeePassRescue["1. Check KeePassXC '.kdbx.tmp' & Cloud Version History. 2. Search Disk for Keyfile via 'Everything' / Photorec or Windows Volume Shadow Copy (vssadmin)"]

    WhichApp -->|"Forgot Master Password Itself (Still Have Biometric Unlock Active on Phone/Laptop)"| BiometricRescue["DO NOT REBOOT DEVICE: Keep in Airplane Mode -> Unlock Vault via Face ID / Touch ID / Windows Hello -> Copy Passwords Manually"]

Phase 1: Recovering a lost 1Password Secret Key (A3-XXXXXX-...) and offline vault¶

1Password (versions 7 ir 8) uses a Two-Secret Key Derivation (2SKD) architecture: your vault encryption key (MPK) yra matematiškai išvestas sujungus jūsų Pagrindinį slaptažodį (per PBKDF2-HMAC-SHA256) with a randomly generated 128-bit Secret Key formatted as a 34-character string starting with A3- (pvz., A3-ABCDEF-GHIJKL-MNOPQR-STUVWX-YZ1234-567890). Be to A3- Secret Key, knowing your Master Password alone is mathematically insufficient to decrypt data from 1Password's servers.

However, the Secret Key is NOT secret from your own devices: every single device that has ever logged into your 1Password account stores your full A3- Secret Key on its local storage drive so you do not have to type 34 characters every morning.

Method 1: Revealing your A3- Secret Key from any signed-in phone, tablet, or computer¶

Check every smartphone, iPad, work laptop, or desktop browser where you ever used 1Password (keep the device in Airplane Mode first): 1. On 1Password 8 for iOS / Android: - Open the 1Password app -> tap your Account / Profile icon in the top-left corner -> tap Set Up Another Device (arba Manage Accounts -> [Your Account] -> Set Up Another Device). - Tap View Account Details beneath the QR code: your full A3-... Secret Key is displayed in plain text right on the screen. Write it down on paper immediately. 2. On 1Password 8 for macOS / Windows / Linux: - Open 1Password -> click your Account name in the top-left sidebar -> select Set Up Another Device... -> click secret key and sign-in address to display the exact A3-... string. 3. Inside your 1Password Vault itself: - Every 1Password account automatically generates a built-in vault item named 1Password Account (login) inside your Personal / Private vault on day one. If you can unlock 1Password offline on any device, search your vault for 1Password Account; it contains both your Master Password and your Secret Key.

Method 2: Extracting a lost 1Password Secret Key from Apple iCloud Keychain or macOS Keychain Access¶

If you ever signed into 1Password on an iPhone, iPad, or Mac using Safari or the native app, Apple's operating system automatically offers to save your 1Password sign-in details or Account Key inside Apple Keychain / Passwords: 1. On macOS Sonoma / Sequoia (macOS 14 / 15+) or iOS 17 / 18: - Open the Passwords app (or System Settings -> Passwords) and unlock with Touch ID or Face ID. - Search for 1password.com arba 1Password Account Key. - Inspect the saved username, password, or notes field: Safari and 1Password for iOS frequently store the full A3-XXXXXX-... Secret Key inside the saved credential entry for my.1password.com. 2. In macOS Keychain Access (local items / iCloud): - Paspauskite Cmd + Space, type Keychain Access, and search for 1Password, agilebits, or A3-. - Double-click any matching application password entry and check Show password.

Method 3: Extracting the A3- Secret Key or cached vault from disk (1Password.sqlite & Emergency Kit.pdf)¶

Even if the 1Password desktop app will not open or your computer is unbootable (mounted as a secondary drive or restored from a Time Machine / File History / Backblaze backup), check these exact disk locations:

Phase 2: Recovering from a Bitwarden 2FA lockout (data.json offline cache extraction and decryption)¶

If you lost your TOTP Authenticator app, hardware YubiKey, and your Bitwarden Two-Step Login Recovery Code, Bitwarden's cloud servers (vault.bitwarden.com) will refuse to let you log in on any new browser or phone. However, Bitwarden's cryptographic design gives you a critical rescue advantage: Bitwarden's 2FA only authenticates you to the web API; it is NOT part of the encryption key (masterKey / encKey) used to encrypt your local vault file (data.json).

That means if you still know your Bitwarden Master Password, and you have any computer, phone, or backup that contains a cached copy of Bitwarden's local data.json arba IndexedDB / LevelDB storage from when you were logged in, you can decrypt 100 percent of your passwords offline.

Method 1: Unlocking a still-logged-in Bitwarden app or extension in Airplane Mode¶

1. Disconnect the computer or phone from the internet completely (turn off Wi-Fi, unplug Ethernet, enable Airplane Mode on mobile).
2. Open the Bitwarden Desktop App, Browser Extension (Chrome, Brave, Edge, Firefox), or Mobile App.
3. As long as the app was in the "Locked" state (asking for your Master Password or PIN/Biometrics) rather than "Logged Out" (asking for your Email Address), typing your Master Password while offline unlocks the local cached vault immediately without asking for 2FA.
4. Immediately go to Settings -> Vault options -> Export vault (arba File -> Export Vault on Desktop), select .json (unencrypted JSON, so it exports custom fields, URIs, TOTP seeds, and folder structures), enter your Master Password, and save the .json file to an encrypted USB drive or VeraCrypt container.
5. Once you have verified that your exported .json file contains all your logins in a text editor, you can safely go to vault.bitwarden.com/#/recover-delete (arba vault.bitwarden.eu/#/recover-delete), delete the 2FA-locked cloud account, create a fresh Bitwarden account with the same email, and click Tools -> Import Data -> Bitwarden (json) to restore your entire vault in 30 seconds.

Method 2: Decrypting Bitwarden's data.json or Browser LevelDB directly from disk (bitwarden-decrypt)¶

What if the Bitwarden desktop app or browser extension will not unlock in the UI, or your computer drive is mounted from a backup, or you only have the raw application data folder?

1. Locate your local Bitwarden data.json or browser extension storage on disk (make a backup copy of the folder before touching it):

1. Verify that the encrypted vault payload is still inside data.json:
2. Open your copied data.json file in a text editor (Notepad arba VS Code).
3. Search for the strings "ciphers_ ir "encKey" (arba "masterKeyEncryptedUserKey" naujesnėje „Bitwarden“. stateVersion schemas).
4. Jei matote šimtus eilučių "2.iv|ciphertext|mac" strings under ciphers_<userId>, every single one of your passwords, notes, and TOTP seeds is sitting right inside that file, encrypted solely by your Master Password.
5. Decrypt data.json offline using bitwarden-decrypt (Open-Source Python Utility):
6. On any computer with Python 3 installed, download the audited open-source bitwarden-decrypt script (github.com/GurpreetKang/BitwardenDecrypt) which implements Bitwarden's exact PBKDF2-SHA256 / Argon2id + HKDF-Expand + AES-256-CBC-HMAC-SHA256 key hierarchy locally:

   pip install cryptography argon2-cffi
   python3 BitwardenDecrypt.py data.json --output recovered_vault.json
   

7. Enter your Bitwarden Master Password when prompted. The script derives your masterKey from your email and Master Password, decrypts your encKey (masterKeyEncryptedUserKey), and outputs a clean, human-readable recovered_vault.json containing every login, password, TOTP seed, and secure note.

Phase 3: Recovering from a KeePass arba KeePassXC Keyfile loss or .kdbx corruption¶

Unlike cloud-hosted managers, KeePass 2.x ir KeePassXC store your vault in a standalone .kdbx file (KDBX 4.x format) encrypted using a Composite Master Key. If you configured your database to require both a Master Password and a Keyfile (.key arba .keyx), KeePass hashes the exact contents of the keyfile with SHA-256 and combines that 32-byte hash with your password hash before running Argon2d/Argon2id.

1. How to find a misplaced or deleted .key / .keyx Keyfile (or image/document used as a keyfile)¶

Because losing a keyfile is equivalent to losing a 256-bit cryptographic key, you cannot brute-force a missing random keyfile; you must locate a byte-identical copy of the file: 1. Inspect KeePassXC.ini / KeePass.config.xml to see the exact last-used filename and path of the keyfile: - Often users forget which file on their computer they selected as their keyfile (many users select a random .jpg photo, .pdf document, or obscurely named file on a USB drive). - Open your local configuration file in a text editor: - KeePassXC (Windows): %AppData%\KeePassXC\keepassxc.ini (arba %LocalAppData%\KeePassXC\keepassxc.ini) -> look under [LastDatabases] arba LastKeyFiles. - KeePassXC (macOS / Linux): /Users/<Username>/Library/Application Support/KeePassXC/keepassxc.ini arba /home/<Username>/.config/keepassxc/keepassxc.ini. - KeePass 2.x (Windows): %AppData%\KeePass\KeePass.config.xml -> search for <KeyFilePath>. - Knowing the exact filename and folder path (E:\Keys\my_secret_pic.jpg) tells you which USB stick, SD card, or cloud folder to search. 2. Carve a deleted .keyx XML Keyfile from unallocated disk space in 60 seconds: - Standard KeePass / KeePassXC generated keyfiles (.keyx arba .key XML format) are tiny (< 1 KB files) that begin with a distinctive XML header:

<?xml version="1.0" encoding="utf-8"?>
<KeyFile>
    <Meta>
        <Version>1.00</Version>

2. Fixing a corrupted .kdbx database (Invalid signature arba HMACHashMismatch after power loss or cloud sync)¶

If your .kdbx file throws Not a KeePass database arba Corrupted database / HMAC mismatch after a computer crash or Google Drive / OneDrive sync conflict: 1. Look for hidden .kdbx.tmp arba .kdbx.bak atomic-write sibling files: - By default, KeePassXC uses Safe Save (Atomic Write): it writes changes to a temporary file in the same folder first, then renames it over the original .kdbx. Look in the same directory (with hidden files enabled) for any .tmp, .bak, or conflict copy (Passwords (Conflicted copy).kdbx). 2. Restore yesterday's version from Cloud Version History or Windows Shadow Copy: - If your .kdbx sits inside Dropbox, Google Drive, OneDrive, or iCloud Drive, log into the cloud web portal in your browser, right-click the .kdbx file, and select Version History norėdami atsisiųsti ankstesnę švarią versiją, kuri buvo prieš sugadinimą. 3. Paleiskite įtaisytą KeePass 2.x Repair Mode Import: - Open official KeePass 2.x on Windows -> create a brand-new blank database -> click File -> Import... -> select KeePass KDBX (2.x) (Repair Mode) -> point it at your corrupted .kdbx file and enter your Master Password. Repair Mode ignores broken stream HMAC footers and salvages every readable entry block up to the corrupted byte offset.

Phase 4: Extracting cached vaults from iOS, Android, and macOS backups (iMazing, Time Machine, ir DPAPI memory dumps)¶

What if your primary phone was lost, stolen, or factory reset, and your laptop was already wiped or logged out, leaving you with zero active live sessions? You can still extract the offline password manager vault from an iPhone local backup, macOS Time Machine snapshot, or Windows hibernation / crash dump file.

1. Extracting 1Password arba Bitwarden SQLite/JSON vaults from an iPhone or iPad backup (iMazing / idevicebackup2)¶

Whenever you back up an iPhone or iPad to a Mac or Windows PC (especially an Encrypted Local Backup in Finder or iTunes), the backup archive captures the application sandbox containers of 1Password ir Bitwarden: 1. Do NOT restore the backup onto a live internet-connected phone first: If you restore the backup onto a phone that connects to Wi-Fi during Setup Assistant, the restored app will immediately ping the cloud server and wipe its expired token. 2. Use iMazing arba iBackup Viewer on an offline computer to browse the raw backup filesystem: - Open your local iPhone backup inside iMazing (File System -> Apps -> 1Password arba Bitwarden). - For 1Password: Go to AppDomainGroup-group.com.agilebits.onepassword-ios/Library/Application Support/1Password/Data/ and extract 1Password.sqlite (arba B5.sqlite). Inside the accounts table of that SQLite file sits your plaintext A3-XXXXXX-... Secret Key. - For Bitwarden: Go to AppDomainGroup-group.com.8bit.bitwarden/Library/Preferences/ and extract group.com.8bit.bitwarden.plist. Convert the binary .plist to XML (plutil -convert xml1 group.com.8bit.bitwarden.plist) and open it in a text editor: it contains the exact same ciphers_<userId> ir masterKeyEncryptedUserKey JSON structures used by BitwardenDecrypt.py, allowing you to decrypt every password offline using your Master Password.

2. Extracting Proton Pass, Dashlane, ir LastPass offline browser caches¶

If your lockout involves Proton Pass, Dashlane, arba LastPass: - Proton Pass Offline Mode & Browser Extension Cache: Proton Pass caches an encrypted local snapshot inside Chromium IndexedDB (chrome-extension_<id>_0.indexeddb.leveldb). If you keep your laptop in Airplane Mode, open the browser, and unlock Proton Pass with your password or PIN, you can access your offline vault and export or view your credentials before reconnecting to the network. - LastPass Local Offline Cache (lpall.slp / acct.slp): On Windows (%LocalAppData%\LastPass arba %AppData%\LocalLow\LastPass) and macOS (/Users/<Username>/Library/Application Support/LastPass), LastPass stores an AES-256 encrypted local XML/SQLite cache file named after your email hash. Disconnecting Wi-Fi and signing into the LastPass browser extension with your Master Password bypasses broken multifactor authenticators and opens the local offline vault directly.

3. Dumping a still-unlocked vault from Windows RAM (Task Manager -> Create dump file) before a forced lock¶

If you realize you have forgotten your Master Password (or deleted your KeePass keyfile while the database is currently open and unlocked on your screen right now), DO NOT lock the database or close the window. 1. Even when KeePassXC, Bitwarden, arba 1Password requires you to re-type your Master Password to click the Export Vault button, the decrypted vault entries or the derived 256-bit MasterKey are currently sitting in process memory (RAM) while the vault window is unlocked. 2. First, click through your highest-priority logins on screen (email, banking, cloud accounts, domain registrar) and copy them into an encrypted text file or photograph them. 3. Už KeePass / KeePassXC: While the database is still unlocked, if you forgot the Master Password or deleted the keyfile, check whether File -> Export -> CSV works without prompting for the Master Password (in several versions of KeePassXC, exporting an already-unlocked database to CSV or HTML does not require re-entering the composite key).

Dažnai užduodami klausimai¶

Can 1Password or Bitwarden customer support unlock my vault if I send them my government passport and notarized ID?¶

No, it is mathematically impossible. Both 1Password and Bitwarden use end-to-end zero-knowledge client-side encryption. Your Master Password (and 1Password's 34-character A3- Secret Key) never leave your device and are never transmitted to their servers. Even if a court subpoenaed AgileBits or Bitwarden, or you presented a notarized passport in person at their headquarters, their servers only hold an encrypted ciphertext blob (AES-256) that cannot be decrypted without the keys stored on your own devices.

Why does disconnecting Wi-Fi (Airplane Mode) let me unlock Bitwarden without my lost 2FA code?¶

In Bitwarden's security architecture, Two-Step Login (2FA) is an authentication check enforced by the Bitwarden cloud server when downloading your encrypted vault blob over the internet; it is ne used as part of the cryptographic key that encrypts the vault itself. Once a device has logged in once, Bitwarden caches that encrypted vault locally inside data.json (or browser LevelDB) protected by your Master Password. When you keep the computer or phone in Airplane Mode, the app unlocks the local cached copy using only your Master Password and lets you export all your passwords to a .json arba .csv file.

What if I forgot my Master Password, I have no Emergency Kit, and my only open session is on my iPhone with Face ID?¶

If your iPhone or iPad still unlocks your password manager via Face ID or Touch ID, treat that phone like bomb-disposal hardware: keep it plugged into a charger, put it in Airplane Mode, and DO NOT let the battery die or reboot the phone. If the phone reboots, or if Face ID fails 3 to 5 times in a row, the app flushes the biometric decryption key from the Secure Enclave session and forces you to type your forgotten Master Password. Note that exporting a vault via Settings -> Export usually requires typing the Master Password even when unlocked via Face ID; therefore, do not try to use the bulk Export menu. Instead, unlock with Face ID and manually open each critical account entry one by one, tap the eye icon to reveal the password, and photograph or write down each password on paper.

How do I prevent a password manager lockout from ever happening again once I recover my vault?¶

Immediately after recovering your vault, implement the 3-Layer Physical + Offline Backup Rule: (1) Print two physical paper copies of your 1Password Emergency Kit (or your Bitwarden Master Password + 2FA Recovery Code) and store one in a fireproof home safe and one in a bank safe deposit box or with a trusted family member; (2) Export an encrypted backup of your vault (.kdbx or password-protected Bitwarden .json) onto two offline USB flash drives every 90 days; and (3) If you use 1Password Families arba Bitwarden Families / Enterprise, assign a trusted partner or second admin account to the **Account Recovery** role, which holds an escrow key capable of resetting a family member's forgotten Master Password or lost Secret Key.

Susiję vadovai¶

• Password manager lockout, master password loss, and vault recovery
• Authenticator app TOTP lost during phone upgrade or screen shatter
• MFA blokavimas ir autentifikatoriaus atkūrimas
• Passkey and WebAuthn device loss: synced vs. hardware-bound passkeys
• VeraCrypt, BitLocker, or Cryptomator corrupted volume header recovery
• Pagalbos numeriai pagal šalį

Šaltiniai ir oficialios rekomendacijos¶

• 1Password Official Security White Paper & Support Documentation (support.apple.com / support.1password.com/secret-key-security/ & support.1password.com/find-secret-key/): Two-Secret Key Derivation (2SKD), A3- Secret Key Storage on Authorized Devices, and Emergency Kit Recovery Procedures.
• Bitwarden Official Security & Cryptographic White Paper (bitwarden.com/help/bitwarden-security-white-paper/ & bitwarden.com/help/storage-locations/): Master Password Key Derivation (PBKDF2-SHA256 / Argon2id), Local data.json Offline Storage Locations, and Two-Step Login Recovery.
• KeePass / KeePassXC Official Documentation (keepass.info/help/base/keys.html & keepass.info/help/base/repair.html): Composite Master Key Architecture, .keyx XML Keyfile Specification, and KDBX 4.x Repair Mode Import.
• GurpreetKang Open-Source Forensic Tool (github.com/GurpreetKang/BitwardenDecrypt): Offline Decryption of Cached Bitwarden data.json Vault Files Using Known Master Passwords.