Yeah &F is factory default, M1 is speaker on only until connect, S11=35 is the dial speed (although we later learned that 50 ms is the minimum). Dial speed was important because we’d have Telemate on constant redial trying to get into the BBSes that were popular but were busy because they only had one or two phone lines.
FYI, making you the product is only a tiny part of their stated reasoning:
In Chromium browsers you can simply type “thisisunsafe” to bypass even HSTS failures.
They mean CAA records:
https://developers.cloudflare.com/ssl/edge-certificates/caa-records/
What the fuck are you on about? Are people traveling with an entire Lowe’s warehouse in their fucking luggage?
That’s good advice, especially when traveling internationally.
Also when traveling to another country, always check the state department’s travel advisory for your destination(s).
Obviously this is the US state department, but it is still good info and I’d assume other countries have something similar.
Their country, their rules. One bullet can still kill someone. Play stupid games, win stupid prizes.
Most likely it was a password stuffing attack. If they used the same password on multiple sites, there is a good chance one of those other sites was compromised and the attackers took the compromised credentials and tried them on other sites like Instagram. It could have been something more advanced like a stolen cookie, but usually the simplest explanation is most likely.
Always use a different password for each service, enable MFA where possible, and use a password vault like Bitwarden.
Don’t worry, the FBI confiscated all of their phones but they received other phones and SIMs without data.
You need to demand a raise. And keep working from home.
I agree as long as the money is actually going toward building out the charging network and not just getting sucked up by corporations like the ISPs that were supposed to improve our network infrastructure.
Although it would be nice for them to let us know what is happening and when we can expect some real improvements. Maybe that info is out there, but I haven’t seen it and this biased reporter sure isn’t looking to do any real journalism.
Right, because international hackers are going to mobilize boots on the ground across the world to steal your fucking Optiplex.
And similarly, why can’t Star Trek officers just set it to wide beam and/or just hold down the button while they paint the room?
Yep totally. The documentation is downright wrong so much more today than it used to be. It’s all written like they pawned it off on a junior engineer, who then threw shit at the wall until they got it working, then that process becomes the official documentation.
And don’t get me started on Copilot hallucinating Powershell cmdlets.
With support it’s become kind of a game to see how quick you can get to T2. My tactic is to passive aggressively point out how their first response shows a complete lack of understanding of the topic, then directly request escalation.
The reality is they probably don’t know the full scope or root cause and are going off of limited reporting coming from their beta channels.
But they likely determined the impact was low enough that they could still ship the update while they investigate further.
There are similar known issues reported in the update KBs all the time that sound much worse to me as an admin but are as equally low impact in the end. But they’re not as easy for the layperson to latch onto like these low-effort “VPN no worky” articles.
Regardless, none of this absolves IT of the responsibility of testing patches.
Exactly. Everybody on Lemmy a couple days ago was acting like the sky was falling when all we had were these one-paragraph FUD articles quoting Microsoft’s own KB article. Most people commenting have no clue that “VPN” is a broad term covering at least a dozen different possible protocols and acted like Microsoft was intentionally breaking all VPNs.
The only thing I found was a reddit thread talking about how some VPNs using TPM-backed certs were broken. I, for one, am using an IPsec VPN with certs stored in TPM on one of the affected versions of Windows 11 and have had no problems. Nor have I had any issues with SSL or Wireguard-based VPNs, so it does just seem to be a fringe case they’re warning about.
So Microsoft is just giving a heads-up that IT should probably include VPN testing in their patch cycle test rings and all the anti-MS people are losing their shit.
The rootkit is easy enough to turn off in the BIOS but I highly, highly recommend G-Helper instead of Armoury Crate.
Moving to it from AC is like leaving a prison cell full of screaming children and entering a calm beach.
Yeah, but that security patch level.