<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><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> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - Multiple compositor crash and security problem"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101345">bug 101345</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>REOPENED
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>NOTABUG
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - Multiple compositor crash and security problem"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101345#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - Multiple compositor crash and security problem"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101345">bug 101345</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 Daniele from <a href="show_bug.cgi?id=101345#c4">comment #4</a>)
<span class="quote">> If the user can view an application on compositor A but receiving messages
> from compositor B is a security issue.</span >
What is happening is: application A is connected to compositor A. Application B
is connected to compositor B. Application A can send messages _directly_ to
application A, without the need of any compositor.
This is what gnome-terminal (and Chrome, etc) do, the same as they do under
X11. This has nothing to do with Wayland, but the design of the specific client
applications you are trying to use.
<span class="quote">> The compositor starts without root privileges and it may be easy to start a
> fake compositor created only to run a keylogger.</span >
If this is true, then you control the environment your applications run in. If
you control the environment your applications run in, then you can trace them
and modify their execution directly: you don't even need to bother running a
separate compositor.
This has nothing to do with Wayland, but you may be interested in things like
SELinux for isolation.
I understand the problems you are describing, but this is really not a security
issue introduced by Wayland. If you would like to have sessions isolated from
each other, then run them as separate users, at which point you will never be
able to connect to the other compositor (thanks to filesystem permissions) no
matter how hard you try.</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>