4 ms·

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 wo

by zekica 4y ago

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 receiving vendor updates.

snvzz 4y ago
>LineageOS's first priority isn't security - it's freedom. But, importantly, they also care about security, and you'll get security updates faster and more often than with the vendor's stock ROM.
- aaaaaaaaata 4y ago
  Applying security patches to something that doesn't even do verified boot seems...hmmm
  - snvzz 4y ago
    Sure, because security is boolean. Either something is secure, or it is not. This is sarcasm, to be clear. (on my device, it is possible to just "fastboot oem lock", but that is aside the point)
lberrymage 4y ago
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..
- josephcsible 4y ago
  > They ship userdebug builds as production releases What specific security problem does this cause? > pretend to support devices past their vendor EOL (which is impossible since Lineage can't provide security updates for firmware etc.) This is good for security. Not everyone can afford to get a new phone as soon as the vendor drops support, and just because you can't fix everything doesn't mean that you shouldn't fix what you can. > ship the F-Droid Privileged Extension (which uses an incorrect approach to implementing unattended updates) What's incorrect about it? > don't support locking the bootloader to enable verified boot on many supported devices This isn't really their fault. On most devices, relocking the bootloader with anything non-stock has a high chance of permanently hard bricking.
  - aaaaaaaaata 4y ago
    > This is good for security No, it isn't. It's good for reducing e-waste, your security is on the line. Having the newly shaped and colored Android UI doesn't do anything to fix security issues..
    - josephcsible 4y ago
      Security issues can occur in both the device-agnostic Android OS code and in device-specific drivers. Some people are going to continue to use phones after the vendor drops support. Although those people won't get security updates to their device-specific drivers anymore no matter what they do, by using LineageOS instead of their stock ROM, they will get security updates to the device-agnostic Android OS code.
- kelnos 4y ago
  > pretend to support devices past their vendor EOL They don't "pretend" anything. They are very clear that, after a device no longer gets kernel/driver updates from the manufacturer, they can only provide OS/framework updates. > don't support locking the bootloader to enable verified boot on many supported devices Can you expand on this more? My understanding was that you could do this on Pixel phones, but that no other manufacturer supports adding user keys to the bootloader.

by zekica 4y ago

snvzz 4y ago

>LineageOS's first priority isn't security - it's freedom. But, importantly, they also care about security, and you'll get security updates faster and more often than with the vendor's stock ROM.

aaaaaaaaata 4y ago
Applying security patches to something that doesn't even do verified boot seems...hmmm
- snvzz 4y ago
  Sure, because security is boolean. Either something is secure, or it is not. This is sarcasm, to be clear. (on my device, it is possible to just "fastboot oem lock", but that is aside the point)

lberrymage 4y ago

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..

josephcsible 4y ago
> They ship userdebug builds as production releases What specific security problem does this cause? > pretend to support devices past their vendor EOL (which is impossible since Lineage can't provide security updates for firmware etc.) This is good for security. Not everyone can afford to get a new phone as soon as the vendor drops support, and just because you can't fix everything doesn't mean that you shouldn't fix what you can. > ship the F-Droid Privileged Extension (which uses an incorrect approach to implementing unattended updates) What's incorrect about it? > don't support locking the bootloader to enable verified boot on many supported devices This isn't really their fault. On most devices, relocking the bootloader with anything non-stock has a high chance of permanently hard bricking.
- aaaaaaaaata 4y ago
  > This is good for security No, it isn't. It's good for reducing e-waste, your security is on the line. Having the newly shaped and colored Android UI doesn't do anything to fix security issues..
  - josephcsible 4y ago
    Security issues can occur in both the device-agnostic Android OS code and in device-specific drivers. Some people are going to continue to use phones after the vendor drops support. Although those people won't get security updates to their device-specific drivers anymore no matter what they do, by using LineageOS instead of their stock ROM, they will get security updates to the device-agnostic Android OS code.
kelnos 4y ago
> pretend to support devices past their vendor EOL They don't "pretend" anything. They are very clear that, after a device no longer gets kernel/driver updates from the manufacturer, they can only provide OS/framework updates. > don't support locking the bootloader to enable verified boot on many supported devices Can you expand on this more? My understanding was that you could do this on Pixel phones, but that no other manufacturer supports adding user keys to the bootloader.