edik

Secures the backend AND the frontend with ssl when you are logged in. If a user logs in and calls a http site you will be redirected to the equivalent https site. You do not have to manually define <code>FORCE_SSL_ADMIN</code> in the <code>wp-config.php</code>. The authentication cookies will be ssl secured.
<h4>Warning</h4>
There is no protection against ssl leaks. If you follow a http link, a <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack" rel="nofollow ugc">men in the middle</a> could, for example, see which site you enter.
But he cannot steal your login session! 😀

Secured Users Front

Secures the backend AND the frontend with ssl when you are logged in

Janis Elsts

Normally when you login to your blog WordPress will create a session cookie that is used to authenticate you. If someone was to steal the cookie they would be able to use it to get full access to your blog without having to know your password. This plugin prevents that from happening – it makes the cookie specific to your IP address, so it won’t be usable from a different computer.
Use this plugin if you have a static IP. If you have a dynamic IP address and it changes often you will get logged out frequently.
A bit more info can be obtained from the <a href="http://w-shadow.com/blog/2008/07/12/safer-cookies-plugin-for-wordpress/" title="Safer Cookies homepage" rel="nofollow ugc">Safer Cookies homepage</a>

Safer Cookies

Ties the WP session cookie to your IP address so that it can't be used to get access to you blog from another computer.

Secured Users Front vs Safer Cookies