Yeah, but that security patch level.
Yeah, but that security patch level.
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.
I believe you. I’m just saying their non-firewalls (i.e., switches and APs) don’t have that limitation.
My firewall is a Fortigate 60F.
I would never use their firewalls/gateways, but their switches are pretty good for the price and their APs are decent (although tbh after 3 generations my next AP will likely be an enterprise Aruba).
That said, I still use Unifi in docker, everything is up to date, and nothing is requiring a sign-in to the cloud. Am I missing something? If it’s just the firewalls, then I’m not surprised since I’ve never been remotely tempted to use them, but it sure isn’t all of their devices.
FYI, making you the product is only a tiny part of their stated reasoning:
The definition I learned for web 2.0, as it was happening, was a shift from static web pages generated all at once on the server and delivered to the client whole, to using Ajax with in-browser Javascript dynamically changing already-delivered pages with back-end XML calls.
Look man, it’s okay to be wrong. It’s a natural part of growth.
But when you double down on your ignorance instead of taking the opportunity to open your mind and listen to the experts in the room, you just end up embarrassing yourself.
Try to be better.
We can restrict the use of software TOTP, which is what companies are doing when they move users onto the MS Authenticator app.
Admins can’t control the other TOTP apps like Google Authenticator or Authy unless they go full MDM. And I don’t think someone worried about installing the MS Authenticator app is going to be happy about enrolling their phone in Intune.
Edit: And even then, there is no way to control or force users to use a managed device for software TOTP.
This is incredibly well said and I agree 100%. I’ll just add that software TOTP is weaker than the MS Authenticator with number matching because the TOTP seed can still be intercepted and/or stolen by an attacker.
Ever notice that TOTP can be backed up and restored to a new device? If it can be transferred, then the device no longer counts for the “something you have” second factor in my threat model.
While I prefer pure phishing-resistant MFA methods (FIDO2, WHFB, or CBA), the support isn’t quite there yet for mobile devices (especially mobile browsers) so the MS Authenticator is the best alternative we have.
And what’s wrong with asking that? Plenty of email platforms let you change your primary SMTP address and/or add/remove aliases.
It’s a legitimate question. And it could be that the lack of ability to change it has a perfectly logical answer. It still wouldn’t invalidate the question.
I have several docker servers, but for Immich I want a dedicated VM. Regardless the problem isn’t going to be setting it up, that should be easy. But for something as important as this, I am going to pore over every possible architectural design decision from the storage tier to the HA and DR strategy. I don’t want to start migrating to it then realize I wanted to do something differently and have to migrate again.
If it’s replacing Google Photos for my family, I expect the same level of resiliency and data protection standards. Or at least as close as I can reasonably get.
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/
That’s been my plan to move off of Google photos. Decided on Immich a few months ago. Now if only I had some more of that free time to set it up.
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.
You need to demand a raise. And keep working from home.
I found it amusing that these posts were adjacent.