Live data from Hacker News

Google confirms Android attacks; no fix for most Samsung users

forbes.com

71–80 of 177 posts

Re: Google confirms Android attacks; no fix for most Samsung users

#71
post #29

Earlier quoted context omitted.

The problem is that each OEM releases 50 different models per year, vs Google (or Apple) that release 3 or 4 models.

If that truly is an issue then Android is a fundamentally broken OS. How many different models of PCs get released? How hard is it to patch any of their OSs?

But how are they doing to do the artificial market segmentation otherwise ?

(E.g. Samsung still limits Now brief to latest devices even though it is a 99% software feature + 1% cloud with 0 hardware requirements.)

Re: Google confirms Android attacks; no fix for most Samsung users

#72
post #33

Earlier quoted context omitted.

> Being reliant on the hardware manufacturer (or network operator?) for OS updates is the crazy world we live in. Being reliant on a single OS permanently nailed to the hardware is no less crazier. I'd like to be able to install another OS on a vulnerable device, it would help tremendously and not only with the security of that specific device. Now I've got some expensive paperweights that I can't even use as such be…

Please try to e-recycle rather than normal land-fill trash.

e-recycling is only marginally better than a landfill. At least a landfill in pseudo-regulated government economy has the chance to be safely abated in 100 years. Though a few things of value are sometimes extracted, mostly it all ends in places like Turkey or India and burned or buried.

Sorry for the cynical take, but patronizing folks like this is worse than cynicism because it suggests that you actually believe what you're saying is true.

Re: Google confirms Android attacks; no fix for most Samsung users

#73

Earlier quoted context omitted.

As Randall Munroe pointed out in https://blog.xkcd.com/2010/05/03/color-survey-results/ , almost nobody knows how to spell "fuchsia" correctly. I only remember it by the mnemonic of it's fuck, but with an s.

I vote to just change the spelling to what almost everyone already thinks it is anyways. It'll still be just as weird. But "chs" is just nonsensical . The idea that it would sound like "sh" is baffling. I mean, I know this is English spelling which is not known for its regularity, but this is just too much.

> But "chs" is just nonsensical. The idea that it would sound like "sh" is baffling

In the word "french" C H is pronounced sh and nobody bats an eye, I don't think it's that outlandish that someone once read it as fuch-sia, incorrectly splitting it compared to the original.

In the language French, fuchsia is unequivocally read something more like few-shia, and I'd bet that even though it comes from German Fuchs-ia (fooks-ia) English has picked it up from the French side.

If you find such a loanword weird, don't you dare try reading Japanese.

https://aethermug.com/posts/the-beautiful-dissociation-of-th...

Re: Google confirms Android attacks; no fix for most Samsung users

#74
post #23

Earlier quoted context omitted.

It’s “Fuchsia” with a “chs” not a “sch”. Where do you get your information that it’s dead?

As Randall Munroe pointed out in https://blog.xkcd.com/2010/05/03/color-survey-results/ , almost nobody knows how to spell "fuchsia" correctly. I only remember it by the mnemonic of it's fuck, but with an s.

It’s helps if you know that the flower the fuchsia, was discovered by Dr Fuchs

Re: Google confirms Android attacks; no fix for most Samsung users

#76
post #5

No fix yet for Samsung. Being reliant on the hardware manufacturer (or network operator?) for OS updates is the crazy world we live in.

That's always the case, even on Windows, even on Linux for closed-source third party drivers. The only exception is macOS because Apple insists on writing the drivers themselves - that was, in addition to Soldergate, the reason why Apple dropped NVIDIA.

Are apples drivers open source?

Re: Google confirms Android attacks; no fix for most Samsung users

#77

This requires user action, right? User needs to install the APK by hand? In other words - if I don't install any crap on my phone I am safe?

Whilst the play store supposedly scans all apps for malicious behaviour, it's pretty easy to detect the test environment they use for testing and make malicious behaviour only trigger in situations Google doesn't test - eg. 5 days after installation, only if the device IP address changes at least once.

Re: Google confirms Android attacks; no fix for most Samsung users

#78
post #11

> This [update] was rushed out to all Pixel users. Pixel 8 here, still don't have the update. That's... not great.

You can manually download the full OTA from https://developers.google.com/android/ota#shiba and install it with adb.

Re: Google confirms Android attacks; no fix for most Samsung users

#79
post #47

Earlier quoted context omitted.

The big difference with PC hardware is that the OS will get most driver updates for the individual components directly from the OEM. A driver update for, say, a sound card will directly be available to every machine with that sound card installed. The PC vendor doesn't have to be involved in any way. It's the other way around with Android. Google does a new core release, and each individual manufacturer is responsibl…

Again, no sympathy as that’s the route they chose. Rely on Google for everything OS and make a phone whereas Apple made a phone and supplied an OS. Apple made a product. Google made a software revenue stream. Entirely different things and now the Android makers are crying foul that they too have to do product engineering support. Nah. This is what you get when you rely on out of house innovation. I hope they all clos…

Yeah, and I also hope that all the PC makers close up shop as well. They rely on Microsoft for everything OS. Listen, you can just enjoy your iPhone in peace. Let other people make things, even if you feel they don't meet your standards.

Re: Google confirms Android attacks; no fix for most Samsung users

#80
post #68

Never mind the December security patches, Samsung haven't even released the November patches yet, the ones for the critical severity RCE. Unless you have a "major flagship model" [1], because apparently only the richest users deserve to be secure. [1] https://security.samsungmobile.com/securityUpdate.smsb

Google Pixel 7 and Pixel 7 Pro are still stuck on the October patches.
Post reply on HN