A deep dive into how we do E2EE and how we intend to improve on the E2EE implementation in our secure file sharing product called Skizzle.
- You will learn not only about our current E2EE implementation but also our proposed future implementation where we intend to employ Signal’s Double Ratchet Algorithm
- We will also discuss our measures to ensure Skizzle is privacy preserving.
- We will also discuss how we leverage a public blockchain to bring about unprecedented trust in Skizzle.
In its current avatar, Skizzle is a browser extension that allows you to send/receive end-to-end encrypted attachments right in your Gmail. All user actions are written to a public blockchain which allows them to publicly verify their account usage and the state of their files(who has access), at any time.
With a focus on data security and being privacy preserving, Skizzle intends to create a suite of products for various platforms that allows all kinds of users(individuals, small or big businesses/institutions) to plug E2EE of files and data into their normal workflow when using their favorite email or chat clients.
We also intend to expand into a secure storage and data sharing platform where developers can plug our SDKs into their apps and offer a variety of E2EE use cases to their users, right out of the box.
- Introduction to Skizzle
- How does Skizzle do E2EE
- How is Skizzle privacy preserving
- How is Skizzle transparent
- What the future looks like for Skizzle
Mayur Relekar
Founder https://skizzle.email
Founder https://newfang.io
https://www.linkedin.com/in/mayurrelekar
https://twitter.com/mayurrelekar
- Previous talk on Skizzle’s E2EE scheme:
-
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}