I rebooted an old (2012) MacBook Pro on my internal network.
-
I rebooted an old (2012) MacBook Pro on my internal network. It’s been connected to my Apple Account (Apple ID) since it was new.
Treating this like some brand new device that represents a security threat every single time it reboots — with redundant, simultaneous alerts to my other Macs, iPhone, & iPad — actually undermines security by training me to ignore these endless, false-positive alerts.
A well-intentioned choice backfiring. #Apple #macOS #security
-
I rebooted an old (2012) MacBook Pro on my internal network. It’s been connected to my Apple Account (Apple ID) since it was new.
Treating this like some brand new device that represents a security threat every single time it reboots — with redundant, simultaneous alerts to my other Macs, iPhone, & iPad — actually undermines security by training me to ignore these endless, false-positive alerts.
A well-intentioned choice backfiring. #Apple #macOS #security
@tantramar presumably because its certificates expired & re-negotiated, but I concur the spurious alerts attenuate critical response.
(That's not a Monday morning thing to write....)
-
@tantramar presumably because its certificates expired & re-negotiated, but I concur the spurious alerts attenuate critical response.
(That's not a Monday morning thing to write....)
@mWare That “Late-2012 MacBook Pro with Retina Display” — to use its full, proper name — is stuck at Catalina (macOS 10.15, I believe). Expired certs are almost certainly behind this. Nevertheless…
-
I rebooted an old (2012) MacBook Pro on my internal network. It’s been connected to my Apple Account (Apple ID) since it was new.
Treating this like some brand new device that represents a security threat every single time it reboots — with redundant, simultaneous alerts to my other Macs, iPhone, & iPad — actually undermines security by training me to ignore these endless, false-positive alerts.
A well-intentioned choice backfiring. #Apple #macOS #security
@tantramar My up-to-date M1 does this essentially every time I turn it on, because I only turn it on once a month or two. It's just dumb. If they want to send me an alert because they think it's unusual that it's on, fine, whatever. But don't act like it's a new device.
-
I rebooted an old (2012) MacBook Pro on my internal network. It’s been connected to my Apple Account (Apple ID) since it was new.
Treating this like some brand new device that represents a security threat every single time it reboots — with redundant, simultaneous alerts to my other Macs, iPhone, & iPad — actually undermines security by training me to ignore these endless, false-positive alerts.
A well-intentioned choice backfiring. #Apple #macOS #security
@tantramar that's annoying.
Interesting, I have a 2012 Mac I still use sometimes, and a 2006 that even gets booted rarely, but haven't seen it. Wondering if it's because I've always avoided iCloud and iMessage features that maybe saves me.
-
@tantramar My up-to-date M1 does this essentially every time I turn it on, because I only turn it on once a month or two. It's just dumb. If they want to send me an alert because they think it's unusual that it's on, fine, whatever. But don't act like it's a new device.
@mariellequinton It’s almost enough to make my sympathize with people who don’t want to update their operating systems*.
As in “give me an option to never see this alert ever again”.
*I mean, not quite, because that’s clearly insane on multiple levels.
-
@tantramar that's annoying.
Interesting, I have a 2012 Mac I still use sometimes, and a 2006 that even gets booted rarely, but haven't seen it. Wondering if it's because I've always avoided iCloud and iMessage features that maybe saves me.
@ottaross Super annoying. I suspect you’ve nailed the reason.
-
I rebooted an old (2012) MacBook Pro on my internal network. It’s been connected to my Apple Account (Apple ID) since it was new.
Treating this like some brand new device that represents a security threat every single time it reboots — with redundant, simultaneous alerts to my other Macs, iPhone, & iPad — actually undermines security by training me to ignore these endless, false-positive alerts.
A well-intentioned choice backfiring. #Apple #macOS #security
The other really stupid things about this alert:
1) “Device Added to Your Account” is not true. A device that’s been part my account for more than a decade has rebooted. Because it falls flat on its face every 36–48 hours and has to be helped back to its feet.
2) “If you don’t recognize this device…” You don’t provide any information that would help me to identify this device in the exceedingly rare edge case where it’s not something harmless.
So non-actionable fear-mongering.
-
@mariellequinton It’s almost enough to make my sympathize with people who don’t want to update their operating systems*.
As in “give me an option to never see this alert ever again”.
*I mean, not quite, because that’s clearly insane on multiple levels.
@tantramar Why do they act like it's so hard to have multiple alert types? They know these machines, they know they aren't new and haven't changed users. They're on the same network as the iPad etc they just sent the alert to. Make it a low level "hey, your machine just connected to the network" not "omg, a new machine just connected to your account". And yes, I could totally see people refusing to update or getting sufficiently irritated that they figure out how to turn off all the alerts.
-
@mWare That “Late-2012 MacBook Pro with Retina Display” — to use its full, proper name — is stuck at Catalina (macOS 10.15, I believe). Expired certs are almost certainly behind this. Nevertheless…
@tantramar I mean for personal PKK stuff (E2E encrypted messaging etc)
-
I rebooted an old (2012) MacBook Pro on my internal network. It’s been connected to my Apple Account (Apple ID) since it was new.
Treating this like some brand new device that represents a security threat every single time it reboots — with redundant, simultaneous alerts to my other Macs, iPhone, & iPad — actually undermines security by training me to ignore these endless, false-positive alerts.
A well-intentioned choice backfiring. #Apple #macOS #security
@tantramar I think the rationale here is, if a device was lost or stolen, that someone has gained access to it by discovering your password (and not multi-factor authentication).
Of course, the proper solution here is to enforce MFA on the dormant device — requiring that it be online, and report its location to you before prompting you for a token.
But I guess that would be annoying as well.
-
R relay@relay.mycrowd.ca shared this topic
