Announcement

Collapse
No announcement yet.

Wayland Testing New Protocol Extension To Handle Session Locking

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

  • Wayland Testing New Protocol Extension To Handle Session Locking

    Phoronix: Wayland Testing New Protocol Extension To Handle Session Locking

    Wayland Protocols 1.25 was released today as the collection of testing and stable Wayland protocols. New to Wayland Protocols 1.25 is the session-lock-v1 protocol being experimental and responsible to handle session locking...

    https://www.phoronix.com/scan.php?pa...Protocols-1.25

  • #2
    Nice. But this is proof that "privileged" protocols are possible on Wayland, so why not a protocol to query mouse position or window status, or one to add hotkeys...

    Comment


    • #3
      I would like support for logging in using Ctrl+Alt+Del like on Windows and then nothing can spoof it with fake login prompts.

      Comment


      • #4
        How is screen locking being implemented right now in Wayland?
        ## VGA ##
        AMD: X1950XTX, HD3870, HD5870
        Intel: GMA45, HD3000 (Core i5 2500K)

        Comment


        • #5
          We used to have security through obscurity.
          Now we have security through missing functionality.

          Comment


          • #6
            Originally posted by darkbasic View Post
            How is screen locking being implemented right now in Wayland?
            Probably built into the compositor.

            Comment


            • #7
              Originally posted by darkbasic View Post
              How is screen locking being implemented right now in Wayland?
              Read it again.

              "This protocol allows for a privileged Wayland client to lock the session and display arbitrary graphics while the session is locked.

              The compositor may choose to restrict this protocol to a special client launched by the compositor itself or expose it to all privileged clients, this is compositor policy.

              The client is responsible for performing authentication and informing the compositor when the session should be unlocked. If the client dies while the session is locked the session remains locked, possibly permanently depending on compositor policy."

              Comment


              • #8
                Originally posted by ssokolow View Post

                Probably built into the compositor.
                I think that's how it's done.

                Comment


                • #9
                  Originally posted by tildearrow View Post
                  Nice. But this is proof that "privileged" protocols are possible on Wayland, so why not a protocol to query mouse position or window status, or one to add hotkeys...
                  A portal for global hotkeys is actually in the works.
                  https://github.com/flatpak/xdg-deskt...tal/issues/624

                  Comment


                  • #10
                    Originally posted by tildearrow View Post
                    Nice. But this is proof that "privileged" protocols are possible on Wayland, so why not a protocol to query mouse position or window status, or one to add hotkeys...
                    Apart from being on nivida with switchable graphics, this is the main blocker for me to switch to Wayland... I use global hot keys as well as scripts to automate window movements mouse clicks etc. This is so easy with X using for example xdotool. Too easy for security, but if a program can be designated as privileged, that solves that issue.

                    Comment

                    Working...
                    X