xpressyoo
The RSA key is just used to show that what has been inserted was through our service. Note that the final hash resulting from the mixer is done without any RSA.
This hybrid process implies you will need to trust parties at some points, e.g., Google and Gmelius. However, the point here is to offer a means to store in a robust way the trace that a specific email communication existed at a point in time, including its context/content.
We only receive response statuses and act accordingly. Moreover, we think it's important for this functionality to make sense to insert the hash corresponding to the integrity of the email, and so make possible for our customers to "prove" they have indeed sent an email with a specific body/subject/...
"They both supply email tracking, and protect your privacy by blocking email tracking."
> This is mainly offered to prevent false positives for our own trackers. But point taken :)
"It doesn't prove that the email has been sent, it just proves that it has been submitted to Gmelius for signing."
> The insertion is done when we have received a response from Google servers.
"SHA-512"
> Long debate but this was the most natural solution for a Merkle architecture.
A decisive challenge raised by today’s email dominance in the workplace is that the latter means of communication does not offer a built-in function to prove the integrity and authenticity neither of its content nor of its origin. Knowing that emails are increasingly presented as legal evidence in courts worldwide, it becomes urgent to think of approaches that could palliate the inherent flaws of email.
EDIT: And yes, Gmelius offers a lightweight CRM targeting SMEs that covers all the stages of the modern communication flow: from the first interaction to the potential signature of a contract/quote. Besides, Gmelius offers a shared inbox making possible to follow-up on leads, stay in sync with your team.
Show HN: Prevent email forgery in Gmail using a Blockchain-powered architecture
If you need more convincing, just go through our code after installing the extension and/or check your console and network when using Gmail with Gmelius installed.
Show HN: Gmelius 6 – Gmail just got better
Block and Unsubscribe
i) Are you planning to make the whole implementation Open Source?
ii) Say I wish to adopt and use your SDK in my current Gmail/Inbox extensions (>100K daily users), may I expect the implementation of a fixed upper limit on the number of transmissions in the coming months (which could endanger the reliability of my service for my users)?
iii) While the SDK currently only focuses on the UI, are you planning to add more "complex" interactions, such as Gmail filters/Gmail preferences ? If yes, feel free to get in touch. I will be happy to help.
Congrats, again.
-- Florian, Gmelius dev
Show HN: Gmelius for Google Inbox – Import Gmail Signatures, Block Trackers
Show HN: Add signatures to Inbox by Gmail
Show HN: Gmelius for Inbox by Gmail
Show HN: Gmelius for Inbox by Gmail (Beta)
https://chrome.google.com/webstore/detail/gmelius-for-google-inbox/dlbjhjnahgmigifoggidegpakbcjomgg
This is a very early version of Gmelius for Google Inbox, currently available as a Chrome extension. Feel free to share your suggestions and feedback in the comments. Thanks in advance.