Cuidado com o KB Enforcer SSL, o HTTPS Everywhere parece bastante cauteloso.
A página principal afirma
There is a Chrome extension called KB
SSL Enforcer which attempts to take
that approach, but it does not appear
to be implemented securely; when we
tested it, it seemed to always use
http before https, which means that
your surfing habits and authentication
cookies are not protected (this may be
a limitation of the Chrome Extensions
framework).
Há também uma entrada específica na FAQ sobre o tópico complementar de uma lista mais ampla perspectiva:
Q. Will there be a version of HTTPS Everywhere for Chrome? Or IE, Safari,
Opera, or some other browser?
A. Our understanding is that the
Chrome extensions API does not support
request rewriting. That means that
there is currently no way to write a
secure version of HTTPS Everywhere
without modifying the Chrome source
code. However, Chrome's developers
have shown interest in supporting
extensions of this sort, so this
limitation may change in a future
version of Chrome. We believe the IE
and Safari APIs have similar
limitations. But if you happen to know
a way to perform secure request
rewriting in these browsers, feel free
to let us know at https-everywhere at
EFF.org (but note that modifying
document.location or window.location
in JavaScript is not secure).
Observação: Para uma navegação mais segura, os links fornecidos redirecionarão um para a página https ;-)
Nota 2: O autor do KB SSL Enforcer está bem ciente do problema (cf. issue # 25 )