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

LineageOS 23

lineageos.org

Post reply on HN
Print view View original

171–180 of 188 posts

Re: LineageOS 23

#171

Post by okanat »

andrewflnr wrote: post #132
okanat wrote: post #130

Earlier quoted context omitted.

Where are you from? I live in Germany. I use ING and DKB as my banks. Both of the banks require a Play Integrity-checked app as their default 2FA.In the past I used Sparkasse and Commerzbank. They too required a PI-approved app. As an alternative you can order a code generator but for DKB that requires a paid debit-card. ING disables the phone app if you use a code generator. You cannot have multiple 2FA.

US, Virginia. Funny, I tend to assume Europe has this stuff better figured out.

EU Nations who are familiar with computers like Sweden and Estonia did.

Germany likes to think that they belong to cabinets and powered with internal combustion engines. Internet was a new land in 2013. So every user-friendly feature has to be shoved into Germany's throat by EU (especially banks and insurance). The usual reaction from German companies is to wait until the last moment and then hire a law / consultancy firm to implement required changes as badly as possible.

Re: LineageOS 23

#172

Post by baranul »

exabrial wrote: post #121
laktak wrote: post #58

I'd love to see a hybrid phone with an embedded stock android for banking, pay and government apps and a regular LinageOS or Linux OS that runs on a separate partition/hw/vm. Like "gluing" two phones together - just better ;) It would be great to run an open OS but having to carry a separate phone for banking/paying is not really a viable option.

There's 0 reason why bank/pay/gov apps can't be ran on a regular OS. The goal is to force users into the Google world at the excuse of "security"

This is on point and it's sickening what Google is allowed to get away with. Even with the recent crackdowns on Google by various governments, they are steadily locking down Android, so even if you paid for your phone, whatever apps that you want to put on it will need their seal of approval.

The excuse of "security" or "it's for the children" is complete BS, because it's about "them" having unwanted and total control.

Re: LineageOS 23

#173

Post by wartijn_ »

unnouinceput wrote: post #106

I just want something, anything at all, for my Redmi 14C. No luck so far.

It has a Mediatek soc, custom roms for these chips are scarce. If you look at the supported devices on the Lineage wiki, you’ll see only 2 out of 550 devices have a Mediatek soc[0], most of them are Qualcomm.

And iirc from the xda forums, even for Xiaomi phones with a Qualcomm soc it isn’t certain anyone will try to make a custom rom. Xiaomi just releases too many devices to have support for all of them.

[0] https://wiki.lineageos.org/devices/

Re: LineageOS 23

#174

Post by hollow-moe »

strcat wrote: post #138
riedel wrote: post #86

Earlier quoted context omitted.

The bad thing in general is the dependence on Google policy for all AOSP distros. Joining those programs might long term worsen the situation. IMHO, it could be worth the fight if GrapheneOS could win their (rather legal/lobbying) battle to obtain play integrity certification by following security closely (which is a joke IMHO because EOL phones with not updates for years also get integrity). Google releasing easily…

We have the sources for the patches which is how they get applied the source tree. We have both the regular releases and security preview releases so it's easy to see what was changed since it's a small amount of code: currently 59 security patches for Android 16, similar to the size of typical Android security patches, although 1 was already public elsewhere so we applied to the regular release. > does not even incl…

> Trusting third parties with this is a privacy and security risk. I sure trust more LineageOS webview and the guy running BeaconDB than google or apple fwiw. I understand Graphene goal isn't freedom but "security", just a hardwareless OEM eventually complying with whatever Google will want.

Re: LineageOS 23

#175

Post by saaspirant »

microflash wrote: post #118
saaspirant wrote: post #90

Somewhat related: I could never get adb in my M1 Air (Tahoe and Sonoma too) to detect any android devices. I have an OnePlus Nord CE 2 Lite 5G. Same cable and everything works fine on Ubuntu and Windows machines. The phone is not getting detected in the "System Information" either. Tried MTP, PTP, USB Debugging, OTG everything. Anyone faced this issue?

Your Chrome-based browser might be blocking the port that adb uses.

adb is able to start successfully and listens on its port

Re: LineageOS 23

#176

Post by saaspirant »

d3Xt3r wrote: post #135
saaspirant wrote: post #90

Somewhat related: I could never get adb in my M1 Air (Tahoe and Sonoma too) to detect any android devices. I have an OnePlus Nord CE 2 Lite 5G. Same cable and everything works fine on Ubuntu and Windows machines. The phone is not getting detected in the "System Information" either. Tried MTP, PTP, USB Debugging, OTG everything. Anyone faced this issue?

I have an M1 Air too and adb works fine for me. I used homebrew to install it ("brew install android-platform-tools").

I used the same command

ADB starts correctly but can't detect the phone

Re: LineageOS 23

#177

Post by raspyberr »

fsflover wrote: post #162
strcat wrote: post #146

Earlier quoted context omitted.

Open schematics for a PCB don't make it any harder to hide a backdoor. You're talking about devices which still have an entirely closed source SoC with all of the real complexity. The products you're repeatedly marketing here use a bunch of low end components with very poor security including lacking ongoing patches for vulnerabilities and basic standard security protections. They're falsely marketed as open but are…

> They're falsely marketed as open but are actually closed source hardware This is just a strawman: Nobody claimed they were open hardware. > Open schematics for a PCB don't make it any harder to hide a backdoor. This is like saying that FLOSS doesn't make it harder to hide a backdoor. Of course it does.

The backdoor would be in the firmware and open schematics for a PCB don't say anything about open firmware right....

Re: LineageOS 23

#178

Post by timschumi »

WhyNotHugo wrote: post #115
timschumi wrote: post #79

Earlier quoted context omitted.

There is a guide on how to set up LineageOS for libvirt (i.e. QEMU) [1], but there exist no prebuilt images at this point in time. [1] https://wiki.lineageos.org/libvirt-qemu

The requirements are monstrous: 300GB storage, 32GB RAM. My everyday working laptop has a 240GB SSD. I've build the kernel, Firefox, and the heaviest packages which I use from sources with a fraction of those resources. I can't even fathom what the build system is doing in order to require this amount of storage.

> I can't even fathom what the build system is doing in order to require this amount of storage.

A large number of 17 year old repositories, prebuilt toolchains, and the fact that you otherwise have every little bit of source code, intermediary results, and output to create a full operating system all in the same place.

As for the memory, the very first step (that basically already is the benchmark for the most memory usage) is loading the entire build tree and generating build steps. Yes, that takes 32GB of RAM, if not 64GB nowadays.

Re: LineageOS 23

#179

Post by kzhe »

strcat wrote: post #155
Borealid wrote: post #93

Earlier quoted context omitted.

Let's define "more secure" as "preventing a particular behavior that is against the device owner's conscious or unconscious wishes". It would be "more secure" to have a per-application firewall that blocks particular apps from outbound traffic over certain networks or to certain destinations. This prevents a malicious app from consuming roaming data. LineageOS can have that, at the owner's preference. Graphene explic…

> LineageOS can have that, at the owner's preference. Graphene explicitly forbids it. That's not true. You can use apps like RethinkDNS providing local monitoring and filtering of connections while still supporting using a VPN on either LineageOS or GrapheneOS. GrapheneOS fixes 5 different kinds of outbound VPN leaks which are still present on LineageOS, which is quite relevant to this. There are no known outbound VP…

I'm using Graphene but honestly the biggest thing is that Lineage devs wouldn't care if you root, while Graphene devs obviously do because it screws the whole point of Graphene

Re: LineageOS 23

#180

Post by fsflover »

raspyberr wrote: post #177
fsflover wrote: post #162

Earlier quoted context omitted.

> They're falsely marketed as open but are actually closed source hardware This is just a strawman: Nobody claimed they were open hardware. > Open schematics for a PCB don't make it any harder to hide a backdoor. This is like saying that FLOSS doesn't make it harder to hide a backdoor. Of course it does.

The backdoor would be in the firmware and open schematics for a PCB don't say anything about open firmware right....

You're not wrong. I only claim that there are fewer places to hide a backdoor when the schematics is open (just like with FLOSS software).
Post reply on HN