Oooh, even I shudder when reading that! :D
It's really about someone taking an undetected loan out in your name, credit card fraud is not a big deal to the regular consumer anymore.
I won't do anything with em, pinky-promise, but if something did happen, it doesn't matter, right? Just talk to Visa.
Like, why lock my car and house doors when insurance will pay for it?
Because you'll have a really hard time with a claim if there's no sign of forced entry, since many insurance policies are void in this situation?
Yes, just call them. By regulation, you're not liable for unauthorized use of credit card (specifically, credit card). As a consumer you have zero concerns about card theft.
If your attitude to security is "I can run my computer with unpatched XP with a public IP and sync it to a 7 year unpatched phone because once in a blue moon some credit card company or major business can leak my account data there too", then sure...
Might as well ask me to name "one" covid victim, lest they're all "actors".
My uncle, for one, had a randomsware attack 3 years ago, crippling his (small, construction services) company for weeks.
You are aware that there are tons of malware attacks, computers controlled as bots (doing mining, DDoS, etc.), ransomware, etc, right? Or is this some episode of the Twilight Zone?
https://www.csoonline.com/article/2923557/many-ransomware-vi...
https://krebsonsecurity.com/2019/12/ransomware-gangs-now-out...
https://www.securityweek.com/google-sophisticated-apt-group-...
https://www.securityweek.com/sierra-wireless-says-ransomware...
I don't use Google/Samsung Pay either. They literally do the same thing as the credit + debit card in my wallet. But their advertisements would have you believe they've somehow reinvented consumer finance.
Phone operating systems have so many issues that there's no way I'll trust them with any important data.
as soon as I want to do video calls at reasonable speeds, it's probably in my interest to have moderately new hardware and chipsets supporting things like beamforming or other things that only more recent hardware can give me. but even here my 8 yro phone does everything I want it to so that argument kicks only in for truly ancient hardware (e.g. LTE support etc)
I am using an HTC Desire 826 from 2016 running Android 6, while my father is using a Galaxy Note 3 Neo running Android 4.3.
I personally don't have much issues with regards to not having security patches.. the phone itself does most of what I want, although I am having issues with other things unrelated to security patches -- it's getting a bit sluggish, the 16GB storage does get annoying, and the battery barely lasts two hours of web browsing. Also, it no longer accepts SIM cards for whatever reason. But it's not a big deal to warrant spending money (I don't get called at all and I do have a dumb phone that I go out with for emergencies. Besides, I no longer get annoying messages and calls from my carrier)
Similarly, my father's is doing alright, and the issues he is facing are unrelated to security patches -- many apps don't support Android versions older than 6.. some of them are essential things like Google stuff. YouTube and Gmail for instance outright don't work, and Chrome occasionally brings up messages along the lines of "Please update your Chrome version". But nothing is caused by not having security patches.
What am I missing? This is a genuine question.
The prospect of truly long-term support for years and years is one reason I bought a PinePhone and have been keeping track of its development. But sadly the current PinePhone has too ancient and underpowered a CPU to be useful.
This issue is indicative of the larger problem ARM SoCs pose to consumers: manufacturers choose not to design ARM boards with SBSA-like features[1] because it's cheaper to do so. While x86 machines have enumerable buses for hardware discovery, as well as ACPI support, ARM SoCs don't. As a result, mainline Linux kernels won't boot on them, they require a kernel fork, and a kernel fork must be maintained. Manufacturers have no incentive to maintain that fork for more than a year or two.
As ARM SoCs take over what are considered general purpose computing devices, like laptops, devices that we once thought of as being upgradable, software-wise, suddenly aren't. Apple's M1 Macs are an example of this. To get Linux running on them is a massive undertaking, and running Linux on them in the long-term means relying on a third party to build and maintain M1-specific images in perpetuity, because the SoCs can't run the generic ARM images that ARM servers can run.
There are mitigations against this problem in Linux, like Device Tree[2] support, but that is only one small part of the big[2] undertaking when it comes to porting Linux to ARM SoCs.
[1] https://en.wikipedia.org/wiki/Server_Base_System_Architectur...
There have been tons of critical Android vulnerabilities over the last years that cannot be fixed by app updates, e.g. remote code execution via Bluetooth stack or MMS.
Yes. Because like windows the ecosystem is huge, and there are plenty of grandmas who don't know how or why to update things.
Much of the world can't afford to replace their phone every 2 years.