4 ms·
> And where it matters more, hardware compartmentalization. With the caveat that you need to use secure air-gapped communication, and you probably want to use
by infokiller 6y ago
> And where it matters more, hardware compartmentalization.
With the caveat that you need to use secure air-gapped communication, and you probably want to use Qubes on each of the separate machines as well [1].
[1] https://www.qubes-os.org/faq/#how-does-qubes-os-compare-to-using-a-separate-physical-machine https://www.qubes-os.org/faq/#how-does-qubes-os-compare-to-u...
- mirimir 6y agoRight. The Tinfoil Chat setup uses optocouplers to enforce one-way data transmission.[0] And one can use inexpensive CD-R and micro SD cards for single-use data transfer. But transferring anything but plain text is dangerous. 0) https://github.com/maqp/tfc https://github.com/maqp/tfc
- infokiller 6y agoThanks for mentioning the octocouplers implementation, it looks very interesting and I'll look it. Other options I'm aware of to avoid USB and complex drivers/protocols: - Scanning QR codes (for example https://air-gap.it/ https://air-gap.it/) - Audio codes (for example https://github.com/romanz/amodem https://github.com/romanz/amodem)
- mirimir 6y agoWow. That is very cool. Edit: https://air-gap.it/ https://air-gap.it/ seems down. But https://github.com/airgap-it https://github.com/airgap-it is up. I wonder if one could cut up QR codes, and store pieces separately. If that were done in Gimp or whatever, there could be multiple copies of each piece.
- infokiller 6y agoDo you mean sharding them using something like Shamir Secret Sharing, splitting in order to be able to transfer/store a large blob, or something else?
- mirimir 6y agoI meant actually cutting them with a sharp knife, or scissors. So you could hide pieces in different places. For stuff like URLs, passphrases, wallet seeds, etc.