0

This may be a little unnecessary, but taking into consideration:

  • There are many ways to hack a computer
  • There are many ways to hack a network
  • There is always a possibility of an undetected malware on a device
  • You can't be by your computer 24/7, leaving time for others to (possibly) hack your hardware
  • There is the possibility of an unknown exploit in a software or algorithm
  • There is the possibility of someone tampering with your device before you even buy it
  • There is the possibility of the government placing backdoors in common hardware
  • The government works with various companies that have access to your data (such as Google [Google Chrome & Android], Microsoft [Windows], Apple [Mac & iPhone])
  • The high possibility the government has unknown exploits to access your computer or data

What is the best way to store a password list?


The method I am think of includes:

  • Creating a long passphrase algorithm
  • Using the passphrase algorithm to generate a password for each account
  • Splitting the passphrase algorithm into 3 sections
  • Writing down each section of the algorithm separately
  • Hiding 1 of the lists in various spots around the house
  • Hiding 1 at a relatives house (Government can't get warrant without valid reason, or tear apart a house to find a tiny piece of paper)
  • Hiding 1 in a lockbox, given to a lawyer (Government can't break attorney/client privilege)
  • Only inputting the passwords on a secure OS such as Qubes/Whonix

Can anybody think of a better method of storing passwords? (That doesn't require complete memory and is still accessible if one were to forget the passphrase algorithm)


Okay, to clarify:

To protect against:

  • A password cracker
  • Somebody with access to the hard drive for a full day but never again (in encrypted format, with the hope there is no backdoor on the hardware to begin with)
  • A government agency raid

Not taking into account:

  • Sever-side security
  • Potential backdoors in OS script (Fresh installation)

To protect:

  • Incriminating information
12
  • 1
    The method you devised does not take into consideration,that you stated in the consideration column. – yeah_well Dec 26 '20 at 13:54
  • "Most secure" -- the one thing you always need to be able to answer is "secure from what?" Once you define that, then you have something to compare against – schroeder Dec 26 '20 at 13:54
  • If it is possible to "hack" into a computer/network/account, then passwords really are not your concern. They already have the data that the password protects ... – schroeder Dec 26 '20 at 13:57
  • Okay, I clarified a bit @schroeder♦ and @yeah_well – user247973 Dec 26 '20 at 14:10
  • Where you store your password makes no difference to a password cracker. So, either your process is irrelevant or that threat is. What does "government raid" mean? If you simply mean that someone has physical access to your devices, then you can combine those 2 points. And again, that's not relevant to where you store your algorithm. – schroeder Dec 26 '20 at 14:11