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

LineageOS 19

lineageos.org

Post reply on HN
Print view View original

251–260 of 260 posts

Re: LineageOS 19

#251

Post by timschumi »

lberrymage wrote: post #190
zekica wrote: post #106

Earlier quoted context omitted.

Lineage doesn't "break" android security model. It works around OEMs that don't support installing your own keys in the bootloader. Otherwise, security model works the same as any other android. LineageOS's first priority isn't security - it's freedom. Graphene and CalyxOS have security as the first priority - but have only a couple of phones on their support list and they deprecate old devices as soon as they stop r…

Yes it does. They ship userdebug builds as production releases, pretend to support devices past their vendor EOL (which is impossible since Lineage can't provide security updates for firmware etc.), ship the F-Droid Privileged Extension (which uses an incorrect approach to implementing unattended updates), don't support locking the bootloader to enable verified boot on many supported devices, etc..

> They ship userdebug builds as production releases

`userdebug` is used to have a few specific debugging capabilities that aren't available on a `user` ROM. Note that this is not the same as the standard `userdebug`, as most security measures that would otherwise get removed are manually reinstated.

> pretend to support devices past their vendor EOL (which is impossible since Lineage can't provide security updates for firmware etc.)

So... no security fixes at all are better in your opinion?

> ship the F-Droid Privileged Extension (which uses an incorrect approach to implementing unattended updates),

Where are you getting this from? Neither F-Droid nor its privileged extension is included in the system.

> don't support locking the bootloader to enable verified boot on many supported devices

There is nothing that inherently prevents you from relocking your bootloader on LineageOS. But technically, something may go wrong at any time, so it neither is officially supported nor endorsed, and the keys necessary for relocking the bootloader are not provided.

If someone wants to, they can always just build LineageOS themselves (with all system modifications built-in, because anything else would break the signature), sign it with their own keys, and reconfigure their bootloader to use that key.

Re: LineageOS 19

#252

Post by timschumi »

captn3m0 wrote: post #135

PSA: LineageOS 17.1 is no longer getting official builds, even though it has some of the recent security updates committed. So if can't upgrade immediately to 18.1, you can do a build yourselves to get the security patches. https://endoflife.date/lineageos

That table is wrong by the way. 17.1 went out of support this February, not last April. It also continues to receive security patches.

Re: LineageOS 19

#253

Post by timschumi »

EFruit wrote: post #182

Their IRC setup is profoundly disappointing. Joining their channel redirects unregistered users to a designated quarantine room that blocks all messages. Why on earth do I need to manage YET ANOTHER account just to ask a question, get a response, and leave?

Unfortunately, because we get enough trolls and spammers as-is, and I don't even want to imagine what happens if we lift that restriction as well. Sorry!

Re: LineageOS 19

#254

Post by timschumi »

captn3m0 wrote: post #192
lufte wrote: post #183

Earlier quoted context omitted.

Good tip. My device doesn't have any official build newer than 17.1 so I may need to start building my own images.

16.0 was still getting security patches merged till 19.0 release, so it’s a pretty decent change you can work this way for a while. I just wish the devs clarified timelines around merges (but not builds) on older branches.

> I just wish the devs clarified timelines around merges (but not builds) on older branches.

"When it's ready."

Stuff is merged in once it's well tested and ready. It also is only updated as long as someone still cares to update it.

Re: LineageOS 19

#255

Post by PlqnK »

hedora wrote: post #97
IceWreck wrote: post #69

Earlier quoted context omitted.

Is that build based on Android 12 ? If so I might be wrong about no custom ROMS adding that feature back in. Maybe grapheneOS and some other ROMS made their own patches to fix it.

Settings says "Android 12" and the build date is this month, so presumably, yes. Their firewall is pretty simple though (per app enable disable). Does lineage support more complicated policies?

On my phone running LineageOS 18.1 (Android 11) I have the following on/off options for every app: Allow network access, Wi-Fi data, Mobile data, Background data, VPN data, Unrestricted data usage (even when data saver is on)

Re: LineageOS 19

#256

Post by timschumi »

jackallis wrote: post #30

would a day come when update will auto-install instead of needing to do it "manually"?

The reason why auto-install doesn't work for major version upgrades is because Google Apps are version-specific, and LineageOS isn't allowed to ship Google Apps without paying for certification by Google (and, in fact, disregarding this _will_ result in cease-and-desist letters).

This means that ~95% of users would break their installation by pressing the "auto-update" button because they didn't update their GApps accordingly.

Also, nowadays there is the problem of requiring a certain version of the built-in firmware as well, and in case there are any incompatibilities, a major version upgrade is the perfect time to require updating that as well.

Re: LineageOS 19

#257

Post by ssvss »

ysleepy wrote: post #154
karteum wrote: post #26

Earlier quoted context omitted.

I have a Oneplus 5T (dumpling) and get much less frequent updates (which puzzles me : I though they would have an automated build system i.e. that all supported devices would have exactly the same updates at the same time...)

I have yet to jump to lineage with the 5T, does it run well? I've had so many phones have glitches like random reboots etc. before, I'm hesitant.

I have been running lineage for more than a year in my OP5, I don't face any issues with it. I don't use microg. I have also rooted it with magisk, so that banking apps will work.

Re: LineageOS 19

#258

Post by captn3m0 »

timschumi wrote: post #252
captn3m0 wrote: post #135

PSA: LineageOS 17.1 is no longer getting official builds, even though it has some of the recent security updates committed. So if can't upgrade immediately to 18.1, you can do a build yourselves to get the security patches. https://endoflife.date/lineageos

That table is wrong by the way. 17.1 went out of support this February, not last April. It also continues to receive security patches.

You’re correct, will get this fixed.

Re: LineageOS 19

#259

Post by scns »

onli wrote: post #117
scns wrote: post #20

Earlier quoted context omitted.

https://www.sustaphones.com/ Gives you filters for battery replacement difficulty and headphone jacks. edit: add explanation

Thanks for linking to the site. I just updated it to include the new version. It's called 19.1 in their wiki and I'll just copy that version number for now.

Thanks for building it.

Re: LineageOS 19

#260

Post by MaxBarraclough »

soperj wrote: post #109
nfriedly wrote: post #24

I'm still pissed at Google for locking the bootloader on my Pixel 2. I bought the phone unlocked directly from Google, specifically so that I could install a custom ROM once Google stopped supporting it. But I sent the phone in to repair a broken USB port, and apparently it was Google's policy to send back a phone with a locked bootloader any time you get a repair. I can't even get a response from Google's support ab…

This sounds like it's class-action worthy.

For comparison there was a successful class action against Sony for removing Linux support from the PS3 in an online update.

https://en.wikipedia.org/wiki/OtherOS

Post reply on HN