Hello pol. Recently I've been messing around with a project called Keybase, and I think it could be beneficial to our long-term survival and success as a hivemind.
The basic idea of Keybase is total end-to-end encryption for every day use cases. When you make an account, you generate cryptographic keys for each device and these keys are all linked together as you add friends, join groups and add files to your KBFS (keybase file system). Currently they let you use around 10+ gb of free encrypted cloud storage. You can also do encrypted git repos, cryptographically sign (verify) documents, etc.
I think we could benefit from something like this. The KBFS is really robust, so we can all share files, and groups are totally closed off from anyone that isn't a member.
If anyone is interested, I made a Keybase team/group called "saetet" and I've been adding redpills to my KBFS.
I've also figured out how to add+archive threads live to KBFS: check it out
And when the Chinese regime cracks your encryption protocol with their growing quantum technology in ten years you curl up in a little ball and say goodbye.
These things are going to be added with time, and Keybase is by far the most accesible platform there is. You can use TOR with it as well, FWIW.
Ian Sanchez
With secondary processors in all consumer hardware using a "stronger" algorithm won't solve much of anything. The most helpful thing would be OpenHardware, which has been viciously fought internationally.
At a high level, end-user devices are trusted and Keybase/KBFS/other servers are untrusted. On desktops, we run all KBFS processes as the current user and use OS-level secret stores, but we don’t attempt to protect against other processes owned by the same user or root.
The KBFS client doesn’t trust any data coming from Keybase or KBFS servers, and verifies any received data against the relevant users’ public keys. For the nitty-gritty details, see the KBFS crypto doc. In particular, the KBFS servers cannot see into the contents or structure of your (non-public) files.
That having been said, the KBFS servers knows what users can access which data, and will only serve data to an authorized reader of a TLF with a valid session. Furthermore, they will only serve historical (archived) data to writers of a TLF, even public ones.
Aiden Taylor
Is it OTP encryption? No. /thread
Brody Bell
Use tox nigger
Benjamin Garcia
It doesn't matter if you are using AES-NI instructions or a simple XOR instruction for your encryption, since secondary processors in consumer CPUs are everywhere for "performance" clocking purposes. All these processors are hooked into the attached chipset as well the integrated Ethernet card or even worse wireless or integrated 3G/4G/5G for "IT support" reasons and so unless you're monitoring the radio signals of your computer or Ethernet cable with hardware that you have built yourself or know doesn't have any bugs in it, then you can't be sure all your key information is being transmitted without your knowledge.
This is why agencies have made it publicly a big deal about their inability to break bad guys using encryption, which true from a purely scientific perspective, means nothing when if they have as much information as the user of this encryption. This isn't to say I'm against the use of encryption, because the proofs for the correctness of the algorithms is correct. Just don't be awed when an agency is able to read your AES-512 encrypted harddrive because the key you used was stored by processor during the operation and either secretly held in some small NAND flash somewhere in the chipset or transmitted to the agency when you used the GPL tool with a known signature to do the operation, that you from a software perspective was completely secret.
John Torres
yeah nah. If you didn't take care of the hardware before using OTP you might as well write your message in a plaintext TV advert.
