On 01/09/2020 11:19, Daniel P. Berrangé wrote:
> On Tue, Sep 01, 2020 at 12:11:11PM +0200, Christian Ehrhardt wrote:
>> On Thu, May 28, 2020 at 12:45 PM Simon Arlott wrote:
>>>
>>> The VM does not need read permission for its own sockets to create,
>>> bind(), listen(), accept() connections or to
On 01/09/2020 11:11, Christian Ehrhardt wrote:
> On Thu, May 28, 2020 at 12:45 PM Simon Arlott wrote:
>>
>> The VM does not need read permission for its own sockets to create,
>> bind(), listen(), accept() connections or to recv(), send(), etc. on
>> those connections.
>>
>> This was fixed in ab95
On Tue, Sep 01, 2020 at 12:11:11PM +0200, Christian Ehrhardt wrote:
> On Thu, May 28, 2020 at 12:45 PM Simon Arlott wrote:
> >
> > The VM does not need read permission for its own sockets to create,
> > bind(), listen(), accept() connections or to recv(), send(), etc. on
> > those connections.
> >
On Thu, May 28, 2020 at 12:45 PM Simon Arlott wrote:
>
> The VM does not need read permission for its own sockets to create,
> bind(), listen(), accept() connections or to recv(), send(), etc. on
> those connections.
>
> This was fixed in ab9569e5460d1e4737fe8b625c67687dc2204665
> (virt-aa-helper:
The VM does not need read permission for its own sockets to create,
bind(), listen(), accept() connections or to recv(), send(), etc. on
those connections.
This was fixed in ab9569e5460d1e4737fe8b625c67687dc2204665
(virt-aa-helper: disallow VNC socket read permissions),
but then b6465e1aa49397367a