@mjg59@nondeterministic.computer titelbild
@mjg59@nondeterministic.computer avatar

mjg59

@mjg59@nondeterministic.computer

Former biologist. Actual PhD in genetics. Security at https://aurora.tech, OS security teaching at https://www.ischool.berkeley.edu. Blog: https://mjg59.dreamwidth.org. He/him.

Dieses Profil is von einem föderierten Server und möglicherweise unvollständig. Auf der Original-Instanz anzeigen

mjg59 , an Random Englisch
@mjg59@nondeterministic.computer avatar

The "Recall can't record DRMed video content" thing is because DRMed video content is entirely invisible to the OS. The OS passes the encrypted content to your GPU and tells it where to draw it, and the GPU decrypts it and displays it there. It's not a policy decision on the Recall side, it's just how computers work.

mjg59 OP ,
@mjg59@nondeterministic.computer avatar

@bigolewannabe not trivially - the client would need to encrypt the window content and pass it through the DRM rendering API

mjg59 OP ,
@mjg59@nondeterministic.computer avatar

@RnDanger @bigolewannabe The least restrictive Widevine is implemented in Javascript and doesn't require GPU involvement so can be captured, and it's only fairly recently that Firefox got full Widevine support

mjg59 , an Random Englisch
@mjg59@nondeterministic.computer avatar

Why does my IdP have two entirely different flows for MFA auth depending on how you're hitting it

mjg59 OP ,
@mjg59@nondeterministic.computer avatar

User freedom is obviously the most important aspect of free software but the economic cost of staring at wire dumps to figure out a transaction flow instead of just being able to read the implementation should not be understated

  • Alle
  • Abonniert
  • Moderiert
  • Favoriten
  • •
  • random
  • haupteingang
  • Alle Magazine
    •