Three digits is not that easy to get by brute force. It'll be locked for fraud pretty quickly.
However the CVV is usually only required for card-not-present purchases. One way around that is to imprint the number onto their own magstripe card and run it as a card-present transaction.
The advantage of this is it keeps paying off even years later.
We put googly eyes on an oscillating fan (among many other things) at the beginning of the pandemic and they still make me giggle every time I see them.
Adding my vote for Zabbix. It was a bit of a bear to set up and I had to write custom scripts to install the agents with TLS settings that were secure enough for me, but once it's all set up it's amazingly easy and intuitive to use and incredibly customizable.
Just mark it as final then. This whole thread is infuriating. People working themselves into pretzels with their misguided reasons for not wanting auto-save when they really just don't know to use the software.
OP is right. I use Office 365 and haven't lost work on a document in over 10 years. Auto-save absolutely should be the default.
Yeah, I personally will only use hardware solutions for passkeys -- YubiKeys and TPM-backed WHFB creds.
But the other reply makes a very good point about adoption being more important than perfection since, even with software-backed passkeys, you still have the benefit of the secret never leaving the client.
Yep! In fact you can still use client certificates in certain passkey/WebAuthN authentication flows. It's more or less how Windows Hello for Business works (although X.509 certificates are only one type of key it supports).
Yes it does make sense. Because the insurance companies operate completely on hypotheticals. And that has a very real cost to the business being insured.
I'm always reminded of this video when I think about just how bad AR could be. But then again, it could be pretty cool if we can only keep control over our tech.
Its about time. My stomach was making the rumblies.