I’ve been using GrapheneOS for about 5 years.

Google pay won’t work, but everything else should. I’ve never experienced any of the issues the other commenter had, and I’ve installed Graphene on 4 devices (not dismissing you BTW, just saying I think your experience is quite uncommon).

I don’t think third-party launchers are a good idea (you’re giving full device permission to an unneeded app) but it should work.

Almost every app I wanted to use worked with Graphene before they introduced their sandboxed google services, and now everything I’ve tested works with Google push notifications. The only exception is Google pay, and there are upstream reasons for that. Keep in mind, on a very rare occasion the hardened memory allocator breaks compatibility (again this is very rare), but there is an app-specific setting toggle to turn this off so it’s kind of a non-issue.

Removed by mod

I don’t get these arguments. These tools aren’t weapons, and limiting legal access to pentesting tools will decrease corp’s and individuals’ ability to be proactive about security.

These devices can be manufactured relatively easily and making them illegal will essentially mean the only people doing security tests are criminals. Large tech companies, correctly, run bug bounties where independent security researchers can make income by reporting reproducible and exploitable bugs. The concept here is called offensive security and it’s extremely important for building better and more secure platforms. This situation will never be improved by limiting legal access to useful testing tools.

The responsibility should be on automakers and other companies that have massively insecure products, not on open source developers who are making products for security researchers.

Well that’s actually exactly what I’d expect

It seems like maybe the problem is that automakers were able to widely market vehicles that use wireless protocols that are relatively easy targets for attack. This was never properly secure.

Automakers should absolutely be held to higher standards (in general) than they are, and it’s not likely that banning specific devices is going to have any measurable outcome here. It’s pretty well known that people buy and sell malware, and people can just… make devices similar to a Flipper with cheaply and readily available hardware.

This is just dumb posturing to avoid holding automakers and tech companies accountable for yet another dumb, poorly thought out, design feature.

And obviously it doesn’t stop at cars. It seems pretty clear that snooping on any feature using RFID or NFC tech is only going to become more widespread. Novel idea: what about using… actual keys as the primary method of granting physical access? Lock picking is obviously possible but a properly laid out disc-detainer lock is pretty goddamn hard to bypass even with the proper tools, and that skill can’t just be acquired in the same way as with electronic methods of bypass.

deleted by creator

deleted by creator

I don’t totally disagree with the sentiment of what you’re saying, but it’s worth giving a cursory glance at psychedelic research before you totally write it off. One of the things that’s been documented is an increased ability to access compassion for yourself and others. Another suggests that psilocybin could help reform maladaptive neural pathways.

It’s not like “ingest a substance and your problems will go away,” it’s more like “this is one tool that could be helpful in some specific ways.” Psychedelics are legitimately different from other substances and I think it’s worth reading about with a hair less cynicism. It’s potentially very useful medicine.

https://www.hopkinsmedicine.org/psychiatry/research/psychedelics-research

So this was the exact thing that pushed me over to the FOSS side the last time they did it. Nice to see the tradition of annoying users to the point of them abandoning Microsoft is alive and well.

Just so we’re clear, this is the endgame of all of the propaganda against trans people. Many are culpable in this.

deleted by creator

Not tiktok music?

Can I ask why?

LineageOS supports a custom avb (android verified boot) key and a locked boot loader on a very limited number of devices, and surely not a galaxy s4. Which is to say if malware was installed on your device it could be persistent through boot/reboot cycles. There will be no verifying OS integrity. Also on a device that’s been unsupported for that many years, the firmware and software that you’ll have access to is dramatically less secure. And this just can’t improved by also not having a locked bootloader.

Lineage can only do so much to support devices after they’ve reached EOL, which while I agree sucks, it’s a problem that’s at the hardware level (Qualcomm and Samsung make it impossible to continue meaningful support).

I understand if you’re trying to keep a device alive that you already have, but buying a phone for this purpose is probably not a good call. Or do you live in an area with limited access to newer tech?

If you can at all, the cheapest and best move would be to buy something like a Pixel 6a or 7a (or even a 5a) and run GrapheneOS.

deleted by creator

deleted by creator

I set up 2FA via a hardware security key (a yubikey) for login, sudo etc. I then tried to switch security keys, removing the old pam files and adding a new one. But I didn’t tidy the pam files up before logging in, and there was effectively no way to log in, since editing the pam files required sudo access to edit in the first place. So basically the whole system required access to a pluggable authentication module that it no longer had any ability to recognize. It was honestly pretty funny. I did manage to recover my data by booting from a live system and decrypting my drive from there.

I’ve also accidentally removed my desktop environment twice while trying to update Python versions and then cleaning up old packages, but that’s kinda not that big deal and is just a facepalm moment.