<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;">Resolution</td>
<td>---
</td>
<td>NOTABUG
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEEDINFO
</td>
<td>RESOLVED
</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#c3">Comment # 3</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 Jonas Ådahl from <a href="show_bug.cgi?id=101345#c2">comment #2</a>)
<span class="quote">> FWIW, gnome-terminal uses a single client for all terminal windows, and
> running "gnome-terminal" will just, over D-Bus tell gnome-terminal-daemon to
> launch another window, and it'll use the Wayland display where it was first
> launched. So for that particular "issue" that is probably the cause. I
> suspect chromium works in a similar way.</span >
It does, and it will print 'Creating new window in existing session' whilst
doing so.
This is not a security issue: as a user, you have two processes
(gnome-terminal-daemon and the 'gnome-terminal' wrapper binary you are running)
which are allowed, per your local security policy, to communicate with each
other. This is usually by D-Bus, but can be by UNIX sockets, or even ptrace.
If you want to ensure you cannot access one session from another, I would
recommend running as a different user, so your permissions will prevent
accessing the compositor socket, so they will not share UNIX sockets in your
home directory, and so ptrace will also be cut off.</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>