SKN SSL Enforcer allows you to browse the web securely on websites that support HTTPS.
SKN SSL Enforcer does not use proxy servers or similar methods to establish HTTPS tunnels. It relies solely on the website’s support of HTTPS and the defined ruleset.
SKN SSL Enforcer will intercept web requests made by your browser which match the ruleset and attempt to rewrite them using HTTPS. This process happens before the browser opens a network connection, ensuring all data (headers and content) is encrypted in transit.
! What’s new?
– bugfixes, ui and performance improvements
– bugfixes and performance improvements
– ability to sync default ruleset with active ruleset
– bugfixes and ui improvements
– If you add a website to the ruleset, make sure it supports HTTPS. Not all websites support it and SKN SSL Enforcer will not check if HTTPS is available before redirecting the request. Some websites may fail to load if they match a rule but do not support secure browsing over HTTPS.
– Some websites only implement HTTPS for certain URLS (ie: login pages) and will insist on HTTP for everything else. SKN SSL Enforcer will detect redirect floods on a matched rule and HTTPS will not be enforced.
– SKN SSL Enforcer is always being improved and you may encounter issues loading websites, browser performance degradation, etc. If this is the case, please submit as much information as possible to: https://github.com/slackr/sslenforcer/issues
If you have any questions, comments or feature requests, you can submit a new issue via: https://github.com/slackr/sslenforcer/issues
Contributors are always welcome: https://github.com/slackr/sslenforcer. Feel free to fork the code and submit any improvements/bugfixes.