This means that to run apps user has to have online connection to perform an integrity test. Whether it's only a test on launch or continues call home like Denuvo-like DRMs is not yet clear. This could also mean that modified headsets could fail to pass this test essentially closing down the device for modifications that could damage "platform integrity". Not all details are clear yet but this doesn't look good.

Currently it's optional and up to app developers to enable it.

you are viewing a single comment's thread
view the rest of the comments

[–] zeekzag@lemmy.world 36 points 1 year ago* (last edited 1 year ago) (2 children)

I haven't updated my Quest 2 since it got a 120hz patch. Been blocking their servers via Pi-Hole and Oculess because fuck Meta and their shitty requirements. Btw, PCVR players, if you want more freedom with your Quest 2 devices you might want to check out Oculess and OculusKiller.

https://github.com/basti564/Oculess - Removes account requirements from Quest 2 and disables telemetry/autoupdates.
https://github.com/DevOculus-Meta-Quest/OculusKiller - Nukes the Oculus Dash and goes straight into Steam VR.

Edit / typos

[–] Ajen@sh.itjust.works 1 points 1 year ago

I'm also glad I've kept my quest isolated from the internet once I enabled dev mode (for oculess). I've noticed it tries to connect to IP addresses owned by Meta (according to whois), without any dns queries involved. Your pihole won't be able to block that... I went a few steps farther and set up a dedicated wifi network that only allows local traffic. Then I set up a http proxy (squid) that only allows connections to certain websites. I mostly use the quest for PCVR though, so the proxy doesn't get much use.

And thanks for sharing oculuskiller! I've been looking for something like that for a while.

[–] Nelots@lemmy.world 1 points 1 year ago

Thanks. I'll be checking these out later.