overview for parsimon

Browser-side decryption for Age-encrypted share links by parsimon in c/privacy@programming.dev

[-] parsimon@programming.dev 0 points 4 days ago

I hate phone typing, so I'll take it as a compliment 😉

Why does Linux have such a terrible sleep? by parsimon in c/linux@programming.dev

[-] parsimon@programming.dev 1 points 4 days ago

32 GiB. I decided against a 96 GiB model with hibernation in mind.

Browser-side decryption for Age-encrypted share links by parsimon in c/privacy@programming.dev

[-] parsimon@programming.dev -1 points 4 days ago

You are absolutely right, and I should have thought before quickly posting. I'm going to amend the source repo ASAP to make it clear. I enjoy algorithmics and CLI works, but I hate UI, so this really is a time-saver for me. I'd never be a good web front-end developer. That said, I exercise quality control and control the logic. This app is just a tiny layer on top of the official age/typage typescript library. Go and check the source!

0

Browser-side decryption for Age-encrypted share links (github.com)

submitted 4 days ago by parsimon@programming.dev to c/privacy@programming.dev

6 comments fedilink

I built a small open-source web app that lets people share Age-encrypted files using ordinary web hosting. The encrypted file can be hosted at any HTTPS URL, including a public or pre-signed URL for an S3-compatible object store. Decryption happens locally in the recipient’s browser.

Source: https://github.com/parsimonit/web-age-stream-decryptor Demo: https://decrypt-app.zebrastream.io/

The encrypted file stays on the existing server. The recipient opens a share link, and the file is decrypted locally in the browser for viewing or downloading. There’s no decryption backend.

The link contains the file URL and Age passphrase in the URL fragment, so the passphrase is not sent in the HTTP request. The complete link is still a bearer secret: anyone who gets it can decrypt the file.

I’m interested in feedback from people familiar with privacy tools and threat modeling:

Is this useful compared with existing encrypted file-sharing tools?
Are there important browser or URL-leakage risks I should document?
Does the “static frontend + arbitrary encrypted object storage” model seem worthwhile?
Should rendering decrypted HTML be disabled or treated as an unsafe feature?

Current limitations include buffering large files in memory and the possibility of script execution when decrypted HTML is rendered.

Why does Linux have such a terrible sleep? by parsimon in c/linux@programming.dev

[-] parsimon@programming.dev 2 points 5 days ago

True, kernel developers should resolve the Secure Boot issue with hibernation, but the development focus is on servers, not laptop computers. Also, hibernation should probably use a dedicated hibernate image file instead of requiring a huge swap partition. That being said, it works regardless of hardware capabilities if you turn off secure boot and just configure a LUKS-encrypted SWAP partition. You should figure this out before you install the OS.

Why does Linux have such a terrible sleep? by parsimon in c/linux@programming.dev

[-] parsimon@programming.dev 14 points 5 days ago

I recommend using hibernate (suspend to disk): your computer will "sleep" for 10 years without draining. The only cost is about 7 seconds to boot on modern hardware. For short interruptions with instant wakeup, you can still use light sleep states.

It combines perfectly with LUKS-encrypted root and swap partitions: your data is safe even if someone steals your computer and swakes it up.