added notes

This commit is contained in:
Shautvast 2026-02-22 18:57:26 +01:00
parent 7916365816
commit 69fe7994c8

View file

@ -67,7 +67,7 @@ TCP listener on `localhost:587` (configurable). Minimal implementation:
Components 2 → 3 → 4 can be built and tested with a simple CLI harness before any Components 2 → 3 → 4 can be built and tested with a simple CLI harness before any
network server exists. Component 5 is pure logic with no I/O. Components 6 and 7 are network server exists. Component 5 is pure logic with no I/O. Components 6 and 7 are
the final pieces and can be validated by pointing `skim` at localhost. the final pieces and can be validated by pointing `tuimail` at localhost.
## References ## References
@ -75,4 +75,9 @@ the final pieces and can be validated by pointing `skim` at localhost.
- [ProtonMail/go-proton-api](https://github.com/ProtonMail/go-proton-api) — official Go API client - [ProtonMail/go-proton-api](https://github.com/ProtonMail/go-proton-api) — official Go API client
- [ProtonMail/proton-crypto-rs](https://github.com/ProtonMail/proton-crypto-rs) — official Rust crypto crates - [ProtonMail/proton-crypto-rs](https://github.com/ProtonMail/proton-crypto-rs) — official Rust crypto crates
- [ProtonMail/proton-srp](https://github.com/ProtonMail/proton-srp) — official Rust SRP implementation - [ProtonMail/proton-srp](https://github.com/ProtonMail/proton-srp) — official Rust SRP implementation
- [rpgp](https://github.com/rpgp/rpgp) — pure Rust OpenPGP implementation - [rpgp](https://github.com/rpgp/rpgp) — pure Rust OpenPGP implementation
More work:
- local storge in the proton-bridge. Decide whether to store the message body pgp-encrypted, as it came from the proton server, or
use decrypt it (and serve to the client using imap) and create a AES-256-GCM encrypted cache
- email replies in the tui client have not yet been implemented