Privacy

515 readers

319 users here now

Protect your privacy in the digital world

Welcome! This is a community for all those who are interested in protecting their privacy.

Rules

~PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!~

Be nice, civil and no bigotry/prejudice
No tankies/alt-right fascists. The former can be tolerated but the latter are banned
Stay on topic
Don't promote proprietary software
No crypto
No Xitter links (only allowed when can't fact check any other way, use xcancel)
If you post news exclusive to a country please name it. ~(This isn't a bannable rule, just a recommendation!)~

Related communities

founded 2 months ago

MODERATORS

[email protected]

crypt.fyi - Secure Secret Sharing with Zero-Knowledge End-to-End Encryption (crypt.fyi)

submitted 5 days ago by [email protected] to c/[email protected]

20 comments fedilink hide all child comments

From an author:

I wanted to share crypt.fyi - a free, open-source tool I built for securely sharing sensitive data/files. It uses client-side encryption and zero-knowledge architecture.

Key features:

- Zero-knowledge architecture
- End-to-end encryption using AES-256-GCM (actively investigating post-quantum encryption options)
- Self-hostable
- Suite of configurations (password, burn after read, max read count, ip/cidr-allow list, webhooks)
- Strict rate-limiting
- Strict CSP to mitigate supply chain attacks
- Web, cli, and chrome-extension clients
- Fully open source (Github)

The problems I aimed to solve: Many people share sensitive info (passwords, keys, etc.) through email, Slack, or SMS - which often leaves plaintext copies in multiple places. Existing solutions either require accounts, aren't open source, or have security/privacy/ui/ux/feature/config gaps/limitations.

crypt.fyi is built with privacy-first principles:

- No logging of sensitive data
- No analytics or tracking
- Separation of web and api servers
- All encryption/decryption happens client-side using shared cross-platform cryptography primitives from noble cryptography
- TLS encryption for all traffic
- Encrypted data is automatically destroyed after being read with strong guarantees around once-only reads

The entire codebase is open source and available for review. I'd love to get feedback from the privacy community on how to make it even better!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 day ago* (last edited 1 day ago)

Edit: Hi & welcome! Nice to come by and discuss these kind of things!

How is the key circulated? Over RSA or something? Or do you have to send the link+key somehow to the recipient?

Yeah GCM is nice with the inbuilt authentication. AES 256 I guess?

NIST is aaaabout to chose an algo, right? I dug deep down in all that quantum stuff like a year ago, but it didn't seem like they'd chosen Rivests algo just yet ^^

BTW is the GCM adding a lot of space? I'm on AES CTR (which just aligns to the block size) + RSA for authentication.