Robert Watson wrote:
I've modified the su(1) source in HEAD to print a message if su(1) is
executed without an effective uid of 0 (i.e., as root, or setuid as
another user). Hopefully this error message will be more suggestive than
"sorry":
paprika:~/freebsd/commit/src/usr.bin/su> ./su
su: n
On Mon, 17 Jan 2005, Ivan Voras wrote:
> >>I have a user that's in wheel group. Logging in as root works on the
> >>console, but su-ing from the user just writes 'Sorry', like the
> >>password's wrong. There are no clues in log files.
> >
> > Make sure /usr/sbin/su is suid root (and /usr isn't mo
Michael Nottebrock wrote:
On Sunday, 16. January 2005 01:07, Ivan Voras wrote:
What could be the reasons for "su root" to not work?
I have a user that's in wheel group. Logging in as root works on the
console, but su-ing from the user just writes 'Sorry', like the
password's wrong. There are no clu
On Sun, Jan 16, 2005 at 01:07:07AM +0100, Ivan Voras wrote:
> What could be the reasons for "su root" to not work?
>
> I have a user that's in wheel group. Logging in as root works on the
> console, but su-ing from the user just writes 'Sorry', like the
> password's wrong. There are no clues in
+++ Ivan Voras [Sunday 16 January 2005 02:18]:
> Kris Kennaway wrote:
> >On Sun, Jan 16, 2005 at 01:15:34AM +0100, Ivan Voras wrote:
> >
> >>Kris Kennaway wrote:
>
> /etc/pam.d/su is identical to another machine where everything works ok.
>
> >
> >OK. /etc/pam.d/su on 5.3 includes /etc/pam.
On Sunday, 16. January 2005 01:07, Ivan Voras wrote:
> What could be the reasons for "su root" to not work?
>
> I have a user that's in wheel group. Logging in as root works on the
> console, but su-ing from the user just writes 'Sorry', like the
> password's wrong. There are no clues in log files.
Thomas Dymond wrote:
Could this be anything to do with : security.bsd.suser_enabled
what's yours set to ?
security.bsd.suser_enabled: 1
But, I noticed I've got security.mac.* enabled somehow (it's not my
kernel...) - could MAC be interfering?
___
freebsd
On Sat, Jan 15, 2005 at 10:46:03PM -0500, Robert William Vesterman wrote:
> I have a similar problem, but only after I use X. I can su perfectly
> fine before using X, and I can su perfectly fine while using X (and a
> terminal window), but after exiting X, if I want to su, I have to reboot.
Yo
I have a similar problem, but only after I use X. I can su perfectly
fine before using X, and I can su perfectly fine while using X (and a
terminal window), but after exiting X, if I want to su, I have to reboot.
Ivan Voras wrote:
What could be the reasons for "su root" to not work?
I have a us
Kris Kennaway wrote:
On Sun, Jan 16, 2005 at 01:15:34AM +0100, Ivan Voras wrote:
Kris Kennaway wrote:
/etc/pam.d/su is identical to another machine where everything works ok.
OK. /etc/pam.d/su on 5.3 includes /etc/pam.d/system, so also make
sure they're in sync.
/etc/pam.d/system is the same as
On Sun, Jan 16, 2005 at 01:15:34AM +0100, Ivan Voras wrote:
> Kris Kennaway wrote:
> >On Sun, Jan 16, 2005 at 01:07:07AM +0100, Ivan Voras wrote:
>
> >>/etc/pam.d/su is identical to another machine where everything works ok.
> >
> >
> >You forgot to mention what version (4.x doesn't use /etc/pam.d
Kris Kennaway wrote:
On Sun, Jan 16, 2005 at 01:07:07AM +0100, Ivan Voras wrote:
/etc/pam.d/su is identical to another machine where everything works ok.
You forgot to mention what version (4.x doesn't use /etc/pam.d)
oops. 5.3-release.
___
freebsd-stabl
On Sun, Jan 16, 2005 at 01:07:07AM +0100, Ivan Voras wrote:
> What could be the reasons for "su root" to not work?
>
> I have a user that's in wheel group. Logging in as root works on the
> console, but su-ing from the user just writes 'Sorry', like the
> password's wrong. There are no clues in
13 matches
Mail list logo
