Re:Dutch 'idealist' bank ASN blocks non-Google Android, incl...
by teekert on Friday November 06, 2026 @08:14AM
(#50391935)
"Hardly true, if they permitted Lineage and so on."
I agree, but that is also totally unrealistic for normal people.
Re:Dutch 'idealist' bank ASN blocks non-Google Android, incl...
by hedora on Friday November 06, 2026 @10:05AM
(#50393205)
This bank claims "security is very important to them". In another, the poster reports getting training spam every week.
Installing Lineage isn't that hard. If they're going to badly inconvenience some customers / force hardware purchases, why not start with the ones who are most likely to get their accounts drained?
Re:Dutch 'idealist' bank ASN blocks non-Google Android, incl...
by dns_snek on Friday November 06, 2026 @08:38AM
(#50392148)
[delayed]
Re:Dutch 'idealist' bank ASN blocks non-Google Android, incl...
by yjftsjthsd-h on Friday November 06, 2026 @12:04PM
(#50395053)
I'm sure they're completely unbiased source. But seriously, the real question is whether lineage is more or less secure than the stock ROMs that are currently allowed.
Re:Dutch 'idealist' bank ASN blocks non-Google Android, incl...
by bilkow on Friday November 06, 2026 @06:46PM
(#50400073)
I have read the first comment in your link and just replied to it. Pretty sure it's incorrect as I've seen a LineageOS device in September with a September security update level, and you can see in Gerrit[0] that the version string bumps are merged every month, with the commit messages including which CVEs were fixed. New images are built weekly[1].
What I think happened is that GrapheneOS assumed the blog post meant that those updates happened at the time of the post, while the post is actually announcing things that were done in the last few months.
[0] https://review.lineageos.org/q/subject:%22release:+Bump+Secu...
Hardly true, if they permitted Lineage and so on.
> Just like any enterprise software, it targets a set of common devices so they can provide support and QA on it.
Not really, there are a myriad of devices and they're not testing on all of them. A "pound sand if you're on an unsupported device and it isn't working" policy would be perfectly acceptable, as long as the issue isn't directly caused by the developer purposefully breaking the application for a subset of users that fail Play Protect check or whatever.