linux sysctl tunable knob kernel.yama.ptrace_scope
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
The reference lists as values 0,1,2,3.
Today I tried it on two servers :
- kernel 3.0.0
sysctl -w kernel.yama.ptrace_scope=3
error: "Invalid argument" setting key "kernel.yama.ptrace_scope"
- kernel 4.9.38
sysctl kernel.yama.ptrace_scope
error: "kernel.yama.ptrace_scope" is an unknown key
Where can I get this tunable change history ?
Is it replaced by a new name in recent kernels ?
Is the old kernel.yama.protected_sticky_symlinks renamed to fs.protected_symlinks ?
linux kernel sysctl
asked Aug 1 '17 at 19:22
Massimo
4001317
 |Â
show 2 more comments
up vote
1
down vote
favorite
The reference lists as values 0,1,2,3.
Today I tried it on two servers :
- kernel 3.0.0
sysctl -w kernel.yama.ptrace_scope=3
error: "Invalid argument" setting key "kernel.yama.ptrace_scope"
- kernel 4.9.38
sysctl kernel.yama.ptrace_scope
error: "kernel.yama.ptrace_scope" is an unknown key
Where can I get this tunable change history ?
Is it replaced by a new name in recent kernels ?
Is the old kernel.yama.protected_sticky_symlinks renamed to fs.protected_symlinks ?
linux kernel sysctl
asked Aug 1 '17 at 19:22
Massimo
4001317
1
Do these systems have anything in the directory/proc/sys/kernel/yama? If not, then they may not have been configured with yama (it's optional).
– Mark Plotnick
Aug 1 '17 at 19:28
The 4.9.38, Amazon AMI instance, hasn't /proc/sys/kernel/yama
– Massimo
Aug 1 '17 at 19:32
The 3.0.0 supports yama : I can set the values 0 and 1.
– Massimo
Aug 1 '17 at 19:32
1
As far as I can tell, yama patches were around as of 2.6, and made it into the mainstream kernel in 3.4, whereptrace_scopehad an allowable range of [0,1]. In 3.5,ptrace_scopehad an allowable range of [0,3].
– Mark Plotnick
Aug 2 '17 at 19:25
@Mark, if you make an answer I will upvote.
– Massimo
Aug 5 '17 at 22:52
 |Â
show 2 more comments
up vote
1
down vote
favorite
up vote
1
down vote
favorite
The reference lists as values 0,1,2,3.
Today I tried it on two servers :
- kernel 3.0.0
sysctl -w kernel.yama.ptrace_scope=3
error: "Invalid argument" setting key "kernel.yama.ptrace_scope"
- kernel 4.9.38
sysctl kernel.yama.ptrace_scope
error: "kernel.yama.ptrace_scope" is an unknown key
Where can I get this tunable change history ?
Is it replaced by a new name in recent kernels ?
Is the old kernel.yama.protected_sticky_symlinks renamed to fs.protected_symlinks ?
linux kernel sysctl
asked Aug 1 '17 at 19:22
Massimo
4001317
The reference lists as values 0,1,2,3.
Today I tried it on two servers :
- kernel 3.0.0
sysctl -w kernel.yama.ptrace_scope=3
error: "Invalid argument" setting key "kernel.yama.ptrace_scope"
- kernel 4.9.38
sysctl kernel.yama.ptrace_scope
error: "kernel.yama.ptrace_scope" is an unknown key
Where can I get this tunable change history ?
Is it replaced by a new name in recent kernels ?
Is the old kernel.yama.protected_sticky_symlinks renamed to fs.protected_symlinks ?
linux kernel sysctl
linux kernel sysctl
asked Aug 1 '17 at 19:22
Massimo
4001317
asked Aug 1 '17 at 19:22
Massimo
4001317
edited Sep 19 at 19:32
asked Aug 1 '17 at 19:22
Massimo
4001317
asked Aug 1 '17 at 19:22
Massimo
4001317
asked Aug 1 '17 at 19:22
Massimo
4001317
4001317
1
Do these systems have anything in the directory/proc/sys/kernel/yama? If not, then they may not have been configured with yama (it's optional).
– Mark Plotnick
Aug 1 '17 at 19:28
The 4.9.38, Amazon AMI instance, hasn't /proc/sys/kernel/yama
– Massimo
Aug 1 '17 at 19:32
The 3.0.0 supports yama : I can set the values 0 and 1.
– Massimo
Aug 1 '17 at 19:32
1
As far as I can tell, yama patches were around as of 2.6, and made it into the mainstream kernel in 3.4, whereptrace_scopehad an allowable range of [0,1]. In 3.5,ptrace_scopehad an allowable range of [0,3].
– Mark Plotnick
Aug 2 '17 at 19:25
@Mark, if you make an answer I will upvote.
– Massimo
Aug 5 '17 at 22:52
 |Â
show 2 more comments
1
Do these systems have anything in the directory/proc/sys/kernel/yama? If not, then they may not have been configured with yama (it's optional).
– Mark Plotnick
Aug 1 '17 at 19:28
The 4.9.38, Amazon AMI instance, hasn't /proc/sys/kernel/yama
– Massimo
Aug 1 '17 at 19:32
The 3.0.0 supports yama : I can set the values 0 and 1.
– Massimo
Aug 1 '17 at 19:32
1
As far as I can tell, yama patches were around as of 2.6, and made it into the mainstream kernel in 3.4, whereptrace_scopehad an allowable range of [0,1]. In 3.5,ptrace_scopehad an allowable range of [0,3].
– Mark Plotnick
Aug 2 '17 at 19:25
@Mark, if you make an answer I will upvote.
– Massimo
Aug 5 '17 at 22:52
1
1
Do these systems have anything in the directory
/proc/sys/kernel/yama ? If not, then they may not have been configured with yama (it's optional).– Mark Plotnick
Aug 1 '17 at 19:28
Do these systems have anything in the directory
/proc/sys/kernel/yama ? If not, then they may not have been configured with yama (it's optional).– Mark Plotnick
Aug 1 '17 at 19:28
The 4.9.38, Amazon AMI instance, hasn't /proc/sys/kernel/yama
– Massimo
Aug 1 '17 at 19:32
The 4.9.38, Amazon AMI instance, hasn't /proc/sys/kernel/yama
– Massimo
Aug 1 '17 at 19:32
The 3.0.0 supports yama : I can set the values 0 and 1.
– Massimo
Aug 1 '17 at 19:32
The 3.0.0 supports yama : I can set the values 0 and 1.
– Massimo
Aug 1 '17 at 19:32
1
1
As far as I can tell, yama patches were around as of 2.6, and made it into the mainstream kernel in 3.4, where
ptrace_scope had an allowable range of [0,1]. In 3.5, ptrace_scope had an allowable range of [0,3].– Mark Plotnick
Aug 2 '17 at 19:25
As far as I can tell, yama patches were around as of 2.6, and made it into the mainstream kernel in 3.4, where
ptrace_scope had an allowable range of [0,1]. In 3.5, ptrace_scope had an allowable range of [0,3].– Mark Plotnick
Aug 2 '17 at 19:25
@Mark, if you make an answer I will upvote.
– Massimo
Aug 5 '17 at 22:52
@Mark, if you make an answer I will upvote.
– Massimo
Aug 5 '17 at 22:52
 |Â
show 2 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f383263%2flinux-sysctl-tunable-knob-kernel-yama-ptrace-scope%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
Do these systems have anything in the directory
/proc/sys/kernel/yama? If not, then they may not have been configured with yama (it's optional).– Mark Plotnick
Aug 1 '17 at 19:28
The 4.9.38, Amazon AMI instance, hasn't /proc/sys/kernel/yama
– Massimo
Aug 1 '17 at 19:32
The 3.0.0 supports yama : I can set the values 0 and 1.
– Massimo
Aug 1 '17 at 19:32
1
As far as I can tell, yama patches were around as of 2.6, and made it into the mainstream kernel in 3.4, where
ptrace_scopehad an allowable range of [0,1]. In 3.5,ptrace_scopehad an allowable range of [0,3].– Mark Plotnick
Aug 2 '17 at 19:25
@Mark, if you make an answer I will upvote.
– Massimo
Aug 5 '17 at 22:52