Aleksa Sarai writes:
> On 2017-08-06 02:52, Aleksa Sarai wrote:
>> It appears as though the addition of the PID namespace did not update
>> the output code for /proc/$pid/sched, which made it trivial to figure
>> out whether a process was inside _pid_ns from userspace (making
>>
Aleksa Sarai writes:
> On 2017-08-06 02:52, Aleksa Sarai wrote:
>> It appears as though the addition of the PID namespace did not update
>> the output code for /proc/$pid/sched, which made it trivial to figure
>> out whether a process was inside _pid_ns from userspace (making
>> container
On 2017-08-06 02:52, Aleksa Sarai wrote:
It appears as though the addition of the PID namespace did not update
the output code for /proc/$pid/sched, which made it trivial to figure
out whether a process was inside _pid_ns from userspace (making
container detection trivial[1]). This lead to
On 2017-08-06 02:52, Aleksa Sarai wrote:
It appears as though the addition of the PID namespace did not update
the output code for /proc/$pid/sched, which made it trivial to figure
out whether a process was inside _pid_ns from userspace (making
container detection trivial[1]). This lead to
It appears as though the addition of the PID namespace did not update
the output code for /proc/$pid/sched, which made it trivial to figure
out whether a process was inside _pid_ns from userspace (making
container detection trivial[1]). This lead to situations such as:
% unshare -pf head -n1
It appears as though the addition of the PID namespace did not update
the output code for /proc/$pid/sched, which made it trivial to figure
out whether a process was inside _pid_ns from userspace (making
container detection trivial[1]). This lead to situations such as:
% unshare -pf head -n1
6 matches
Mail list logo