Quoting: Guest

Quoting: EagleDelta

Quoting: Guestwhat I don't get about this whole article... is how does the heck Fortnite for Android works? and I think there's enough android "distros" out there, that have plenty of different kernels. Did google let them run a proprietary module on their kernels?
I'm sorry if my question is too stupid I simply ignore this.

They will detect if you are running with root, or running with an unlocked bootloader, or try to see if you're running a custom ROM and block those things.

that probably can be easily bypassed with MagisK. There's actually nothing preventing me from patching my own kernel and building a custom rom image, with a patched kernel to run on my android device (and running fortnite with full customized kernel). I don't see that being any different from Linux distros, It might be a little more complicated to setup and compile, than lets say installing xanmod or liquorix kernel, but it's totally doable.

Anyway... I think that clearly, they are not relying on a kernel module on android, so all this about GPL incompatibilities with EAC and the kernel is all nonsense.

Besides let's not make it about Linux only tho... I think that probably Apple wouldn't allow a kernel module for anticheat on their kernel, for the obvious security reasons.

In my opinion...this is not about Linux only, Google banned fortnite from their play store, Apple did likewise. So maybe the problem is Epic here. Maybe their app wants unlimited trust, their app needs more permissions and priviliges, than anything out there, so it's getting banned, for security reasons.
And Sweeney is so blinded with greed, that cannot see the Elephant in the room here.

Android is moving towards hardware-based attestation, which means that Magisk will come to an end eventually, regardless.

The reason why this practice of kernel-based anti-cheat is ok on desktop but not on mobile is because the OS vendors (Google and Apple, respectively) do not allow it.
The desktop security model however, is so broken that nobody even cares anymore.

View this comment - View article - View full comments

Quoting: RobertKrigCouldn't they just have a whitelist of kernels that they allow Fortnite+EAC to run against?
At least for steamdeck they could check the hash of valve's provided kernel to ensure it's not a custom compiled one. Sure, it would mean they would need to keep an updated list of allowed kernels, but I don't think that's such a gargantuan task.

I think the "We don't want to pay Valve's fees" is probably the real reason why fortnite won't be coming to steamdeck.

And who is ultimately managing the memory that would perform that checksum calculation? The kernel.

And you could very well build your own kernel and have it lie to a module.
Asking another component if it is legit is simply naive.

View this comment - View article - View full comments

Quoting: marcusThanks for the write-up! Interesting read. I still think that if Valve provided a measured boot facility where a user-program could verify that it is running on an un-modified kernel then EAC could assume that there are also no kernel-level cheats present and that all kernel-level introspection APIs present correct and unmodified results.

So I'm not sure that a kernel level component is actually required. Mind you that measured boot does not imply that the platform is locked down. It only implies that user programs can check that the system was booted in a known good configuration. You are still free to modify it, however a cheat detection program such as EAC could then refuse to run.

1. Measured boot uses the hardware-capabilities to ensure that the software you run is from a certain source (enrolled platform key) and hasn't been tampered with.
2. A software running on such a system cannot verify that the hardware did what it claims to have done. (Hardware always beats software)
3. There are ways to attest the integrity of the system at runtime, via a TPM or the upcoming Pluton chip in Zen3D CPUs.

The problem is that even a TPM or Pluton would be unsuited to combat cheaters.

A cheater could simply modify one system and keep another "legit" one. When something asks for a verification, you send that request to the legit machine, have it attest that everything is ok and send that back instead.

This is also why TPMs aren't used to enforce DRM, btw.

View this comment - View article - View full comments

Dead By Daylight (won't work due to anti-cheat)

Yet*

View this comment - View article - View full comments

Are there any signs of their Nvidia Settings app being ported to Wayland?

View this comment - View article - View full comments

Nice, TkG already told me before that Capcom is using the new RE engine, instead of the one they used for World/Iceborne (though that one received a DX12 backend later, which also significantly improved performance with Proton).

View this comment - View article - View full comments

They also seem to be aiming for a release on Flathub.
https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/issues/743 [External Link]

View this comment - View article - View full comments

Quoting: Lofty

Quoting: TheRiddickI look forward to the day I can switch to Wayland. But we still need some better Display Management stuff like Brightness/Gamma/Contrast/ICC controls along with HDR at some point.

Nvidia binary driver user here..
I had assumed good real world multi-monitor would work ok by now on x-server and i was wrong. Here with my dual screen mixed refresh/resolution combo. Windows will draw at the lowest refresh available instead of refreshing separately for each screen (although the mouse cursor refreshes at the screens native refresh) not only that but the window movement is clunky even when setting both screens to 60hz.. because reasons. The only solution is to disable v-sync entirely (not good).

This is because on X11, all monitors are considered one screen.

As such, refresh rate and DPI scaling will be applied uniformly to all monitors.

View this comment - View article - View full comments

Quoting: rustybroomhandleI suspect the 10GB is not just the OS but also some pre-allocated space for OS images.

I think so too, they are probably using an A/B-model, which means that you have two installations of the OS at every time.

The actual OS size is probably somewhere around 3-4GB (Pop!_OS' Nvidia iso is 4.6GB) and reserving 5GB per image to account for future updates.

Or they use btrfs-subvolumes and allocate storage dynamically.

View this comment - View article - View full comments

Quoting: zimplex1I'm sorry, but this is just dumb. They turned the vanilla Gnome app grid into... an app grid. They did this with the search and overview features as well, breaking them into separate components. Why waste time and effort on this? They aren't even adding functionality, and they definitely aren't making it LOOK better, it's just inferior versions of what vanilla Gnome already did, and since they are split apart, it's not as cohesive of an experience.

Same here, I don't see what it brings to the table really.

1. You can already group apps by default
2. You can already search for installed and installable apps by pressing Super and then starting to type.

The recovery partition is better than nothing, but I consider it inferior to btrfs snapshots and OSTree images.

But what really grinds my gear is that they have the guts to claim that their distro is "fundamentally secure", while
1. still using X11 by default,
2. still using PulseAudio by default,
3. not providing signed kernels and drivers to utilize Secure Boot (maybe include instructions how to enroll MOK or possibly automate it during installation?),
4. not using a mandatory access control system like SELinux or AppArmor,
5. preferring non-sandboxed applications (Flatpaks and Snaps are still far from perfect in that regard, but they are moving in the right direction),
5.1. that are not isolated from the base system which is the root cause of the whole "Do as I say!"-debacle.

EDIT: r/pop_os is being flooded by people that ran into dependency hell after upgrading to 21.10 already.
https://www.reddit.com/r/linuxmemes/comments/rftl4h/vietnam_flashbacks/ [External Link]

View this comment - View article - View full comments