CTemplar Checksum Implementation
Does having open-source code eliminate this risk? No, because open source code is just an act to encourage users’ trust. The audited code in Github might not be the same code that is sent to you from a companies private server. They make no assurances or promises that the code they show to the public and the code you get is the same.
Currently all end to end encrypted email services can hack their own users and decrypt all of their data except us. We are able to provide this level of protection using an implementation of checksums that have not been used before. We are proudly the first “Zero Access” end to end encrypted email service that is not able to decrypt our own user’s emails.
How Did We Solve This With Checksums?
Our checksum implementation allows our users to compare all the code in their browser, to all the code in github within 15-30 seconds. Normally comparing code can take hours or days. Checksums enable it to be done in seconds. You can do it yourself by following our guide it Github, or watching our video (Pending).
First, the file “index.html” starts the platform loading process and determines what is loaded, but when doing so, could pose a couple of risks:
In any case, if anyone wants to manually verify if our “index.html” hasn’t tampered and is exactly the same as the one being served, we have a guide in GitHub.
Our current checksum is:
SHA-256 checksum of “index.html”:
The CTemplar Team:
Disclaimer: Checksums do not protect you from hacks from your browser, OS’s, plugins, mobile ISP providers, running process software or the Intel Microprocessor hardware backdoor. We do not protect against keyloggers that may be installed on your computer.