Of course, bolting security on top of email is going to be a challenge, and require trade-offs between convenience and security.
It’s likely that there are aspects of how Tuta works that I have misunderstood, but based on my understandings, this is my take:
For my use case, I believe tuta’s choice of increased security isn’t worth the added inconvenience for the people I’m communicating with who have to access our communications through a separate webpage instead of within their normal email inbox. (Perhaps they can export the emails from that site, but if so, they’d be unencrypted on their machine unless the user took manual steps to reenceypt, no?)
Secondly, I do not, IRL, know anybody else who uses Tuta, but I know a handful of people who do use PGP (for example through Proton). That would mean that communications with them would need to be unencrypted, or go through Tuta’s portal, just as if they were regular gmail users. In contrast, if I were to choose a PGP based encryption, communicating with them - encrypted - would be more convenient. Less secure? Yes, but as I said above, that’s a trade-off that I’m willing to make. Not to mention, if I no longer liked the service next year I ought be able to move on without ruining access to old emails, or really, even seeing an interruption in ongoing email conversations. Yes, that does require a custom domain to work in practice - I’ve set that as a precondition for whatever service I’m going to sign up for.
Thirdly, I mentioned a walled garden.
Assume I were to use Tuta for a couple of years. People I regularly exchange encrypted mail with have gotten frustrated by having to use the portal and signed up for Tuta as well. One day, I decide that I would like to move elsewhere for whatever reason. Now I’m the one who have to use Tuta’s portal whenever I want to communicate with my friends, because there’s no other service that I can go to, that’s compatible with Tuta’s encryption.
That’s why I consider Tuta to be a walled garden.
I am glad that they finally did add import/export. When I took the service for a spin maybe a year and a half ago, import and export wasn’t yet possible and a another reason too why I didn’t join them already in mid 2023.
(BTW, have they fixed the Linux desktop app so that it can be used on a hi-dpi (4k) screen without a magnifying glass? Back then, that app refused to listen to any display scaling commands. I had to reconfigure the display resolution from 4k to 2k to be able to interact with the app.)
That all makes sense. You described yourself as a non-techie, so I misunderstood and thought you had assumed that all emails had to go through their portal.
You’re correct that Tuta doesn’t support PGP or S/MIME, which I didn’t realize. I assumed that any email service that has the word “privacy” on their website would support both. I don’t use personal email for sensitive communications, so I’m not in the habit of using PGP or S/MIME, but still… come on.
Their reasoning seems a bit silly. They say they don’t support PGP because it doesn’t encrypt the subject line, and it doesn’t support post-quantum algorithms or forward secrecy. That’s, at most, a warning line in the GUI, not something you just don’t implement.
They say they don’t implement S/MIME because of EFail, a seven year old vulnerability. They can’t confirm that all external services have a mitigation in place for it. But again, just put a warning on the UI. Could even build a list of external providers that mitigate it and only show the warning if the user is sending to a system not on the list.
There are a lot of places on Tuta’s website where they say they’re working on features but don’t specify a timeline, and a quick scan through their github issues finds someconversations where they indicate developer resources are low and they’re focused on post quantum encryption first, but they said that for years. Seems they didn’t implement basic features because they wanted the one big QC feature. They stated in 2020 that they intend to support PGP and Autocrypt, but they removed those from their roadmap. They’re not a current priority.
Yep, I can totally see the walled garden aspect. If you want PGP, Autocrypt, or S/MIME, find another provider until Tuta gets around to implementing them. A lot of their communications read as though they don’t have enough development staff to chew what they’re biting off.
ETA: I don’t see any scaling option in their desktop app, but you can launch it with GDK_DPI_SCALE=1.25 (or some other number) to embiggen it.
Of course, bolting security on top of email is going to be a challenge, and require trade-offs between convenience and security.
It’s likely that there are aspects of how Tuta works that I have misunderstood, but based on my understandings, this is my take:
For my use case, I believe tuta’s choice of increased security isn’t worth the added inconvenience for the people I’m communicating with who have to access our communications through a separate webpage instead of within their normal email inbox. (Perhaps they can export the emails from that site, but if so, they’d be unencrypted on their machine unless the user took manual steps to reenceypt, no?)
Secondly, I do not, IRL, know anybody else who uses Tuta, but I know a handful of people who do use PGP (for example through Proton). That would mean that communications with them would need to be unencrypted, or go through Tuta’s portal, just as if they were regular gmail users. In contrast, if I were to choose a PGP based encryption, communicating with them - encrypted - would be more convenient. Less secure? Yes, but as I said above, that’s a trade-off that I’m willing to make. Not to mention, if I no longer liked the service next year I ought be able to move on without ruining access to old emails, or really, even seeing an interruption in ongoing email conversations. Yes, that does require a custom domain to work in practice - I’ve set that as a precondition for whatever service I’m going to sign up for.
Thirdly, I mentioned a walled garden. Assume I were to use Tuta for a couple of years. People I regularly exchange encrypted mail with have gotten frustrated by having to use the portal and signed up for Tuta as well. One day, I decide that I would like to move elsewhere for whatever reason. Now I’m the one who have to use Tuta’s portal whenever I want to communicate with my friends, because there’s no other service that I can go to, that’s compatible with Tuta’s encryption. That’s why I consider Tuta to be a walled garden.
I am glad that they finally did add import/export. When I took the service for a spin maybe a year and a half ago, import and export wasn’t yet possible and a another reason too why I didn’t join them already in mid 2023.
(BTW, have they fixed the Linux desktop app so that it can be used on a hi-dpi (4k) screen without a magnifying glass? Back then, that app refused to listen to any display scaling commands. I had to reconfigure the display resolution from 4k to 2k to be able to interact with the app.)
That all makes sense. You described yourself as a non-techie, so I misunderstood and thought you had assumed that all emails had to go through their portal.
You’re correct that Tuta doesn’t support PGP or S/MIME, which I didn’t realize. I assumed that any email service that has the word “privacy” on their website would support both. I don’t use personal email for sensitive communications, so I’m not in the habit of using PGP or S/MIME, but still… come on.
Their reasoning seems a bit silly. They say they don’t support PGP because it doesn’t encrypt the subject line, and it doesn’t support post-quantum algorithms or forward secrecy. That’s, at most, a warning line in the GUI, not something you just don’t implement.
They say they don’t implement S/MIME because of EFail, a seven year old vulnerability. They can’t confirm that all external services have a mitigation in place for it. But again, just put a warning on the UI. Could even build a list of external providers that mitigate it and only show the warning if the user is sending to a system not on the list.
There are a lot of places on Tuta’s website where they say they’re working on features but don’t specify a timeline, and a quick scan through their github issues finds some conversations where they indicate developer resources are low and they’re focused on post quantum encryption first, but they said that for years. Seems they didn’t implement basic features because they wanted the one big QC feature. They stated in 2020 that they intend to support PGP and Autocrypt, but they removed those from their roadmap. They’re not a current priority.
“Once our PQ-encryption is in place we can consider how to best interop with others keeping benefits of perfect secrecy and post-quantum encryption.” So it looks like they’re letting Perfect be the enemy of Good.
Yep, I can totally see the walled garden aspect. If you want PGP, Autocrypt, or S/MIME, find another provider until Tuta gets around to implementing them. A lot of their communications read as though they don’t have enough development staff to chew what they’re biting off.
ETA: I don’t see any scaling option in their desktop app, but you can launch it with GDK_DPI_SCALE=1.25 (or some other number) to embiggen it.