Disabling Firefox insecure password form warning

While I believe in security in general, and in SSL-certificates as a means for that, it gets quite annoying to have the newly released password form warning for several of my sites.

In particular my home router and my intranet NAS-box at home, which prefers http login, even though the NAS actually comes with an https-variant, which unfortunately does not work very well since it uses a self-signed certificate issued to QNAP NAS, and therefore does not match the hostname/URL of my configured NAS. Which still creates warnings and needs for exceptions and so on rather than actually helping out.

But anyway, the point of this post was not about QNAP, (who beyond this little misstep makes a splendid product), but about how to disable the insecure password form warning in Firefox, and also how to re-enable password autofill on http sites again.

So. Here’s how to disable Firefox insecure password warnings:

  1. Open a new tab, paste about:config into the address bar.
  2. In the Search box at the top, paste insecure_field_warning.contextual.enabled
  3. Double click the setting to change it to “false”, to disable Firefox’s insecure password warning.

To also restore autofill functionality, so saved login/password automatically populates in an HTTP form here’s how:

  1. In the Search Box on the about:config page, paste signon.autofillForms.http
  2. Double click the setting to change it to “true,” to enable autofill

And I believe the old joke on doing unsafe things you shouldn’t used to come with the warning “don’t do this at home!”… 😉

One thing I would like very much however is for Binero to come up with their planned support for free SSL-certificates through some 3rd party provider. (I believe Let’s Encrypt was mentioned in a comment to a blog post a while back but now I can no longer even find that specific blog post so it might have been deleted).

 

 

Advertisements

Quarterly website backup done

WordPress has become quite stable with their new automatic update functionality. So stable that it’s to forget making proper backups, and just rely on the webhost to have this (which is not the case here) and the auto-update to always work (which so far has been the case).

But since the last backup was just before new years, it seemed like a good time to go about this painful task again. Painful because the way to backup the sites from the service provider is through FTP, and because the FTP connection gets disconnected over and over, with an error message that I’m over limit of 10 simultaneous connections, which is interesting since I’ve set FileZilla to never go above 8.

I’ve tried to lower it to 5 connections, and while the error won’t go away, it at least reconnects more quickly, less waiting time for sessions to die I would guess.

But now I’m done for this time, 4 websites, plus mySQL databases, 50000 files, and about 1,75 GB of data saved to local device for later transfer to bank vault.