• 6 Posts
  • 32 Comments
Joined 2 years ago
cake
Cake day: February 1st, 2023

help-circle

  • that makes no sense - you need the key

    But if it’s stored in a keyring or similar (like on windows) and the client reads from it you don’t need the file with the plain text key. Like you don’t store the git credentials in a file, but with libsecret.

    I would prefer something that never ask for the password.

    Things like the gnome-keyring or kwallet keep all the passwords in an encrypted file, they get decrypted and kept in ram using your login password when you log into gnome/KDE session and programs can ask for passwords using some API. Once you log out the passwords are removed from ram and no one can read them. My goal is to have something like this, so I’m never asked for a password, I just log into my session and everything is available







  • Which is bullshit because DRM doesn’t effectively prevent ripping (source: you can find pirated hd content). So it’s literally only harmful to the customer.

    I’ll give you a quick demo of how DRM is literally useless at protecting content:

    • You need:
      • a machine with any Nvidia GPU series 600 or newer running Windows, a browser with DRM support (e.g. chrome), and optionally sunshine. This is not an uncommon setup
      • any other machine that can run moonlight (even a phone).\
    • Services often use widevine as DRM provider, so using the Nvidia machine visit this test page and make sure DRM is working
    • Normally the DRM api ensure that the decrypted content of that video can never in any form get out of a special GPU buffer, not even the browser can access it
    • enable sunshine on the machine
    • Connect from the second machine to the using moonlight and notice that the video is not being shared. DRM seems to be working correctly.
    • Now disable sunshine and enable Nvidia gamestream from GeForce experience, and set it up to share the whole desktop
    • connect from the second machine to the first using moonlight
    • now the video is being shared to the second machine, and DRM is circumvented. There is literally nothing preventing you from recording the screen on the second machine

    Now, this is a terrible way of ripping content, it causes at least one reencoding, which reduces quality (a lot of people won’t even notice it), but it is a stupidly simple working demo of DRM circumvention.

    Btw, that procedure is not the result of some study, reverse engineering, or any clever stuff. I was literally playing a game in streaming and I went “hmm, I wonder what would happen if I streamed widevine” and it just worked.


  • As the video points out, a lot of the work in xorg (and Linux in general, fwiw) is done by red hat engineers. So red hat cutting on that investment bears direct consequences for everyone else. Unless of course someone steps up and takes their place in maintenance, but it’s not gonna happen, which is literally why Wayland (and not some revamped xorg) is the future of Linux desktop.

    Also, red hat’s decisions often trickle down on most other distros. E.g.: systemd, pulseaudio, pipewire, gnome, not including proprietary codecs, etc.

    So, they technically don’t arbiter, but they definitely set the pace.





  • That’s weird because it’s against the law.

    A recent (few months ago) EU law mandates that if your platform is big enough (in the EU market) to gatekeep users from using other platforms, then it must interoperate with competing services. That means you should thrive because you make a better product, and not because it has more users.

    The fine is a considerable percentage of the company’s earnings, that supposedly even the likes of Amazon and Google cannot overlook.

    This includes Whatsapp that in a few months will have to be interoperable with competing services like telegram. This requires a protocol, the IETF is working on that. Google probably wishes to use RCS, but Matrix is also working with the IETF.

    Apple says iMessage is not that widespread in the EU and should not be included, Google says it is and should be regulated, that’s because this regulation will most likely have effects even outside the EU.







  • You are correct in saying that there are still several problems in both Wayland (e.g. lack of drawing tablet support) and mutter (e.g. tearing protocol non yet implemented). But then you proceed to list problems that are Nvidia’s fault.

    The first is weird, but it probably depends on Nvidia’s kernel driver.

    The second is probably a synchronization issue, so it’s probably due to Nvidia refusing to implement implicit sync, and explicit sync not being yet supported in Linux. But don’t quote me on that.

    Vulkan should work. But video acceleration is definitely absent, and is listed by Nvidia itself among current driver limitations. Try this.