-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can this be packaged as a distributable EXE? (and other thoughts) #2
Comments
Do you find a docker alternative better? I am wondering if people are more and more going to share their work using docker. |
I don't think so really... I'm talking more about passing the "wife test" or the "grandma test" - in general, thinking about how to pass along secrets to computer laymen in such a way that doesn't necessitate much know how and technical prowess |
The usual trade-off is web-based I fear. Or some phone app to make it worst. |
That's why I asked for something like a self-contained .exe:
|
Hi, thanks for your comments. I can also see a need for something that is more aimed at laypersons in case of death. However the intention when I was not to protect against death , but for loss of my hw device. In that case I could just ask my friends and family for their shards. That being said, pull requests are of course very welcome :) |
Possible to use something like this to create standalone exe? |
@VM81 Cool, that looks promising. Will check it out when I have more time. |
@VM81 added som simple binaries using pkg :) |
@oed Awesome, will you be uploading them to github? |
@oed working good on Windows 10, thanks! |
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:
1a. An alternative may be a small bootable ISO, but teaching someone to boot a USB can be non-trivial.
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?
The text was updated successfully, but these errors were encountered: