Hello,
I have been prototyping with this idea of using Tor as a domain for email service It works really well so far in testing. Wanted to share with the community.
It works identically to email as a store and forward service. The idea is you can use a old computer or something as a physical mailbox in your control.
Here are some design choices I have implemented.
Two onion addresses.
One becomes your public domain with a customizable prefex. [prefix@123…onion]. This prefix can be changed and if the sender does not have it, you will not receive.
One is strictly a UI address and by default is set up as a authentecated service. Without the key, address, master password, and optional 2FA, you cannot access remotely. It should be a pretty solid way of protecting communications.
The reciever service does very basic things and has limited surface intentionally.
-Receives incoming messages from other users.
-Hosts your PGP public key. During compose, if a key is published on your node, the sender can fetch for an additional layer of encryption.
PGP implementation is included as openpgp.min.js in /static. Private keys never transmitted over the network. Including it directly from the server additional e2ee one click.
I’ve decided to not include attachments. This is a text only service for now and maybe forever.
Install is as straight forward and compatible with termux, Linux, macos. No root required and just a few commands to get it going.
Once the service is running, you can access it remotely with your credentials, or on localhost without the need to download the Tor browser.
The directory is isolated in a way where you can actually host multiple services on one device.
Still a work in progress but I thought it was far enough along to share.
Are there any other services set up like this in this fashion?
Repository here
