Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google confirms Android attacks; no fix for most Samsung users

forbes.com

Post reply on HN
Print view View original

41–50 of 177 posts

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

#41

Post by TheDong »

kwanbix wrote: post #29
charcircuit wrote: post #17

>But in reality, Samsung (and the other Android OEMs) cannot compete with Google and its unique control over hardware and software. Yes, they can. We are talking about applying provided security patches to source code, and then releasing a new version of their OS. For patches that have existed for months. The time from patch to release should be on the order l of days from receiving the patches to having a validated…

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

Weird how LineageOS supports ~300 devices while still managing to release patches.

I bet this CVE's patched quicker on a samsung device running LineageOS than the stock OS.

The real difference is that Google has a more competent software development process and release process than other android OEMs, regardless of how many different devices they have.

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

#42

Post by [deleted] »

reactordev wrote: post #38
shiandow wrote: post #32

Earlier quoted context omitted.

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?

>How many different models of PCs get released? If you want to go that route, each manufacturer is responsible for their own drivers for windows, linux, and possibly Mac (though if it’s novel enough, they will do it). Then think about the components that make up a PC. Motherboard, CPU, Memory Control, IO, OS, Audio, Video. Each of those needs to release patches. So its orders of magnitude more than any Android OS. It…

[deleted]

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

#43

Post by crote »

kwanbix wrote: post #29
charcircuit wrote: post #17

>But in reality, Samsung (and the other Android OEMs) cannot compete with Google and its unique control over hardware and software. Yes, they can. We are talking about applying provided security patches to source code, and then releasing a new version of their OS. For patches that have existed for months. The time from patch to release should be on the order l of days from receiving the patches to having a validated…

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

If you can't support 50 different models, then perhaps you shouldn't be releasing 50 different models.

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

#44

Post by stackskipton »

TheDong wrote: post #41
kwanbix wrote: 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.

Weird how LineageOS supports ~300 devices while still managing to release patches. I bet this CVE's patched quicker on a samsung device running LineageOS than the stock OS. The real difference is that Google has a more competent software development process and release process than other android OEMs, regardless of how many different devices they have.

LineageOS doesn't customize the hell out of their OSes per device.

That's core of the issue. Samsung takes Android, customizes per device and then tosses them into the world. So now they don't have 1 OS to update, they have 100s of OSes to update.

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

#45

Post by int0x29 »

kelnos wrote: post #11

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

I think your carrier hasn't approved it yet. T-mobile seems to lag on these things. I also can't seem to find a system update. A Google Play system update does seem to exist

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

#46

Post by like_any_other »

kwanbix wrote: post #29
charcircuit wrote: post #17

>But in reality, Samsung (and the other Android OEMs) cannot compete with Google and its unique control over hardware and software. Yes, they can. We are talking about applying provided security patches to source code, and then releasing a new version of their OS. For patches that have existed for months. The time from patch to release should be on the order l of days from receiving the patches to having a validated…

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

And 5000+ laptop models per year, yet linux runs on (pretty much) all of them. This is an entirely self-inflicted problem. They don't deserve an ounce of mercy.

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

#47

Post by crote »

reactordev wrote: post #38
shiandow wrote: post #32

Earlier quoted context omitted.

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?

>How many different models of PCs get released? If you want to go that route, each manufacturer is responsible for their own drivers for windows, linux, and possibly Mac (though if it’s novel enough, they will do it). Then think about the components that make up a PC. Motherboard, CPU, Memory Control, IO, OS, Audio, Video. Each of those needs to release patches. So its orders of magnitude more than any Android OS. It…

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 responsible for modifying it for their devices. If you don't bother to upstream your drivers to mainline Linux and use a skin which heavily modifies core Android, backporting those fixes can quickly become a nightmare.

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

#48

Post by School-Cotton »

pwdisswordfishy wrote: post #39
crazygringo wrote: post #31

Earlier quoted context omitted.

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.

It comes from the surname of a German botanist. Which just happens to mean "fox". Never had problems with it. It would probably help if you pronounced it right, with a /ks/.

The beginning of the English word "fuchsia" is not pronounced like the German word Fuchs, so indeed the spelling does not match the pronunciation. This is independent of the fact that it comes from that word. Plenty of things in English (and, in fact, loanwords in every language) sound different from the words they're derived from; that doesn't mean trying to imitate the source language is the "right" pronunciation. If you pronounce fuchsia like "fuksia" nobody will understand you.
Post reply on HN