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. There is no assurance or promise that the code hosted is the same as the one is served.
How Did We Solve This With Checksums?
The checksums, released on GitHub after every update, allows our users to quickly compare the code served to their browser, with the code hosted on GitHub within 15-30 seconds. Usually, comparing code can take hours or days. With checksums, you can do it in seconds.
Note: Checksums only guarantee the integrity index.html and it does not replace a proper code audit. It merely exists to help our users to quickly verify that the scripts served on CTemplar.com are the same as hosted on GitHub.
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 been tampered and is the same as the one being served, we have a guide in GitHub.
At the time of writing, our current checksum is:
SHA-256 checksum of index.html:
The CTemplar Team
Disclaimer: The checksums do not protect you from malicious code or spying from your browser, OS’s, plugins, ISP providers, running processes, or any other types of malwares or hardware backdoors. We do not protect against keyloggers that may be installed on your computer.