<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2/27/19 6:42 PM, Paul F Fraser
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:90699fc4-f672-7620-6754-51ec2c2a9a7b@a2zliving.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Trying to work out for my project, how best to handle a master
password for relatives and others to access data after death,
including data about ongoing subscriptions etc.. </blockquote>
<p>My advice? Change how we manage passwords. (No, I'm not
ambitious...)<br>
</p>
<p>First, don't recycle passwords between different sites. Okay, I
just lost 99.8% of my audience.<br>
</p>
<p>Second, people should write down their passwords on paper. All
analogue, no electronic-anything involved (because you can't trust
that stuff is working for you, and can't trust it is competent).
There goes 0.1%...<br>
</p>
<p> - Keep a backup by copying by hand, and regularly updating the
backup. And now I have lost the remaining 0.1%. (No photocopies,
they are computers these days and can't be trusted.) <br>
</p>
<p> - Protect that paper as though it were important--treat it like
cash money. For frequently used passwords you will learn them and
won't need to refer to the paper, it's not that bad.<br>
</p>
<p> - If some passwords are more critical than others put them on a
different piece of paper and treat it like a <i>lot</i> of cash
(i.e., don't carry it around with you).</p>
<p><br>
</p>
<p>Now the recovery question is much simpler: Tell your airs where
the backups are kept. (Put that in information in a sealed
envelope, if you would like.)</p>
<p><br>
</p>
<p>-kb, the Kent who is terrified of end-point security.<br>
</p>
</body>
</html>