CONFIG_GRKERNSEC_CHROOT_FINDTASK, pipe communication, bash
Posted: Fri Oct 27, 2006 2:23 pm
When enabling CONFIG_GRKERNSEC_CHROOT_FINDTASK, grsec complains about processes piping to another when they are started from a bash login shell, in my particular case being spawned by a chrooted sshd.
Example:
Also, no problems with directly running
I've searched high and low for other people having the same problem. All I came up with is a discussion on the grsec mailing list, which has remotely to do with the topic (bash oddities, that is): http://www.grsecurity.net/pipermail/grs ... 00522.html
As I could reproduce that issue in combination with bash as well, I disabled random PIDs, however, as expected this did not resolve my actual problem ;-).
Tested with 2.6.17.11-grsec. Insights, anyone? (besides changing the login shell)
Sorry if I'm overlooking something obvious.
Example:
- Code: Select all
# echo test |grep test
-bash: child setpgid (28927 to 28926): Operation not permitted
test
- Code: Select all
#!/bin/bash
echo test |grep test
Also, no problems with directly running
- Code: Select all
chroot /chroot echo test |grep test
I've searched high and low for other people having the same problem. All I came up with is a discussion on the grsec mailing list, which has remotely to do with the topic (bash oddities, that is): http://www.grsecurity.net/pipermail/grs ... 00522.html
As I could reproduce that issue in combination with bash as well, I disabled random PIDs, however, as expected this did not resolve my actual problem ;-).
Tested with 2.6.17.11-grsec. Insights, anyone? (besides changing the login shell)
Sorry if I'm overlooking something obvious.