> basically, as root i did: "chmod 4111 /usr/local/bin/su"
I would rather suggest
chmod 4755 /usr/local/bin/su
that gives you standard permissions for su (rwsr-xr-x)
Regardless of what they were before
- Alex
---
This SF.net email is sponso
On Thursday 29 May 2003 03:02 pm, Theodore Wynnychenko wrote:
> thanks for everyone's help and input.
NP
> basically, as root i did: "chmod 4111 /usr/local/bin/su"
>
> (not "chmod +4111 /usr/local/bin/su" - the "+411" in my last email was a
> typo - i had been trying "+4111")
>
> i don't really
thanks for everyone's help and input.
you know what they say - a little knowldege is a dangerous thing.
anyway, su now works.
basically, as root i did: "chmod 4111 /usr/local/bin/su"
(not "chmod +4111 /usr/local/bin/su" - the "+411" in my last email was a
typo - i had been trying "+4111")
i
Lynn pretty much covered this one, but I wanted to add one suggestion.
After you run the chmod (not CHMOD; Unix/Linux is case sensitive) command
as Lynn advises, then run "ls -l /usr/local/bin/su" to verify that the
permissions are set properly (that is, that they match the example Lynn
showed
On Thursday 29 May 2003 10:11 am, Theodore Wynnychenko wrote:
> lynn-
>
> sorry, i wasn't ignoring anything.
>
> i guess i just didn't say it. but i did EXACTLY what you suggested.
>
> i logged in as ROOT (via lshd), and typed "chmod +411 /usr/local/bin/su"
>
> after this i logged out, went back t
good idea. but "chmod +4111
/path/to/su"
executed as root, did not change the error/problem.
thanks for your - ted
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Lynn Avants
Sent: Thursday, May 29, 2003 8:57 AM
To: [EMAIL PROTECTED]
Subject: Re: [
On Thursday 29 May 2003 09:25 am, Theodore Wynnychenko wrote:
> > any other ideas on login or su?
>
> As 'root', do:
> chmod +4111 /path/to/su
>
> If 'su' isn't run suid, then most likely /etc/shadow isn't
> being read because 'su' is running as your non-root user.
> --
> ~Lynn Avants
> Linux Embed
> any other ideas on login or su?
As 'root', do:
chmod +4111 /path/to/su
If 'su' isn't run suid, then most likely /etc/shadow isn't
being read because 'su' is running as your non-root user.
--
~Lynn Avants
Linux Embedded Appliance Firewall Developer
-
ok, i tried chmod, still g
On Wednesday 28 May 2003 06:15 pm, Theodore Wynnychenko wrote:
> any other ideas on login or su?
As 'root', do:
chmod +4111 /path/to/su
If 'su' isn't run suid, then most likely /etc/shadow isn't
being read because 'su' is running as your non-root user.
--
~Lynn Avants
Linux Embedded Appliance
thanks Ray. i tried using login.
after connecting via lsh with a user account i tried "login". i also tried
"login root",
"exec login", "exec login root"
they all return the same message:
No utmp entry. you must exec "login" from the lowest level "sh"
also, when i use the "exec login" ver
At 12:22 PM 5/28/2003 -0500, [EMAIL PROTECTED] wrote:
again, i would like to thank everyone for their input.
yes, the su binary comes from (i think) the Dach distribution.
there is not a problem with path. the command does execute when it
resides in /usr/local/bin.
in fact, if i log in as root, i
again, i would like to thank everyone for their input.
yes, the su binary comes from (i think) the Dach distribution.
there is not a problem with path. the command does execute when it
resides in /usr/local/bin.
in fact, if i log in as root, i can su to root (no password required),
and i do get
> Normally, disabling root logins in regular sshd does NOT prevent
> use of su.
> (I routinely set up sshd this way on my servers.) I'd be surprised if lsh
> is different here ... but once more, I cannot be certain.
neither lshd nor sshd or telnetd could prevent the use of su, because they
simply
On Wednesday 28 May 2003 10:02 am, Ray Olszewski wrote:
> Lynn -- I didn't comment initially, because I'm not sure of what I'm about
> to say. But on other systems I've used, this problem arises when su is not
> properly set up to use PAM password processing. Hence, every possible
> password (inclu
Lynn -- I didn't comment initially, because I'm not sure of what I'm about
to say. But on other systems I've used, this problem arises when su is not
properly set up to use PAM password processing. Hence, every possible
password (including the right one) reads as incorrect.
The original poster
On Tuesday 27 May 2003 10:26 pm, [EMAIL PROTECTED] wrote:
> well, again thanks. hearing that it had worked for others without major
> issues made me go back over some basics. I had a relatively OLD copy of
> putty, so i got a newer release. Now, lshd works. Finally, I can do
> away with the the
well, again thanks. hearing that it had worked for others without major
issues made me go back over some basics. I had a relatively OLD copy of
putty, so i got a newer release. Now, lshd works. Finally, I can do
away with the the extra monitor (back to the basement).
anyway, i have one final q
17 matches
Mail list logo
