blastrock

7 ms·

1.
by blastrock 2y ago
Thanks for the link! Funny to see that someone already thought of this attack in 2022
2.
by blastrock 2y ago
Very clever! I am the author of one of the older guides https://blastrock.github.io/fde-tpm-sb.html . I was wondering about the solution you propose which seems a bit complicated to me. Here's my idea, please tell me i
3.
by blastrock 7y ago
The encryption/upload is streamed, but the download/decryption is not, we will work on that. Thanks for the link!
4.
by blastrock 7y ago
Actually, Filekit is meant to be integrated into an application, and that application is responsible for delivering JS and handling identities, not the Tanker server.
5.
by blastrock 7y ago
No, the unlock key is for the user to keep, and never be transmitted by anyone else than the user themselves. If you do the transmission, it's not end to end anymore. This option is only for users concerned about security, the other un
6.
by blastrock 7y ago
TweetNaCl is roughly equivalent to libsodium, on which Tanker builds. Tanker is easier to integrate into your app because it takes care of key sharing, multi-devices, user group managment, etc. These are all things you would have to handle
7.
by blastrock 7y ago
> how the Trustchain Private Key is "obtained". The Trustchain private key is generated when you create a Trustchain. It is generated on your machine. You can try it and create a Trustchain yourself here: https://d
8.
by blastrock 7y ago
> Is libsodium WASMed for the browser? It is not WASMed yet, but we are working on it. > It would be nice if Tanker exposed the cryptography operations, so it could be a more re-usable library. Is this possible? Tanker is more of a hi
9.
by blastrock 7y ago
You are right, you'd still have to trust the webmail/chat provider if you want to chat securely. Tanker still protects against data leaks from the app servers in this case. We also provide SDKs for Android and iOS. They protect ag
10.
by blastrock 7y ago
Tanker developer here. We use libsodium as our underlying cryptographic library. It uses XChacha20/Poly1305 for symmetric encryption, Curve25519 for asymmetric encryption and signature, and Blake2 for hashing.