Package: open-vm-tools
Version: 2:10.2.0-3

Hi,
I'll start with a try to map all related bugs as it is confusing enough
already.

I had reported [DEB-1] in the past which was based on [UBU-1], but then
realized there was [DEB-2]. So we closed [DEB-1] and continued in [DEB-1].
The TL;DR there as well as in [UBU-1] looking forward was that there is no
issue with newer systemd's anymore and releases having older systemd might
need the fix discussed there.

But there also is/was [UBU-2] which is actually a different issue.
I myself did mix it up as removing PrivateTmp was a solution there as well
:-/

But it is a different issue, the TL;DR on it is that due to PrivateTmp=yes
one can no more drive code execution trough VMOMI API that needs tmp.

The suggestion came by Olvier Kurth (open-vm-tools upstream) to drop
PrivateTmp from the systemd service file. This was also later verified and
considered ok by VMware testing people - you can see that part of the
history in [UBU-1].

The TL;DR for you is - would you consider dropping PrivateTmp to eliminate
this issue from Debian as well?

[DEB-1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891071
[DEB-2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888955
[UBU-1]:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780
[UBU-2]:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1758428

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

Reply via email to