Wordfence update process

  • Daedalon

    (@daedalon)


    9 years, 3 months ago

    Hi, noticed a bit of a silly thing today. An email at 2:55 AM (14 hours ago) stated:

    [Wordfence Alert] Problems found on [sitename]
    …
    Warnings:

    * The Plugin “Wordfence Security” needs an upgrade (6.3.1 -> 6.3.2).

    Then I got another one at 1:57 PM (3 hours ago):

    [Wordfence Alert] [sitename] Wordfence Upgraded to version 6.3.2

    I was first wondering about why the two emails; why was I notified that Wordfence needs an update, as it was about to be updated automatically, likely immediately? There were no other plugins needing an update according to this email.

    Then I also noticed that there were 11 hours in between Wordfence noticing it itself needs an update and acting on it. That’s 11 hours more for an attack window.

    Wouldn’t it be better to update Wordfence as soon as it’s noticed to be out of date, and send only one email about it?

Viewing 1 replies (of 1 total)
  • mountainguy2

    (@mountainguy2)

    9 years, 3 months ago

    In my case, I’d rather I knew about the update, and it was subsequently delayed. I like the chance to examine the support forum after an update and see if people are reporting that it might be flawed, before it gets installed on my site. That way I can choose to not have it install until further evaluation. I’ve had automatic “updates” of various plugins, as well as WordPress, break my sites many times.

    Most of the Wordfence updates are quite minor, delaying them is the least of our worries when it comes to “attack windows.”

    MTN

Viewing 1 replies (of 1 total)

The topic ‘Wordfence update process’ is closed to new replies.