pull down to refresh
220 sats \ 2 replies \ @lopp OP 13 Feb \ parent \ on: I'm Jameson Lopp, co-founder of Casa, AMA! AMA
The most common one is the long-term issue of not having a well vetted inheritance plan. Those who do have "a plan" usually have some convoluted "treasure map" type of system that hasn't actually be tested and usually has potential points of failure.
The biggest problem that folks run into when using Casa is not heeding our advice, ignoring our reminders, etc. For example, we'll remind you to perform a health check if you haven't used a given key in 6 months. This is just to ensure that your key is still working as expected and hasn't been lost or compromised. But we can't force anyone to maintain their key health, and so if a client ignores our messages for many years they may find themselves in for an unpleasant surprise when they finally go try to use a given key.
Those are good reminders
reply
the world could really use a comprehensive user-friendly security plan creation solution imo - determining & mitigating attack vectors in a "normie-friendly" way
while everyone's situation is a bit unique, it seems like like are commonalities or principles that could be abstracted up and offloaded from manual human research and effort. perhaps like a private local llm that figures out what attack vectors your likely exposed to through a chat interface and then recommending tangible links and steps to address
reply