@linkomatic HTTPS can be enabled by editing the wp-config.php file for your site. There are two lines you could add, and the description of them and what they are and their function can be read about here: https://codex.www.ads-software.com/Administration_Over_SSL
One just forces logins over HTTPS, and the other forces both logins and the Admin page to go over HTTPS.
You need to make sure your web server (hosted or self hosted) is configured for HTTPS connections. Most offer this as a part of their service, but using an SSL certificate that’s not specific to your web site. This will trigger browser warnings that the site you’re connecting to uses a certificate that does not match the URL.
However, if you as the admin are the only one loggin into your site, then this is a non-issue. You just accept the connection and life is good.
The plus is that you won’t have people sniffing your usernames and passwords to your site, or hijacking your sessions after you’ve logged in. This is becoming an ever more common way for sites to get compromised. I was at a conference a while back, and I cringed every time I saw a speaker log into a live/customer’s site over the hotel provided wireless network, over plain, unencrypted HTTP.
The down side is that many developers don’t anticipate people securing their admin pages with HTTPS, and will often have plugins that break because the plug-ins try to connect to the control panel via hard coded HTTP. In this case, you either have to fix the plug-in, get the developer to do it, or abandon its use. EZPZ is one of these.