Only thing worse is not finding the bug that only happens in release mode
Lojcs
- 1 Post
- 4 Comments
Joined 3 months ago
Cake day: June 30th, 2025
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Lojcs@piefed.socialto Linux@lemmy.ml•Running a command only when resuming from the hibernation part of suspend-then-hibernate?English2·6 days agoI don’t follow your thought process. I didn’t say every running process could kill the lock screen or if it can kill the lock screen it can access everything else, I said any process that kills the lock screen has to be running. And as the attacker with physical access doesn’t know the password they can’t run anything to kill the lock screen. The only way for them to unlock it is if they already have malware on the device, in which case their physical access isn’t the cause of the problem.
Lojcs@piefed.socialto Linux@lemmy.ml•Running a command only when resuming from the hibernation part of suspend-then-hibernate?English21·6 days agoHow so? The lock screen is to prevent physical access while you’re away, and an attacker can’t kill it without having access in the first place. Any process that can kill it would already have access to your session.
Or something about packaging. Or I used a function that has a different implementation for debug mode out of its intended purpose. Or