They would still want kernel level anti-cheat in that case.
They would still want kernel level anti-cheat in that case.
Something which notifies you whenever a new comment or reply is made to a selected post/comment, so that you can keep track of any new conversation.
Something like this would be awesome as a core Lemmy feature IMO. It would essentially turn a post (or maybe any comment tree?) into a matrix style room. Lemmy is actually decent for long term discussion (e.g. helping someone with a problem), but not if there are more than two people involved.
I’d probably:
systemctl suspend
When the screen fails to wake, are you able to get it back by powering it off, or by unplugging it? Is it X or wayland?
I’ve been using orgzly for years and this is the first I’ve heard of revived. Looks promising.
Of course not, but you have to either trust your users to some extent or give them a system that’s locked down to the point of hindering them.
What is ‘unallowed software’? A shell script the user wrote? Something they downloaded and compiled?
Limiting that seems fundamentally at odds with FOSS.
If you stop shipping autotools generated artefacts in your tarballs, things will be a lot simpler.
Weirdly enough the malicious code does look eerily similar to the benign code, because both are unnecessarily obfuscated.
This is not a human written or readable file you’re talking about. It’s a generated script.
As the other user suggested, you probably just need to mount the root subvolume somewhere and run it on that.
Try using btdu
. I’m not sure how it works with compression, but it at least understands snapshots, as long as they are named in a sane way.
Yeah, that’s fair. If you want to test that you can still decompress something compressed with some random old version, you either need to keep the old algorithm around, or the data.
Many of the files have been created by hand with a hex editor, thus there is no better “source code” than the files themselves.
I don’t buy that. There would have been some rationale behind the contents that could be automated, like “compressed file with bytes 3-7 in the header zeroed”.
You also probably don’t need these test files to be available in the environment where the library itself is built. There are various ways you could avoid that.
I do agree about the autotools stuff though.
Minor differences in those files are perfectly normal as the contents of them are copied in from the shared autoconf-archive project, but every distro ships a different version of that, so what any given thing looks like will depend on the maintainer’s computer.
This seems avoidable. We shouldn’t be copying code around like that.
They are actually not that much bigger or different from mobile or game console GPUs, they just have a lot of cooling bolted to them. The cooling allows them to sacrifice efficiency, to be more power hungry and more powerful.
I wonder if anyone is doing large scale searches for source releases that differ in meaningful ways from their corresponding public repos.
It’s probably tough due to autotools and that sort of thing.
All of this would be avoided if Debian downloaded from GitHub’s distributions of the source code, albeit unsigned.
In that case they would have just put it in the repo, and I’m not convinced anyone would have caught it. They may have obfuscated it slightly more.
It’s totally reasonable to trust a tarball signed by the maintainer, but there probably needs to be more scrutiny when a package changes hands like this one did.
it had a way to know it was being emissions tested and so it adapted to that.
Not sure why you got downvoted. This is a good analogy. It does a lot of checks to try to disable itself in testing environments. For example, setting TERM will turn it off.
the wilds of Nova Scotia
Walking across the Windsor Street exchange is wild for sure.
For 2d stuff my limit for non-nostalgic enjoyment is probably around:
Stuff like that holds up pretty well IMO.
I agree with others about early 3d stuff being harder. Bad 3d physics especially drives me nuts. Carmageddon is the first game I remember with tolerable 3d physics, but I don’t think it was until around Halo that games were consistently getting it right.
GrapheneOS + Pixel phone is the only true option if you want any kind of ensure that even of the device is lost your data won’t be accessed.
I think that’s an exaggeration. You don’t need secure boot for your data to be encrypted. What secure boot prevents is someone modifying the device without your knowledge (e.g. to capture your keys).
There’s a couple of ways I could imagine debugging this.
One would be to disassemble MapEngine.MapsContainer.IsExists
and see why it would throw that exception. It’s quite strange because it should act like it’s running on windows.
The other would be to enable WINEDBG stuff or possibly use strace
to figure out what it did before throwing that exception.
Have you tried 32-bit wine?
I think most orgs would want to own the server and for messages to not be end-to-end encrypted. All connections to the server would still be encrypted.
That would be more in-line with slack or something.
If you’re referring to federation specifically then that’s going to get pretty complicated with security policies.