Automatic security, browse encrypted.
KB SSL Enforcer Extension
It is not completely secure against the infamous Firesheep, but it does minimize the risk greatly. See the section on complete enforcement for technical details and more on when this will be possible.
Features:
- Automatically detects if a site supports SSL (TLS) and enforces all subsequent requests to be over SSL
- As soon as a domain is set to be enforce, the browser will not send any unencrypted requests for that domain (unless the site deliberately enforces not using encryption, see the section on complete enforcement)
- Flexible options for overriding the auto-detection
- Caches which sites support SSL (respects incognito mode)
- Open source (GPLv2 or later)
Changelog:
https://github.com/kbitdk/kbsslenforcer/blob/master/Changelog.md
Issue tracker:
https://github.com/kbitdk/kbsslenforcer/issues
Complete enforcement:
Due to Chrome limitations KB SSL Enforcer detects SSL on the very first visit to a page and is unable to block the unencrypted request from going through while this is happening. It will let that page load and if it is detected to support SSL, all subsequent requests to that domain will be enforced automatically to use SSL before the unencrypted request is sent from the browser.
The unencrypted request only goes through on the very first page visit where it's detecting SSL support. The setting will be saved and survives reboots and all. The only way to stop enforcing SSL is to manually set it to ignore SSL on that domain or if the extension detects that the site is trying to enforce an unencrypted connection and therefore backs off by not enforcing it from then on.
This first insecure request could send a cookie in the clear, which would give anyone with tools like Firesheep an opportunity to use your account on that site. But this only happens if they catch it during that first request and if it includes sensitive information, such as your logged in session. All subsequent requests, even after restarting the browser and rebooting the computer, will enforce encryption.
Permissions:
The manifest file states the permissions requested:
https://github.com/kbitdk/kbsslenforcer/blob/master/chrome%20extension/manifest.json
* *://*/
* This is for accessing pages on all domains and both with and without SSL
* tabs
* This is for accessing information on whether a tab is in incognito, so it can be respected
* webRequest
* This is for intercepting the unencrypted requests and detecting whether the site doesn't support encryption by redirecting encrypted requests to the unencrypted site
* webRequestBlocking
* This is for blocking the unencrypted requests while determining whether it needs to be redirected
The project is open source and any scrutiny of the code or the extension's behavior is encouraged. If you have any comments, please open an issue on the issue tracker:
https://github.com/kbitdk/kbsslenforcer/issues
Feedback:
Any questions or feedback are welcome in the issue tracker linked above, which has features to manage and notify people of any issues, so they can be fixed and we can all have a better extension. Please keep the user reviews section of this page to just reviews. Thanks.
Developed by KB IT:
https://kbit.dk
Source Manifest.json
How to download and manually install KB SSL Enforcer extension for Chrome
Looking for a way to install KB SSL Enforcer extensions for Chrome, you can search for them in the Chrome Web Store, clicking the "Add to Chrome" button, and following the straightforward process.
However, you may need to install KB SSL Enforcer extensions manually, this article outlines two simple methods to effortlessly install KB SSL Enforcer extensions, whether they come as unpacked folders in compressed formats like .zip or as .crx files.
Method 1: Download KB SSL Enforcer extension and manually install through Drag &Drop
If you ever need to manually install a KB SSL Enforcer extension for Chrome, don't worry, it's a simple process. Just follow these easy steps, and you will have your extension ready to use in no time.
Step 1: Download the KB SSL Enforcer Extension by clicking the "Download CRX" button on the website.
Look for the KB SSL Enforcer extension you wish to install. Go to the website and download the KB SSL Enforcer extension package, which is usually a .CRX file and comes in a zipped file. Here ".crx" file is the format for KB SSL Enforcer extension that contains all the data.
Step 2: Extract &Arrange Files
Once the file is downloaded, extract that file into its own folder. Similarly, give that extension files a permanent home. In other words, keep it in a folder that you don't accidentally delete it because these files will be needed to make that extension work.
Step 3: Go to the Chrome Extensions Page
Open Google Chrome and in the address bar, type chrome://extensions; it will open the Google Chrome extensions page. Make sure that "My extensions" is selected in the sidebar.
Step 4: Drag and Drop the Extension
Now, go to the folder where you extracted the KB SSL Enforcer extension and drag &drop the extension file from there anywhere onto the extension page within Google Chrome.
Step 5: Complete the Installation
Once you drag and drop the extension file, follow the steps that Google Chrome takes you through. Similarly, if the extension file is of .crx file format, you will be required to review the permissions and then add the extension.
Now, you can manage that added extension as you would like to with any other Chrome extension that you added through Chrome Webstore. Its icon will also appear in the Google Chrome Menu on the right side of the address bar once you activate it.
Method 2: Download KB SSL Enforcer extension for Chrome and install in Developer Mode
This is another method to install KB SSL Enforcer extension manually, but the twist is that here, you install by enabling the developer mode option provided in Google Chrome. This mode is commonly used for testing extensions or running unpublished tools.
Step 1: Download the KB SSL Enforcer extension file
Select and download the KB SSL Enforcer extension by clicking the 'Download CRX' button on the website.
Step 2: Extract the downloaded contents
Convert the file to a ZIP file if it is in CRX format then extract the KB SSL Enforcer extension zip file or folder that you downloaded. Make sure you extract it using the same folder name and keep it safely in another folder, so you don't delete it by mistake. The extracted folder will be needed to keep your KB SSL Enforcer extension running.
Step 3: Open Chrome Extension Setting Page
In the address bar of Google Chrome, type chrome://extensions and open the Chrome Extension Page.
Step 4: Enable Developer Mode
After opening the Chrome Extension page, look at the top right side, and you will find the toggle option of "Developer mode."Simply enable that developer mode option.
Step 5: Load the Unpacked Extension
Once you enable the developer mode option, you will see the menu of Load Unpacked, Pack Extensions and Update. From that, select the option "Load unpacked."
Step 6: Select the Extension Folder
Once the pop-up opens upon clicking Load unpacked, select the KB SSL Enforcer extension directory and click on the "Select Folder "button.
Step 7: Confirm and Install
After you select an extension folder of a Google Chrome extension you're installing manually, confirm its installation for the final time and let the installation complete.
Conclusion
Here we've made a step-by-step guide on How to manually install KB SSL Enforcer extension in 2 ways. We hope this guide proves helpful.
Similar Extensions
Certificate Info 20,000+ 20 ★ 18.09KiB
SKN SSL Enforcer 20,000+ 13 ★ 75.28KiB
Disconnect 20,000+ 3135 ★ 1017KiB
SSL Grade 20,000+ 14 ★ 56.41KiB
Force HTTPS (SSL/TLS) 20,000+ 5 ★ 23.24KiB
ScriptSafe 20,000+ 1720 ★ 751KiB
Smart HTTPS 20,000+ 31 ★ 115KiB
SSL to TLS 20,000+ 5 ★ 3.51KiB
Privacy Guardr 20,000+ 16 ★ 410KiB
Privacy Manager 20,000+ 166 ★ 90.21KiB
HTTPS Finder 20,000+ 25 ★ 319KiB
SSL Checker 20,000+ 15 ★ 87.32KiB
IronVest 20,000+ 4404 ★ 10.78MiB
uMatrix 20,000+ 810 ★ 1.39MiB
SSL/TLS安全评估报告 20,000+ 10 ★ 412KiB
TLSA Validator 20,000+ 23 ★ 95.55KiB
Decentraleyes 20,000+ 226 ★ 6.92MiB
ScriptBlock 20,000+ 445 ★ 161KiB
NoWall proxy (by NoWall) 20,000+ 60 ★ 16.28KiB
uBO-Scope 20,000+ 35 ★ 159KiB
Privacy Cleaner 20,000+ 83 ★ 7.82MiB
Proxxy 20,000+ 70 ★ 41.07KiB
UPPERSAFE 20,000+ 37 ★ 16.98KiB
Zalmos Web Proxy 20,000+ 37 ★ 20.3KiB
User reviews
Reynard (ID: 000000a1e011b368) Voted 5 ★ - Updated 11/28/2021
Gianni F (ID: 000000ff940b1eea) Voted 5 ★ - Updated 04/26/2021
Алексей путенихин (Юрьевич) (ID: 0000004f7ab66d41) Voted 5 ★ - Updated 03/29/2018
Ilya Stroganov (ID: 000000edb30e7235) Voted 5 ★ - Updated 04/14/2017
Eddie Atter (ID: 00000004450be582) Voted 5 ★ - Updated 01/30/2017