end-to-end

End-To-End is a crypto library to encrypt, decrypt, digital sign, and verify signed messages (implementing OpenPGP) (by google)

End-to-end Alternatives

Similar projects and alternatives to end-to-end

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better end-to-end alternative or higher similarity.

end-to-end reviews and mentions

Posts with mentions or reviews of end-to-end. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-06-13.
  • age and authenticated encryption
    1 project | /r/cryptography | 5 Oct 2022
    [1] No warning on decrypting Tag 9 (no integrity protection) packets
  • A few questions for the dev…
    3 projects | /r/Cryptee | 13 Jun 2022
    In contrast, companies like Standard Notes actually uses their own home-built encryption library, which is why it's a bit more critical that they go through these audits more often and quickly than others. And despite the audits, this home-brewed encryption library puts them at a much bigger risk, due to the fact that it's never going to be as thoroughly battle tested as an open industry-standard encryption like OpenPGP, used by much larger companies like Google, Protonmail, etc.
  • End-to-End Encryption Threat Model
    1 project | /r/CKsTechNews | 20 Feb 2022
    1 project | news.ycombinator.com | 19 Feb 2022
  • End-to-end encryption messaging implementation
    3 projects | /r/ComputerSecurity | 5 Nov 2021
    https://github.com/google/end-to-end ?
  • How to do E2EE in the Browser correctly if even possible?
    2 projects | /r/crypto | 23 Aug 2021
    When Google was looking at implementing E2E mail via a browser plugin, it gave up in part because of the difficulties of doing it right. They published the library and documentation, but the more valuable part was the threat model. In it they examine the assets to protect, threat sources both inside and outside the threat model, UI threats, message threats, key-related threats, cryptographic threats, and other threats. It's an excellent walk-through of just how difficult it is to do general encryption right, and why doing it in the browser is so hard.
  • Signal protocol security of messages
    1 project | /r/crypto | 12 Mar 2021
    With that in mind, secure messaging in a browser is a nightmare. Google tried to figure out a way to do end-to-end in a browser, mostly in the context of e-mail but it could be extended to chat applications. They wrote up a threat model that you really should read. They identified five threat sources within the architecture and six more that they acknowledge but don't delve into. They also discuss four UI-based threats, four message-based, four key-based, and two cryptographic threats, and each of those threats has subthreats. Finally, they wrap with three "Other" threats. They dropped the project soon after.
  • Browser extension that makes any web app E2E encrypted?
    5 projects | /r/privacy | 28 Feb 2021
    Google E2E Library — Unsure how up-to-date this ... limited GitHub activity.
  • A note from our sponsor - WorkOS
    workos.com | 26 Apr 2024
    The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →

Stats

Basic end-to-end repo stats
8
4,133
0.0
about 1 year ago

google/end-to-end is an open source project licensed under Apache License 2.0 which is an OSI approved license.

The primary programming language of end-to-end is JavaScript.


Sponsored
The modern identity platform for B2B SaaS
The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
workos.com