"Erika" writes:
>When I log in as that user and type linuxconf, long pause (searching for
>something??)
Jacques' wierd translation system is getting caught up in its own stack.
>then a segmentation fault and binary core dump, thought a path
>problem? so logged in as root and su'd as user (still had root env etc) and
>got same results - What I am doing wrong? Need to set file permissions/dir
>permissions? Help ! (thanks :) !!)
You can, if you don't worry about security, change the linuxconf
binary to be setuid root. chmod u+s /bin/linuxconf
You will note that Red Hat Linux doesn't ship that way; that's on
purpose. There have been holes found in linuxconf in the past, and
I am pretty sure that more could be found.
For Red Hat Linux 5.2, we have changed the default so that non-root
users cannot even start linuxconf -- they don't have permissions to
execute it. That gets rid of the segfault.
michaelkjohnson
"Magazines all too frequently lead to books and should be regarded by the
prudent as the heavy petting of literature." -- Fran Lebowitz
Linux Application Development http://www.redhat.com/~johnsonm/lad/
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
