Skiff – Privacy-first end-to-end encrypted email
61–70 of 201 posts
Re: Skiff – Privacy-first end-to-end encrypted email
#62Earlier quoted context omitted.
Worth noting that Google does not do what you're describing. Google has never literally "sold" data from Gmail and stopped using it for their own ads ~6 years ago.
So gmail was making money off of personal emails as recently 2017. Why trust them? There is no good reason they shouldn’t e2ee that data.
Re: Skiff – Privacy-first end-to-end encrypted email
#63Earlier quoted context omitted.
And domain support?
Yes, we have custom domain support with DKIM/DMARC/SPF all enabled.
Re: Skiff – Privacy-first end-to-end encrypted email
#64I'm curious if your emails go to spam more frequently, being a smaller player in an established hegemony.
You have a generous free tier which may attract spammers. How do you deal with IP reputation?
Re: Skiff – Privacy-first end-to-end encrypted email
#65Earlier quoted context omitted.
So gmail was making money off of personal emails as recently 2017. Why trust them? There is no good reason they shouldn’t e2ee that data.
Except there is a reason. Encrypting email has very little to no benefit, since it is transmitted in plaintext and usually stored in plaintext on the recipient's side, your emails almost always exist in unencrypted form. On top of that it has major usability drawbacks, for example you cant ask the server to search emails for you anymore - all emails have to be downloaded on all your devices to be able to search - whi…
Re: Skiff – Privacy-first end-to-end encrypted email
#66Earlier quoted context omitted.
Founding engineer at Skiff here. >From the white paper, it appears as if this system requires its users to trust the server. That's not end-to-end encryption. What do I have wrong here? It doesn't. All data is encrypted client side across all apps - Skiff Mail, Drive, Pages, and Calendar. For sending external, the whitepaper is very clear how this case is handled in section 8.2 as securely as possible (without having…
Section 8.2 seems to talk about how you send plaintext email via SMTP to users who aren't using Skiff. But that's not what I'm talking about with respect to end-to-end encryption. The white paper refers repeatedly to "browser" users. Your server can feed arbitrary Javascript to browsers and subvert encryption in a variety of ways, can't it? I'm still not clear why you designed a new, simplistic cryptosystem at all he…
Re: Skiff – Privacy-first end-to-end encrypted email
#67Their website describes this as open source but their linked repo is under CC BY-NC-SA 4.0 [1] so not commonly regarded as open source, but instead source available. They have been made aware of this [2]. Additionally, I think it may only be the front-end parts of their apps that are source available, I'm not sure the server-side parts of their app have sources published. [1] https://creativecommons.org/licenses/by-n…
Re: Skiff – Privacy-first end-to-end encrypted email
#68Their website describes this as open source but their linked repo is under CC BY-NC-SA 4.0 [1] so not commonly regarded as open source, but instead source available. They have been made aware of this [2]. Additionally, I think it may only be the front-end parts of their apps that are source available, I'm not sure the server-side parts of their app have sources published. [1] https://creativecommons.org/licenses/by-n…
Open source does not mean anything in the first place. Terms like Libre or Free Software exist for a reason.
Re: Skiff – Privacy-first end-to-end encrypted email
#69Their website describes this as open source but their linked repo is under CC BY-NC-SA 4.0 [1] so not commonly regarded as open source, but instead source available. They have been made aware of this [2]. Additionally, I think it may only be the front-end parts of their apps that are source available, I'm not sure the server-side parts of their app have sources published. [1] https://creativecommons.org/licenses/by-n…
Hello! Yes, we're working on this. Note that our UI, cryptography, and editor libraries are MIT licensed.
Global preference for open source aside, whichever license you pick, I'd recommend visiting https://joinup.ec.europa.eu/collection/eupl/solution/joinup-... for example, a great tool to find the appropriate license for your software.
https://reuse.software/tutorial/ is a great read and a wonderful initiative to help with licensing and compliance.
P.S: CC is not made for software.
Re: Skiff – Privacy-first end-to-end encrypted email
#70Their website describes this as open source but their linked repo is under CC BY-NC-SA 4.0 [1] so not commonly regarded as open source, but instead source available. They have been made aware of this [2]. Additionally, I think it may only be the front-end parts of their apps that are source available, I'm not sure the server-side parts of their app have sources published. [1] https://creativecommons.org/licenses/by-n…
Open source does not mean anything in the first place. Terms like Libre or Free Software exist for a reason.