[Lex Computer & Tech Group/LCTG] FW: Turn on Facebook Protect

Sat Mar 19 09:12:52 PDT 2022

Sorry to belabor the point. From what I've read, Facebook Protect is
enabling 2FA for authentication. Additionally, it's activating some other
security measures like identifying your primary country for posting (to
prevent disinformation) and ensuring that Page admins are using an account
with their real name. At least, that's what I read.

I also read many people complaining that a) the emails look like a phishing
attempt; b) they're not receiving the text messages once activated; and c)
Facebook's threat to turn off accounts on March 17th is pretty draconian.

Jerry

On Sat, Mar 19, 2022 at 12:02 PM Robert Primak <bobprimak at yahoo.com> wrote:

> I have posted a message with more details about 2 Factor Authentication
> (2FA) in response to another message in this exchange, which is not part of
> the same Conversation in my gmail view.
>
> Facebook Protect seems to be a bit more than standard 2FA, but it looks
> like it operates in a similar fashion.
>
> -- Bob Primak
>
>
>
> On Saturday, March 19, 2022, 11:58:45 AM EDT, Jerry Harris <
> jerryharri at gmail.com> wrote:
>
>
> Hi Barry,
> On the scale of vulnerability, email is the most vulnerable followed by
> SMS followed by an authentication app followed by a USB security key.
>
> For a hacker to intercept your cell phone messages, they will most likely
> need to have hacked your email as well. The hacker calls your phone
> provider to convince them that they are you and that "you've" lost your
> phone and need to have all calls and SMS messages diverted to a new SIM
> card. The phone provider may email a one-time code that the hacker would
> have to provide, although hackers can usually get around this, too.
>
> One key weakness with authentication apps is when you switch phones and
> neglect to pair the new device to the service provider (eg, email,
> Facebook, etc). I speak from experience and didn't remember until I'd
> already wiped the old phone.
>
> Jerry
>
>
>
> On Sat, Mar 19, 2022 at 11:17 AM <bhff02 at aol.com> wrote:
>
> Jerry: Why would an SMS message be the most vulnerable to hacking? I
> always assumed that email is the most vulnerale, given the frequency at
> which email accounts are hijacked... especially if one uses a weak or
> redundant password.
>
> Barry Hass
>
>
> -----Original Message-----
> From: Jerry Harris <jerryharri at gmail.com>
> To: john rudy <jjrudy1 at comcast.net>
> Cc: Lex Computer Group <LCTG at lists.toku.us>
> Sent: Sat, Mar 19, 2022 10:58 am
> Subject: Re: [Lex Computer & Tech Group/LCTG] FW: Turn on Facebook Protect
>
> While high-profile users might be favored targets of hackers (who are
> using the accounts to promote scams), the rest of us should also take
> precautions. This is from Toms Guide on how to enable two-factor
> authentication on Facebook.
>
> How to enable Facebook's two-factor authentication
>
>     Click Account at the top right of the Facebook web page
>     Click Settings & Privacy in the drop-down menu
>     Click Settings in the next page of the drop-down menu
>     Click Security and Login in the left-hand navigation bar
>     Scroll down to Two-factor authentication and enable it
>
> The easiest way to receive 2FA one-time-use codes is via SMS text
> messages, but it's also the method that's most likely to have 2FA codes
> intercepted by hackers.
>
> We recommend instead installing a free authentication app, such as Authy
> or Google Authenticator, on your smartphone, which will generate 2FA
> one-time-use codes right on your phone. Even safer are USB security keys,
> but you have to buy those before you can use them.
>
>
>  Jerry
>
> On Sat, Mar 19, 2022 at 10:51 AM john rudy <jjrudy1 at comcast.net> wrote:
>
> This is why I need it, Michael.  Apparently the request is real, as best
> as I can determine.  I run a Facebook group which maybe is why I got this.
> Many of you probably don’t need it
> John
>
> John Rudy
> 781-861-0402
> 781-718-8334 (cell)
> John.rudy at alum.mit.edu
>
> 13 Hawthorne Lane
> Bedford, MA  01730-1047
>
> *From:* Facebook <security at facebookmail.com>
> *Sent:* Saturday, March 19, 2022 8:59 AM
> *To:* John Rudy <jjrudy1 at comcast.net>
> *Subject:* Turn on Facebook Protect
>
>
> Turn on Facebook Protect
>
>
>
> <https://www.facebook.com/n/?aref=1647694713245949&medium=email&mid=5da91887ece2bG5c47ea2eG5da91d214d0fdG41dd&n_m=jjrudy1%40comcast.net&rms=v2&irms=true>
>
> Facebook
> <https://www.facebook.com/n/?aref=1647694713245949&medium=email&mid=5da91887ece2bG5c47ea2eG5da91d214d0fdG41dd&n_m=jjrudy1%40comcast.net&rms=v2&irms=true>
>
>
>
>
> *Your account requires advanced security from Facebook Protect*
>
> Hi John,
>
> Your account has the potential to reach a lot more people than an average
> Facebook user. Hackers are often motivated to attack accounts that have a
> lot of followers, run important Pages, or hold some community significance.
>
> To help defend against these targeted attacks, we require Facebook Protect
> for your account.
>
> Turn on Facebook Protect for your account by *27 March 2022*. After that,
> you will be locked out of your account until you enable it.
>
> *• *
> We’ve already turned on advanced login protections for your account.
> *• *
> To fully enable Facebook Protect, we’ll check your account for
> vulnerabilities, and help you resolve them.
>
> John Rudy
> Turn On Facebook Protect
> <https://www.facebook.com/n/?fbprotect%2Femail&aref=1647694713245949&medium=email&mid=5da91887ece2bG5c47ea2eG5da91d214d0fdG41dd&n_m=jjrudy1%40comcast.net&rms=v2&irms=true>
>
> *Note: Facebook Protect isn’t available to everyone on Facebook. We
> require stronger security for your account because it has the potential to
> reach a large audience. *
>
> Thanks so much,
> The Facebook Team
>
>
>
>
>
> This message was sent to jjrudy1 at comcast.net at your request.
> Meta Platforms, Inc., Attention: Community Support, 1 Facebook Way, Menlo
> Park, CA 94025
>
>
>
> ===============================================
> ::The Lexington Computer and Technology Group Mailing List::
> Reply goes to sender only; Reply All to send to list.
> Send to the list: LCTG at lists.toku.us      Message archives:
> http://lists.toku.us/private.cgi/lctg-toku.us
> To subscribe: email lctg-subscribe at toku.us  To unsubscribe: email
> lctg-unsubscribe at toku.us
> Future and Past meeting information: http://LCTG.toku.us
> <http://lctg.toku.us/>
> List information: http://lists.toku.us/listinfo.cgi/lctg-toku.us
> This message was sent to jerryharri at gmail.com.
> Set your list options:
> http://lists.toku.us/options.cgi/lctg-toku.us/jerryharri@gmail.com
>
> ===============================================
> ::The Lexington Computer and Technology Group Mailing List::
> Reply goes to sender only; Reply All to send to list.
> Send to the list: LCTG at lists.toku.us      Message archives:
> http://lists.toku.us/private.cgi/lctg-toku.us
> To subscribe: email lctg-subscribe at toku.us  To unsubscribe: email
> lctg-unsubscribe at toku.us
> Future and Past meeting information: http://LCTG.toku.us
> <http://lctg.toku.us/>
> List information: http://lists.toku.us/listinfo.cgi/lctg-toku.us
> This message was sent to bhff02 at aol.com.
> Set your list options:
> http://lists.toku.us/options.cgi/lctg-toku.us/bhff02@aol.com
>
> ===============================================
> ::The Lexington Computer and Technology Group Mailing List::
> Reply goes to sender only; Reply All to send to list.
> Send to the list: LCTG at lists.toku.us      Message archives:
> http://lists.toku.us/private.cgi/lctg-toku.us
> To subscribe: email lctg-subscribe at toku.us  To unsubscribe: email
> lctg-unsubscribe at toku.us
> Future and Past meeting information: http://LCTG.toku.us
> List information: http://lists.toku.us/listinfo.cgi/lctg-toku.us
> This message was sent to bobprimak at yahoo.com.
> Set your list options:
> http://lists.toku.us/options.cgi/lctg-toku.us/bobprimak@yahoo.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.toku.us/pipermail/lctg-toku.us/attachments/20220319/3733e2e1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 27675 bytes
Desc: not available
URL: <http://lists.toku.us/pipermail/lctg-toku.us/attachments/20220319/3733e2e1/attachment.png>