Sometimes people have to be inconvenienced for security
Don't disagree - but can't stop doing business either.
Managing all these exceptions is an operational nightmare that will create a load of technical debt.
No lie - and no argument there. But resetting the expiry date/time doesn't seem all that different than resetting any password. few clicks and poof.
I can understand your point, but some responsibility for security must fall on the user. Management of course has to buy in on this and/or give full control of IT policies to a CISO/IT manager/generalist (depending on size of business).
Again - no disagreement. Barring this - being able to set a date for the password to expire that isn't to far out of policy seems better and more ideal than some of the options.
Just a heads up on this. If you select their Ampere Arm processor you can have 4CPU with 24gb ram for free as well. VM has boot of 50GB but you can addon block storage for free up to 200GB I believe.
Ampere A1 Compute instances (Arm processor): All tenancies get the first 3,000 OCPU hours and 18,000 GB hours per month for free for VM instances using the VM.Standard.A1.Flex shape, which has an Arm processor. For Always Free tenancies, this is equivalent to 4 OCPUs and 24 GB of memory
This is all you have within the SonicWall control, on or off. I saw this yesterday and assumed I was missing something critical. The most basic APs in the world include the "Identify AP" functionality.
Apparently, SonicWall APs are more basic than basic as they don't include this functionality at all.
they have a flip phone, so SMS isn't an option, but those people are so few that it doesn't affect the masses.
Huh? Every flip phone and service I've had in the 90s and early 2000s had SMS texting.
That was definitely not my experience. I've had cell service continuously since 1992 and did not get access to texting until more like 2002 and never sent or received a text until I would guess after 2006. But I had email on my phone before that and talked with loads of people because it was common in business then, because of Blackberry devices, to have email on the phones. ANd because texting was costly and rarely available, they had Blackberry messenger instead of texting on the devices. We didn't use it, but it was there.
Not my own experience. Texting was big for me and my circle back then, regardless of your experience. Besides the point though... Being a flip phone had nothing to do with SMS.
I think the answer is, in the rare circumstance that SIP / T.38 is working perfectly, you would not change. We have big customers doing tons of faxing and they desperately need this solution because they can't get SIP / T.38 to an acceptable failure rate.
If you have an ideal setup - modern fax machine, fiber internet, correctly configured ATA (which is, by far, the biggest problem we've had - people just won't read the guides thoroughly), your expected failure rate is about 8% on a T.38 ATA. For small offices who send/receive a fax once in a couple of months, this is a fine solution.
HTTPS ATAs only fail when the party on the other end of the fax fails; which makes them at least as reliable as traditional POTS lines. They are probably more reliable because we will retry the fax 9 times before failing it. So if you need near 100% reliability, you need to use the HTTPS ATAs.
The reason we are charging monthly for the ATAs is because that is how we are charged for them. We have to buy software for these things to work, and its expensive. Most of our competitors who offer HTTPS ATAs charge north of $15/mo.