On 7/26/22 14:17, Hector Gonzalez Jaime via Dng wrote:
On 7/26/22 10:00, Ken Dibble wrote:
On 7/25/22 09:29, Ken Dibble wrote:
This is the first time I have seen this with any package.
I have no idea whether it has happened with packages not installed
on my systems.
It is my
On 7/26/22 10:00, Ken Dibble wrote:
On 7/25/22 09:29, Ken Dibble wrote:
This is the first time I have seen this with any package.
I have no idea whether it has happened with packages not installed on
my systems.
It is my understanding that best practice is noexec on /tmp and that
this is
On 7/25/22 09:29, Ken Dibble wrote:
This is the first time I have seen this with any package.
I have no idea whether it has happened with packages not installed on
my systems.
It is my understanding that best practice is noexec on /tmp and that
this is a Debian recommendation.
Here is
This is the first time I have seen this with any package.
I have no idea whether it has happened with packages not installed on my
systems.
It is my understanding that best practice is noexec on /tmp and that
this is a Debian recommendation.
Here is the relevant line from /etc/fstab.
