<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Allow another local user to run programs on a WAYLAND_DISPLAY"
href="https://bugs.freedesktop.org/show_bug.cgi?id=84817#c13">Comment # 13</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Allow another local user to run programs on a WAYLAND_DISPLAY"
href="https://bugs.freedesktop.org/show_bug.cgi?id=84817">bug 84817</a>
from <span class="vcard"><a class="email" href="mailto:daniel@fooishbar.org" title="Daniel Stone <daniel@fooishbar.org>"> <span class="fn">Daniel Stone</span></a>
</span></b>
<pre>(In reply to Paranoik from <a href="show_bug.cgi?id=84817#c12">comment #12</a>)
<span class="quote">> The only thing
> needed to rethink were: keyboard and mouse events should only be passed to
> active window, clipboard content should only be seen to a program after user
> decides to paste its content into the window and of course user level
> applications shouldn't be able to capture the screen or other application
> windows client area and create mouse and keyboard events themselves.</span >
All these things are true of Wayland, and have been since day one.
<span class="quote">> After
> that every program running from any user profile can be allowed to access
> the desktop because no program would be able to steal info from the other
> program through the desktop or manipulate the other program through its
> graphical interface. This can absolutely be implemented during the
> development of a new API. We were told that wayland is a new modern desktop
> environment made by xorg developers who learned on previous errors. But what
> we actually see is the same level of security we had before but now programs
> are banned from appearing on the desktop. No programs no problems. Heh. Its
> like a joke about a doctor who cured disease by cutting a patient head off.
> This could be somehow achieved on a previous xorg interface there is no need
> in new API to ban programs, this is not a new level of security we needed.</span >
This is unproductive. There is no 'ban' of anything: if you want the socket to
be more widely accessible, then you can make it more widely accessible. It's
not difficult.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>