Earlier quoted context omitted.
Thus defeating the entire purpose! Unless you plan to wipe your router's firmware after every one.
The CNC router's firmware? The CNC controller itself is dumb as hell. It's connected via serial to an old offline computer that's only job is to pipe G-code over RS-232. Not even to "load a program" to hold in memory on the controller. Literally to stream the commands to the machine.
Show HN: PunchCard Key Backup
31–40 of 51 posts
Re: Show HN: PunchCard Key Backup
#32I like the survivability, and the constraint to be doable with common hand tools. For more information density, and easier readability by a less-technical person who inherits it -- at the cost of requiring special tools -- I wonder about using number&letter stamps with a hammer. Or, if you permit very special tools, laser-cut alphanumerics (base16, base58, or base64, for arbitrary bits; or alphabetic passphrases). Ei…
Re: Show HN: PunchCard Key Backup
#33Wouldn't printing a QR code be way easier? If it's just for retro fun / Rube Goldberginess than nevermind, carry on :)
Re: Show HN: PunchCard Key Backup
#34Re: Show HN: PunchCard Key Backup
#35Earlier quoted context omitted.
The CNC router's firmware? The CNC controller itself is dumb as hell. It's connected via serial to an old offline computer that's only job is to pipe G-code over RS-232. Not even to "load a program" to hold in memory on the controller. Literally to stream the commands to the machine.
My CNC controller has an SD card, Wifi, Bluetooth, and USB. They're not all the same.
Re: Show HN: PunchCard Key Backup
#36alternatively for fun use photographic chemical film paper and dark room, place plate on light source flash and capture holes on film
Steganography ideas Another fun-> divide cut plate into puzzle give pieces to different people only when puzzle combined reveals full datà
Another -> Have two or more plates with extraa binary bits holes and masking plates, when they are superimposed/stacked in proper order or aligment then uncessary bits will be masked revealing useful bits
Re: Show HN: PunchCard Key Backup
#37python -c '_secret = "d74ae47dc6f599d3f9cb847bd77d6b7c" ; print (bin(int(_secret,16))[2:])'
Re: Show HN: PunchCard Key Backup
#38I enjoyed the brevity of the python snippet required for this: python -c '_secret = "d74ae47dc6f599d3f9cb847bd77d6b7c" ; print (bin(int(_secret,16))[2:])'
Alternatively, one could use the `.rjust(128,"0")` to pad the bits, as in:
python -c '_secret = "d74ae47dc6f599d3f9cb847bd77d6b7c" ; print (bin(int(_secret,16))[2:].rjust(128,"0"))'
Re: Show HN: PunchCard Key Backup
#39Plus just place punch card on paper apply a paint with brush of better spray and you printed your holes will be printed on paper share anyone (Softcopy ツ) alternatively for fun use photographic chemical film paper and dark room, place plate on light source flash and capture holes on film Steganography ideas Another fun-> divide cut plate into puzzle give pieces to different people only when puzzle combined reveals fu…
With regard to the superimposed cards idea: this is equivalent with an "and" operation on bits, which in terms of entropy means that having one of the cards would reduce the brute force security by the amount of "0" bits (i.e. non holes in the card), because those bits can never be "1" due to superimposing.
The only safe way one can *easily* create multiple shares is through bit-wise XOR-ing:
* generate two random number, encode them into the cards, the actual secret is the XOR of the two numbers;
* K out of N is possible (I've seen some articles / StackOverflow posts), similar (though not quite exactly) to how RAID5 handles data;
Re: Show HN: PunchCard Key Backup
#40Numbered array from 1...
* using 0 as starting point would immediately trigger one's "computer science" instinct, and then it's uncertain which bit is actually bit `0`? the least significant one (as is in most cases), or the most significant one?
* by using 1 as the starting point, I hope would induce most people to just use it as a counter to number things in the "normal" (for westerners) left-to-right top-to-bottom, thus encoding / decoding is more "natural";