7 ms·
Update and Build Prep
- bostand 10y agoLets hope Steve remembers to do the right thing (tm) this time. Edit: in particular, next time someone in his organization does/says something incredibly stupid I want Steve to stop it right away instead of waiting 2 years...
- mk-lovers 10y agoLet's hope so
- xkxx 10y ago> next time someone in his organization does/says something incredibly stupid I want Steve to stop it right away instead of waiting 2 years... Can you fill me in, please?
- tekacs 10y agoFor anyone who isn't already aware, this is a continuation of the work on CyanogenMod, after the company behind the latter closed down. More here: http://www.gsmarena.com/lineage_os_is_now_officially_picking_up_where_cyanogenmod_left_off-blog-22903.php http://www.gsmarena.com/lineage_os_is_now_officially_picking...
- tastythrowaway2 10y agothanks
- tombh 10y agoThank you
- deleted 10y ago[deleted]
- orblivion 10y agoIf I recall, Cyanogenmod builds had sha1sums. Lineage should upgrade to sha256. They could also pgp sign them like Mozilla. And also, they shouldn't offer https download links that redirect to http mirrors. It would be nice if websites didn't do this while browser developers still haven't come terms with this issue.
- keeperofdakeys 10y agoThere are no known attacks which make SHA1 insecure in this context. Also according to this announcement, they will be signing the builds, which is vastly superior to any unverified checksum.
- heinrich5991 10y agoThe signature is only as good as the hash it's using. SHA-1 is considered insecure. From Wikipedia: SHA-1 is no longer considered secure against well-funded opponents. In 2005, cryptanalysts found attacks on SHA-1 suggesting that the algorithm might not be secure enough for ongoing use,[3] and since 2010 many organizations have recommended its replacement by SHA-2 or SHA-3.[4][5][6] Microsoft,[7] Google[8] and Mozilla[9][10][11] have all announced that their respective browsers will stop accepting SHA-1 SSL certificates by 2017.
- qznc 10y ago"All official builds from LineageOS are signed with our private keys. You can verify a build has been signed with our keys by running ..." http://wiki.lineageos.org/verifying-builds.html http://wiki.lineageos.org/verifying-builds.html
- Aaron1011 10y ago"We will NOT be shipping root baked into the ROM." Does anyone know why this is the case? Is there some kind of issue with shipping it rooted + a root manger (SuperSU, Superuser, etc) as CyanogenMod did?
- XorNot 10y agoI too would like an answer to this. If I'm flashing my phone already...
- mastax 10y agoHaving root makes many apps not work (e.g. Android pay) so if you're not going to use it you're better off not having it.
- ikeboy 10y agoAndroid pay requires stock, any custom ROM will fail even without root.
- Markoff 10y agowhy not built in superuser anymore?