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

LineageOS 23.2

lineageos.org

Post reply on HN
Print view View original

31–40 of 64 posts

Re: LineageOS 23.2

#31

Post by zozbot234 »

JamesTRexx wrote: post #28

I enjoyed LineageOS for years on my Samsung S4 until it finally broke from a fall. It's a shame there was no image to install on my new Xcover 7, but not unexpected as it was a newly released phone. But I doubt there will be an alternative/stripped Android available for this model as I haven't seen anything supporting a Xcover version anywhere. Best I can hope for is eventually a support for rooting and de-installing…

Note that Samsung devices with OneUI 8 remove bootloader unlocking altogether, making it impossible to 'root' the device or load LineageOS on it. The Xcover 7 is a newly released Samsung device that will most likely receive that update (it's live already in some regions), and even if you tried to stay on OneUI 7 the community is just unlikely to support it (as with other Samsung devices that are in the same boat today) since most devices in the wild will not be unlockable.

Re: LineageOS 23.2

#32

Post by zozbot234 »

fsflover wrote: post #30
throwaway270925 wrote: post #18

Earlier quoted context omitted.

Are there any alternatives? For phones other than pixels? (Genuine question)

postmarketOS, Mobian.

Unfortunately these OS's don't even support the "phone" use for most hardware. They're probably fine if you just want to turn your old phone into a palmtop-class device, but not for much else.

Re: LineageOS 23.2

#33

Post by fsflover »

zozbot234 wrote: post #32
fsflover wrote: post #30

Earlier quoted context omitted.

postmarketOS, Mobian.

Unfortunately these OS's don't even support the "phone" use for most hardware. They're probably fine if you just want to turn your old phone into a palmtop-class device, but not for much else.

It depends on the hardware a lot. Quite a few people use both of them for daily driving.

Re: LineageOS 23.2

#34

Post by EgregiousCube »

snvzz wrote: post #11
rixrax wrote: post #3

Earlier quoted context omitted.

Why is this?

Because it is more profitable for smartphone makers if you need to buy a new one. Unless there's legislation to force them to allow enrolling new keys or otherwise disabling secure boot, the abuse will continue.

This is true; there is additionally a valid argument that there is security benefit to locking down the bootloader. I don’t like locked down bootloaders, but I get the argument.

Re: LineageOS 23.2

#35

Post by bluebarbet »

dijit wrote: post #24
Aachen wrote: post #22

Earlier quoted context omitted.

> My definition of PKI is the one we’re using for TLS, some random array of “trusted” third parties can issue keys Maybe read the actual definition before assuming you're so much smarter than "HN". One doesn't need third parties to have pki, it's a concept, you can roll out your own

“read the actual definition”;stellar contribution there, mate. I checked and sure enough its exactly in line with my comments. I’ve been discussing the practical implementation of PKI as it exists in the real world, specifically in the context of bootloader verification and TLS certificate validation. You know, the actual systems people use every day. But please, do enlighten me with whatever Wikipedia definition you…

The snarky tone and sarcasm are not helping your case in this thread.

Re: LineageOS 23.2

#36

Post by Paianni »

JamesTRexx wrote: post #28

I enjoyed LineageOS for years on my Samsung S4 until it finally broke from a fall. It's a shame there was no image to install on my new Xcover 7, but not unexpected as it was a newly released phone. But I doubt there will be an alternative/stripped Android available for this model as I haven't seen anything supporting a Xcover version anywhere. Best I can hope for is eventually a support for rooting and de-installing…

The S4 Mini ended up being a legendary long-termer as its drivers were built for the 3.10 kernel, which was still being patched by Red Hat two years ago.

Re: LineageOS 23.2

#37

Post by eklavya »

dijit wrote: post #26
junon wrote: post #25

Earlier quoted context omitted.

You misunderstood, it appears.

Or its collective ignorance, can’t be sure. Public key infrastructure without CAs isn’t a thing as far as I can see, I’m willing to be proven wrong, but I thought the I in PK I was all about the CA system. We have PGP, but that's not PKI, thats peer-based public key cryptography.

I don't know what's going on in this thread. Of course PKI needs some root of trust. That root HAS to be predefined. What do people think all the browsers are doing?

Lineage is signed, sure. It needs to be blessed with that root for it to work on that device.

Re: LineageOS 23.2

#38

Post by JCattheATM »

I'm still running this on my OnePlus 6T, purchased refurbished from ebay for $60. Runs fine. Using it degoogled, I'm not sure if e/OS or similar alternatives have any advantage.

It can run PostmarketOS as well which I might play with at some point.

The 6t allows bootloader locking if I sign it with my own keys, but I haven't tried that yet.

A shame it is less supported on newer devices, but these older devices meet my needs perfectly anyway, so I'm not too worried. People buying a new $800 phone every year are just wasting their disposable income IMO.

Re: LineageOS 23.2

#39

Post by dijit »

bluebarbet wrote: post #35
dijit wrote: post #24

Earlier quoted context omitted.

“read the actual definition”;stellar contribution there, mate. I checked and sure enough its exactly in line with my comments. I’ve been discussing the practical implementation of PKI as it exists in the real world, specifically in the context of bootloader verification and TLS certificate validation. You know, the actual systems people use every day. But please, do enlighten me with whatever Wikipedia definition you…

The snarky tone and sarcasm are not helping your case in this thread.

The tone matched the engagement I received. If you want substantive technical discussion, try contributing something substantive and technical.

I've explained the same point three different ways now. Not one person has actually demonstrated where the technical argument is wrong, just deflected to TOFU comparisons, philosophical ownership debates, and now tone policing.

If Aachen has an actual technical refutation, I'm all ears. But "read the definition" isn't one, and neither is complaining about snark whilst continuing to avoid the substance.

Re: LineageOS 23.2

#40

Post by junon »

eklavya wrote: post #37
dijit wrote: post #26

Earlier quoted context omitted.

Or its collective ignorance, can’t be sure. Public key infrastructure without CAs isn’t a thing as far as I can see, I’m willing to be proven wrong, but I thought the I in PK I was all about the CA system. We have PGP, but that's not PKI, thats peer-based public key cryptography.

I don't know what's going on in this thread. Of course PKI needs some root of trust. That root HAS to be predefined. What do people think all the browsers are doing? Lineage is signed, sure. It needs to be blessed with that root for it to work on that device.

They're assuming PKI is built on a fixed set of root CAs. That's not the case, as others have pointed out - only for major browsers. Subtle nuance, but their shitty, arrogant tone made me not want to elaborate.
Post reply on HN