multibase
paperback
multibase | paperback | |
---|---|---|
3 | 18 | |
268 | 1,061 | |
1.5% | - | |
5.6 | 7.3 | |
6 months ago | 3 days ago | |
Rust | ||
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
multibase
-
Using Zlib-Searcher to Search the Z-Library Index for Books on the IPFS Network
> IPFS now uses base58btc exclusively
That's blatantly wrong. IPFS supports 25 different base representations (https://github.com/multiformats/multibase/blob/master/multib...).
In fact, recently, two community members decided to implement a new base encoding with emojis for fun:
https://cid.ipfs.tech/#%F0%9F%9A%80%F0%9F%AA%90%E2%AD%90%F0%...
https://github.com/multiformats/multihash supports at the very least SHA1 SHA2-256 SHA2-512 SHA3/Keccak Blake2b-256/Blake2b-512/Blake2s-128/Blake2s-256 Blake3 and Strobe. Hashes in IPFS are being standardised through the IETF and W3C https://www.ietf.org/id/draft-multiformats-multihash-05.html.
If you need rhash, you are welcome to submit a PR! We also have a grants program you can use to be rewarded for this.
-
Paperback: An encrypted paper-based backup scheme
I'm still working on the project, at the moment you need to do the following (and the recovery procedure is a bit cumbersome -- there will be a GUI at some point for all of this since ultimately the project is intended for regular people):
% paperback backup [- or the file to back up] -n [threshold] -k [number of shards to make]
The command will print out the contents of the main document QR codes since at the moment the program can't scan the QR codes in the PDFs so you need to manually input the data. Note that the QR codes don't contain Base64 since that is not an efficient way of encoding binary data using QR codes. The QR code data is all encoded in Base10 (but the recovery code can handle any base data because I use multibase[1] prefixes).
And then to recover:
% paperback recover --interactive [- or the path to output the data to]
And it will ask you for the main document data (just copy-paste it, putting an extra newline after each segment) and then the shard data (you can copy-paste the "text fallback" segments from the QR codes) and shard codewords -- also with a newline after each section section. The prompts tell you what to input
"paperback expand" (create new shards from existing ones) works the same way (and also requires --interactive).
I plan to add support for just taking the PDF file and scanning the data from it directly but it seems a bit complicated to do at the moment, and I'm presenting a talk on this project next month at Linux.conf.au so I'm working on that talk right now.
[1]: https://github.com/multiformats/multibase
-
Understanding the filenames inside .ipfs/blocks/
remove the B (which indicates the uppercase base32 encoding base from https://github.com/multiformats/multibase) and use all the rest (including the ML) as the filename, followed by .data
paperback
-
Ask HN: QR Codes Unsuitable for Storing Gigabytes and Beyond in Graphic Format?
Yes. QR codes are meant to store only a few kilobytes at most. They are not suitable for encoding gigabytes of data.
At perhaps 2KB per page, you'd need 524288 pages to store a 1GB. That's 1048 reams. Please just use an archival optical disk instead.
Even if the scheme using multiple QR codes in sequence rather than a single large code block. The paper backup implementations that use QR codes https://github.com/intra2net/paperbackup https://github.com/cyphar/paperback are only meant to be used for private key backup.
-
Horcrux: Split your file into encrypted fragments
There's a cool paper-based backup tool that also uses Shamir Secret Sharing to let you distribute a bunch of paper copies to your friends to restore a file optically:
https://github.com/cyphar/paperback
- Paper backup generator suitable for long-term storage
-
I need to store a 1MB file for 20 years, would making thousands of copies on a 4.7gb DVD be enough?
Paperback will do it automatically for you, open source and free. Thier README also has recommendations for long term storage of paper.
-
PaperAge –easy and secure paper backups of (smallish) secrets
That exists: https://github.com/cyphar/paperback (or the paper-store script suggested by /u/nurupoga/ below).
-
converting data into text files
there are ready-made solutions for that, like https://github.com/cyphar/paperback
-
My biggest concern about Bitcoin, help ease it for me?
You could encrypt your key info using paperback. This then requires at least X amount of people holding parts of the decrypt key to come together to decrypt your last will.
- Is there a way to create an encryption key, that is calculabe if only 3 of 4 parts are available?
-
Man, I feel bad for Ina. Hopefully the EN curse cuts her some slack soon.
I know you're joking but there's actually software that was made just for that
- How to protect your data from an EMP?
What are some alternatives?
multihash - Self describing hashes - for future proofing
MultiPar - Parchive tool
horcrux - Split your file into encrypted fragments so that you don't need to remember a passcode
AONT-RS - An implementation of Resch and Plank's AONT-RS (All or Nothing Transform + Reed-Solomon) information dispersal algorithm.
a-search-of-hogwarts - Tool for searching through the 7 Harry Potter books (Potter Search)
clevis - Automated Encryption Framework
paper-store - Cold store small files on paper as QR codes -- PGP keys, Bitcoin keys, Tox keys or any other small files in general.
exordia - EXOrDIA
paper-age - Easy and secure paper backups of secrets
dorst - Codebase bootstrap/backup utility
horcrux
sss-cli - Command line program for secret-sharing strings