Opened 5 years ago
Last modified 3 years ago
#1362 accepted enhancement
Bote-mail.i2p-internet gateway
Reported by: | user | Owned by: | str4d |
---|---|---|---|
Priority: | minor | Milestone: | eventually |
Component: | other | Version: | 0.9.14.1 |
Keywords: | I2P-Bote privacy | Cc: | |
Parent Tickets: | Sensitive: | no |
Description
A gateway for mails between internet, mail.i2p and Bote.
ideally open-source and freely available so in the event of it going down, alternatvies need not reimplemented, but can easily be set up by volunteers with the required ressources.
Subtickets
Change History (6)
comment:1 Changed 5 years ago by
comment:2 Changed 5 years ago by
very good remarks.
I don't know how big PGP implementations are. so if it'S easy to integrate and does not bloat Bote too much and keeps it maintanable, then icluding PGP would not be bad.
But otoh PGP is widely used and the user likely has it installed on his system anyway.
And a receiver on the internet might really not have PGP, and all that the sender wants is send an anonymous mail to him, caring only about being anon, not about the content of the mail.
Metadata could also be minimized in that kind to a minimum, like omitting sent time - to be discussed.
In case a mail is sent to various destinataries, the sender would likely want to set the others into BCC so that not the entire internt surveillance industry knows with whom you (that anon identity) are communicating with.
So the UI warning about lack of encryption and about visible metadata, to both the gateway itself and internet surveillance could suffice. I like the wording of "Bote is strongest when used for Bote-internal communication".
comment:3 Changed 5 years ago by
Keywords: | I2P-Bote privacy added |
---|---|
Milestone: | 0.9.16 |
I have recently migrated I2P-Bote's address crypto to use the JCA for ECC and AES, instead of BouncyCastle directly. This means that I2P-Bote will now be bundled with the full BouncyCastle crypto provider (instead of the ECC-only stripped-down classes), and it would be trivial to also bundle the BouncyCastle OpenPGP implementation. It would increase the package size, but the full BC provider has already done that :-P
I have a rough draft idea of how this gateway would operate, which I am discussing with postman. Details will follow once we have something worth posting.
comment:4 Changed 4 years ago by
Milestone: | → eventually |
---|---|
Status: | new → open |
Type: | task → enhancement |
comment:5 Changed 3 years ago by
Owner: | changed from postman to str4d |
---|---|
Status: | open → accepted |
comment:6 Changed 3 years ago by
Migrated to https://github.com/i2p/i2p.i2p-bote/issues - I will close these tickets as things are resolved rather than right now, but please make future comments on GitHub?.
On the gateway side, the IMAP and SMTP interfaces make this easier to implement.
On the client side, the trivial case is already deployed: users can add a gateway EmailDestination to their Bote client's settings, and emails with non-EmailDestination recipients will be sent to the gateway.
The trivial case does not account for several issues: