CTemplar Checksum Implementation
Currently, all email services have a backdoor to accessing and decrypting their own user’s data. They make their code “Open Source” allowing anyone to review it. However, they do not serve users code from that “Open Source” depository. You must hope and trust you are getting the same audited “backdoor free” code. You are actually served code that is not audited and is being sent from a server that email companies do not allow to be audited. Because of this email services can serve
Our Solution and How to Perform a Checksum
We are implementing SRI (Subresource Integrity), which is a checksum-like verification integrated
This allows users to guarantee that our open source code shown in Github is the same code that they are receiving from our server. We are the first secure email service to have “Zero-Access” to our users data by closing vulnerability.
What is a checksum?
A checksum is a sequence of numbers and letters used to check data for data corruption or tampering. If the author of a program provides a checksum for a file, you can verify – with a checksum tool – if the file you got, is exactly the same as the
How to Perform a Checksum
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” wasn’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