💾 Archived View for bbs.geminispace.org › u › flipperzero › 18238 captured on 2024-07-09 at 04:10:35. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Re: "I've added support for "at rest" message encryption in the..."
The updates are now live on the Hashnix misfin server
Jun 30 · 9 days ago
😺 gemalaya [OP] · Jun 30 at 13:07:
If you use encryption, the privkey is now spared from destruction by the frontend every time you access the gembox, to prevent repetitive key input.
- Use a time-adaptive sparing cache for gemboxes. Gemboxes which use
encryption are spared from being purged by the cache if a privkey is active.
- Spare active encrypted gemboxes from destruction every time the inbox page
is accessed. This means that the user doesn't have to input the private key
every time the gembox TTL expires, but rather only when the user hasn't accessed
the inbox for some time.
— titan-upload: Shell script for uploading via titan, supporting certificates
😺 gemalaya [OP] · Jun 30 at 16:18:
@byzoni That script (titan-upload) could indeed be used to upload a file to the misfin server, just need to pass the cert and key properly.
I've added support for "at rest" message encryption in the python misfin implementation. When encryption is enabled, you send your private key to decrypt the messages in the gembox and the key remains active for a certain amount of time. There's also experimental support for encrypted file uploads: you upload a file via Titan, and it gives you a download URL with a decryption key that you can include in your misfin messages. [https link]