{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihc22jz76ihne6anj6a3kqogr5qei5olkn276ylzmxtnladgpmxyy",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mllxdw5d4u62"
  },
  "path": "/t/master-password-backup/37745#post_16",
  "publishedAt": "2026-05-11T18:57:12.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "ignoramous:\n\n> lyricism:\n>\n>> I would hope people who are privacy and security conscious would use a secure random method to generate their master passwords\n>\n> Don’t think there’s consensus on whether passwords _must_ be “securely random”\n\nAren’t generatours like that of KeePass random?\n\nignoramous:\n\n> There’s nothing about “writing it down” that’s a single point of failure. You can write (the escrow keys, not the password) those down twice and store it in two separate safe locations (like in a safe/hardware-vault). Break the (ideally, 32 byte uniformly random; 64 hex chars) escrow keys into 4 parts (of 8 bytes; 16 characters each) and store it in 8 different locations. Not saying these are what I’d do… I’d simply write down the escrow keys once, and put in a safe. Rotate (invalidate the previous escrow key for a new one) the escrow key (or the seed that generates multiple escrow keys) every once in a long while, if the scheme supports it.\n\nThis sounds way to complicated and error prone.\n\nAnd why not the real password, what is the difference with escrow keys?",
  "title": "Master Password Backup"
}