2 ms·
"The insertion is done when we have received a response from Google servers" But GMelius is a client-side application, right? According to your whitepaper, the
by crote 8y ago
"The insertion is done when we have received a response from Google servers"
But GMelius is a client-side application, right? According to your whitepaper, the insertion is done when the _client_ receives the response, I don't see anything about validation from the GMelius servers to GMail.
"SHA-512"
It's not the SHA part which is the problem, it's the RSA part. 512-bit RSA is well-known to be broken and there have already been multiple exploits. 2048 bits is the bare minimum anyone should use nowadays.
- xpressyoo 8y agoAll the logic happens at the back-end level via our API communicating with Gmail's one. Nothing is done on the client-side (i.e., extension) besides the integration of our buttons/features within Gmail's UI. 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.