Announcement

Collapse
No announcement yet.

Replay Protected Memory Block "RPMB" Subsystem Submitted For Linux 6.12

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Replay Protected Memory Block "RPMB" Subsystem Submitted For Linux 6.12

    Phoronix: Replay Protected Memory Block "RPMB" Subsystem Submitted For Linux 6.12

    The MMC updates for the Linux 6.12 kernel include the introduction of a new kernel subsystem for Replay Protected Memory Block (RPMB) drivers...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    ...trusted...

    Comment


    • #3
      I hope like hell that the first exploit is named Pro Action.

      Comment


      • #4
        Originally posted by nuetzel View Post
        ...trusted...
        It's fun to pretend sometimes. If Linux plays along well enough then maybe eventually we'll get things like 4K Netflix video playback and other support that requires high levels of Widevine DRM. This would also require HDCP support from Wayland compositors though for "protected" playback which Wlroots would veto. They have a policy of using their position in Wayland protocols to always block any standard position involving DRM, so thank you for that. It's one thing allowing the building blocks for DRM in the kernel but another to actively implement it.

        Comment


        • #5
          Originally posted by ahrs View Post

          It's fun to pretend sometimes. If Linux plays along well enough then maybe eventually we'll get things like 4K Netflix video playback and other support that requires high levels of Widevine DRM. This would also require HDCP support from Wayland compositors though for "protected" playback which Wlroots would veto. They have a policy of using their position in Wayland protocols to always block any standard position involving DRM, so thank you for that. It's one thing allowing the building blocks for DRM in the kernel but another to actively implement it.
          Personally I will always build any kernels supporting digital RESTRICTIONS management with it disabled, my guess is this would mostly by used by Google for Chromebooks. Seeing that wlroots is keeping this kind of DRM (as opposed to "direct rendering...) out of wayland makes me glad to be using wayfire, which is wlroots based.

          As for Netflix, I don't have an account with them or want one. Same for Hulu and all those other locked media vendors. Widevine DRM is banned from my machines and kept turned all the way off in Firefox here. You never know what ELSE is in that kind of blob aimed solely at controlling users, and a computer can be trusted by at most one party. For my purposes that cannot be the RIAA or MPAA.

          Comment


          • #6
            I've experimented extensively with RPMB on Android. I don't believe RPMB is a suitable solution for storing secrets per se, as it lacks any built-in encryption. While a secret key is required for writing to RPMB, reading from it is still possible without a key. However, using a secret key for reading can verify data integrity.

            Comment

            Working...
            X