RootsWeb.com Mailing Lists
Total: 2/2
    1. [FreeHelp]Re: FREEPAGES-HELP Digest, Vol 13, Issue 126
    2. Warwick Sherring
    3. Judy I realise the reason for the current messing about.  My point is, how come it took so long to do something about it and why no mention of the reason? Warwick Sherring On 29/07/2018 6:00 PM, freepages-help-request@rootsweb.com wrote: > Send FREEPAGES-HELP mailing list submissions to > freepages-help@rootsweb.com > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > freepages-help-request@rootsweb.com > > You can reach the person managing the list at > freepages-help-owner@rootsweb.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of FREEPAGES-HELP digest..." > > When replying to a digest message, quote only the specific message to which you are replying, removing the rest of the digest from your reply. Remember to change the subject of your reply so that it coincides with the message subject to which you are replying. > ***FREEPAGES HELP & FAQ*** > <http://helpdesk.rootsweb.com/FAQ/fpindex.html> > > Today's Topics: > > 1. Ancestry Security (Warwick Sherring) > 2. Re: Ancestry Security (JFlorian) > > > ---------------------------------------------------------------------- > > Date: Sun, 29 Jul 2018 13:04:01 +1000 > From: Warwick Sherring <warwick.sherring@bigpond.com> > Subject: [FreeHelp]Ancestry Security > To: <freepages-help@rootsweb.com> > Message-ID: <b5e9302f-7c7e-041c-f603-da2d8c7030dd@bigpond.com> > Content-Type: text/plain; charset="utf-8"; format=flowed > > I have just tested my email address for security on Firefox's Monitor > and it revealed a security breach in Ancestry on November 7th 2015. > > The compromised data was email addresses and passwords. > > Comprised accounts: 297,804 > > I can not recall any mention at the time and I certainly did not receive > any suggestion at the time to change my password. > > you can access the tool at: https://monitor.firefox.com > > Warwick Sherring > > ------------------------------ > > Date: Sun, 29 Jul 2018 03:49:38 -0400 > From: JFlorian <cageycat@gmail.com> > Subject: [FreeHelp]Re: Ancestry Security > To: Freepages Web Sites <freepages-help@rootsweb.com> > Message-ID: > <CAE5hz-DD-XbTTa=E6rR5+Cf81wKtCmQhPSg5O+hn8mRp-CO40w@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Warwick, > > Why do you think they took all sites offline last Dec? > > What do you think all the uproar is about as they try to restore sites now? > > Judy > > ------------------------------ > > Subject: Digest Footer > > -To contact the freepages-help list administrator, send an email to freepages-help-admin@rootsweb.com. > -To post a message to the freepages-help mailing list, send an email to freepages-help@rootsweb.com. > __________________________________________________________ > To unsubscribe from the list, please send an email to freepages-help-leave@rootsweb.com with the word "unsubscribe" without the quotes in the subject and the body of the email with no additional text. > > ------------------------------ > > End of FREEPAGES-HELP Digest, Vol 13, Issue 126 > ***********************************************

    07/29/2018 03:32:33
    1. [FreeHelp]Re: Ancestry Security
    2. Pat Asher
    3. At 05:32 AM 7/29/2018, Warwick Sherring wrote: >Judy > >I realise the reason for the current messing >about. My point is, how come it took so long >to do something about it and why no mention of the reason? 1. The incident reported to you by Firefox occurred in Dec 2015, more than two years ago. The 2015 incident was a hack of Ancestry servers and Ancestry accounts. I was asked at that time to update my Ancestry password. 2. The current incident was an "open" text file discovered on a Rootsweb.com server. It was reported to Ancestry by a white hat hacker on 20 Dec 2017. 3. The vulnerability was immediately investigated and after it was verified, two days later on 23 Dec 2017 Ancestry took RootsWeb offline and started notifying affected users. 4. A complete explanation was posted on the Ancestry blog on 23 Dec 2017. <https://blogs.ancestry.com/ancestry/2017/12/23/rootsweb-security-update/> Pat A.

    07/29/2018 08:27:31