Skip to content
This repository was archived by the owner on Oct 28, 2025. It is now read-only.
This repository was archived by the owner on Oct 28, 2025. It is now read-only.

Can this be packaged as a distributable EXE? (and other thoughts) #2

Description

@xenithorb

I've been waiting to use something like this for a while, but the problems are as follows:

I'm a technical person surrounded by non-techie loved ones. Anyone I would will my seed to would basically have a next-to-zero chance of restoring it with current tools that utilize SSS. Additionally, the existing tools are not standardized and thus you can not simply tell someone to use the SSS algorithm to recombine the secrets, it doesn't work because they don't all follow the same exact format or algorithm. (I blame the fact that this was never standardized). The program must encompass most if not all of the following traits:

  1. Must be easy for laymen to install: In this world that means easy on windows.
    1a. An alternative may be a small bootable ISO, but teaching someone to boot a USB can be non-trivial.
  2. Must be stable and operate predictably: instructions that I put in a will or document in a safe box should remain working years down the road, and should require minimal upkeep and maintenance to ensure that the safely stored secrets continue to work.
  3. It's likely that laypeople are using this to restore something of value from a deceased person that they presumably are close enough to in order to have the necessary secrets, the program should make it very obvious and clear (because they may be grieving and stressed) to not to use this on an internet-connected device. The program should present the user with a very clear warning of this, and the possibility that if they do this on a compromised computer they could lose everything. The program should make it clear that it would be in the best interest of themselves that they should seek technical help from a close friend of family member (a truly trusted party) if they don't understand what any of that means and why it's important.

My experience with node thus far is that what is built with it often involve a deep network of dependencies that may drastically change, fall out of availability, and generally bit-rot over time. What strategy is being used to protect against that?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions