Security Audit & Integrity

Mathematical proof for the "Servers are Evil" mandate.

Warrant Canary Checking...

Loading latest integrity report...

View Raw canary.txt
File Integrity (SHA-256)

Verify your local files against the developer's signed manifest:

Loading hashes.txt...

How to Verify Your Extension:

Privacy Bar is source-available so you can verify that the code running in your browser matches the developer's original build. This facilitates security auditing and trust.

1. Find your Extension Folder:
  • Mac: ~/Library/Application Support/Google/Chrome/Default/Extensions/objpfdibjogbdpjjpomnoaflkgdeaanb
  • Windows: %LOCALAPPDATA%\Google\Chrome\User Data\Default\Extensions/objpfdibjogbdpjjpomnoaflkgdeaanb
  • Linux: ~/.config/google-chrome/Default/Extensions/objpfdibjogbdpjjpomnoaflkgdeaanb
2. Download the Manifest: Save the official hashes.txt file into that folder.

3. Run the Verification Command:
MacOS/Linux:
shasum -a 256 -c hashes.txt

Windows (PowerShell):
Get-Content hashes.txt | Where-Object { $_ -notmatch '^#' } | ForEach-Object { $h, $f = $_ -split ' +'; if ((Get-FileHash $f).Hash -eq $h) { "$f: OK" } else { "$f: FAIL" } }
Troubleshooting Mismatches (LF vs CRLF):
If a file says FAIL but you haven't changed the code, it is likely due to line-ending conversion. Windows often converts LF to CRLF, which changes the file's hash. To be certain, inspect the file manually via DevTools (F12) to audit the raw logic.

Note: "Reading" the code does not constitute a license to copy, modify, or redistribute the logic. "Don't trust. Verify."

Open Source & Credits

Unabridged list of external resources and cryptographic libraries used in Privacy Bar:

Loading credits.txt...

"Standing on the shoulders of giants to keep the servers at bay."