Re: su su- sudo dont work

Am 27.01.24 um 10:23 schrieb Hans: I see this exactly as you and are watching this list for may years. However, I wanted not to be so directly because I want not to blame anyone on this list. But since the beginning, I had the suspicion, that someone just wants to make fun with us. Aleady from

Re: su su- sudo dont work

Yes, He/She is back again. In my opinion no serious request intended by this "person". Same approach as last time (and the issues before) * crying for help (destroyed OS) * no real answers to questions * repeating the same complain frequently Some possibilities 1. Shity AI 2. Troll 3. Bored

Re: su su- sudo dont work

> On 23 Jan 2024, at 18:30, Hans wrote: > > Am Dienstag, 23. Januar 2024, 13:54:25 CET schrieb Schwibinger Michael: > For gvetting root as normal user, best is use "su -". > > Note: It is not "su-", but "su -", with a space between su and the minus sign. Also su requires root's password, no

Re: su su- sudo dont work

-- > *Von:* Greg Wooledge > *Gesendet:* Samstag, 20. Januar 2024 14:14 > *An:* debian-user@lists.debian.org > *Betreff:* Re: su su- sudo dont work > > On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote: > > Good afternoon. > > Root terminal is fine.

Re: su su- sudo dont work

On Sat, 2024-01-20 at 13:26 +, Schwibinger Michael wrote: > > Good afternoon. > Root terminal is fine. > What do I do wrong? > What did I destroy? > > > PC does have only one user=admin. > > > Regards Sophie > Is it the rescue mode? Hellow Sophie, English is not my native language. Somet

Re: su su- sudo dont work

Hi, On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote: > Good afternoon. > Root terminal is fine. > What do I do wrong? > What did I destroy? h-boy, strap yourselves in for another epic Sophie/Michael thread. A bit like the Gene ones, though tend to be circular across a much

Re: su su- sudo dont work

On Sat 20 Jan 2024 at 09:14:30 (-0500), Greg Wooledge wrote: > On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote: > > Good afternoon. > > Root terminal is fine. > > What do I do wrong? > > What did I destroy? > > > > PC does have only one user=admin. > > > > Regards Sophie > > I

Re: su su- sudo dont work

Schwibinger Michael wrote: > Good afternoon. > Root terminal is fine. > What do I do wrong? > What did I destroy? > > PC does have only one user=admin. > > Regards Sophie > Is it the rescue mode? Please tell us: exactly what rescue mode you were using exactly what the prompt was exactly w

Re: su su- sudo dont work

Am Samstag, 20. Januar 2024, 14:26:06 CET schrieb Schwibinger Michael: There is not "su su-", but there is su = change to root, envirenmont of former user without changing of X environment (hope, this is corect said) su -= change to root, environment of user root su -p = change to root

Re: su su- sudo dont work

On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote: > Good afternoon. > Root terminal is fine. > What do I do wrong? > What did I destroy? > > PC does have only one user=admin. > > Regards Sophie > Is it the rescue mode? Explain, please. Your Subject: header says "su su- sudo d

Re: su

On 14/09/2023 22:26, Vincent Lefevre wrote: I noticed the issue just before the upgrade to bookworm (I wanted to do that for the upgrade). But I can't reproduce it in bookworm. So this may have been an old bug that has been fixed. I do not follow the topic, so I can not attribute changes to pa

Re: su

On 2023-09-14 21:25:56 +0700, Max Nikulin wrote: > On 14/09/2023 17:30, Vincent Lefevre wrote: > > Yes, XDG_RUNTIME_DIR is problematic, but as "su -" doesn't work in > > GNU Screen (it yields major display issues), I presume that some > > environment variables (terminal related?) are still useful.

Re: su

On 14/09/2023 17:30, Vincent Lefevre wrote: Yes, XDG_RUNTIME_DIR is problematic, but as "su -" doesn't work in GNU Screen (it yields major display issues), I presume that some environment variables (terminal related?) are still useful. I just have tried it. "su -" preserves TERM=screen.xterm-25

Re: su

On 2023-09-06 14:36:48 +0700, Max Nikulin wrote: > On 06/09/2023 10:41, Greg Wooledge wrote: > > > > Just put "ALWAYS_SET_PATH yes" into /etc/default/su and the problem > > is FIXED. "su" will work properly again! > > Greg, you provided a valid example when "su -" is undesirable, however in > ge

Re: su

On 2023-09-05, Greg Wooledge wrote: > How *incredibly* Red Hat. Really, it just sickens me that this is the > answer accepted by so many people. It's not Red Hat, it's man page and own practice, even before Red Hat exists :) > To perform that installation, you run "su", which gives you a root s

Re: su

On 06/09/2023 10:41, Greg Wooledge wrote: Just put "ALWAYS_SET_PATH yes" into /etc/default/su and the problem is FIXED. "su" will work properly again! Greg, you provided a valid example when "su -" is undesirable, however in general "su -" is safer than just "su" since it resets some user s

Re: su

On Tue, 5 Sep 2023 23:41:45 -0400 Greg Wooledge wrote: > To perform that installation, you run "su", which gives you a root > shell, and then you do something like "make install". > > But the Red Hat answer says you should use "su -" instead, to become > root. What happens now? You've created a

Re: su

On Wed, Sep 06, 2023 at 05:09:29AM +0200, Michel Verdier wrote: > On 2023-09-05, Greg Wooledge wrote: > > > You used "su" to become root, I believe. Unfortunately, beginning > > with Debian 9, "su" with no arguments and no configuration doesn't > > behave the way it used to behave. Specifically,

Re: su does not work anymore

On Saturday 02 May 2020 07:19:13 The Wanderer wrote: > On 2020-05-02 at 06:57, Sven Joachim wrote: > > On 2020-05-02 10:57 +0200, Rainer Dorsch wrote: > >> Am Samstag, 2. Mai 2020, 06:32:02 CEST schrieb Andrei POPESCU: > >>> Ugh. For such situations one should either have good backups or > >>> a r

Re: su does not work anymore

On 2020-05-02 at 08:32, Carl Fink wrote: > On 5/2/20 7:19 AM, The Wanderer wrote: > >> Manual recovery like this *can* be done, but I do not recommend >> embarking upon it without very strong reason. (In my case, I needed >> to fix the filenames and permissions of my entire /home partition >> an

Re: su does not work anymore

On 5/2/20 7:19 AM, The Wanderer wrote: Manual recovery like this *can* be done, but I do not recommend embarking upon it without very strong reason. (In my case, I needed to fix the filenames and permissions of my entire /home partition anyway, and that includes irreplaceable data measuring in te

Re: su does not work anymore

On 2020-05-02 at 06:57, Sven Joachim wrote: > On 2020-05-02 10:57 +0200, Rainer Dorsch wrote: > >> Am Samstag, 2. Mai 2020, 06:32:02 CEST schrieb Andrei POPESCU: >>> Ugh. For such situations one should either have good backups or >>> a reasonably fast and automated method of reinstalling the >>>

Re: su does not work anymore

On 2020-05-02 10:57 +0200, Rainer Dorsch wrote: > Am Samstag, 2. Mai 2020, 06:32:02 CEST schrieb Andrei POPESCU: >> On Vi, 01 mai 20, 22:32:58, Rainer Dorsch wrote: >> > Hello, >> > >> > I had an accidential / in a >> > >> > # chown -R install-user /xyz/dfak / >> > >> > command. Changing the owner

Re: su does not work anymore

Am Samstag, 2. Mai 2020, 06:32:02 CEST schrieb Andrei POPESCU: > On Vi, 01 mai 20, 22:32:58, Rainer Dorsch wrote: > > Hello, > > > > I had an accidential / in a > > > > # chown -R install-user /xyz/dfak / > > > > command. Changing the ownership / recursively is certainly not a good > > idea. >

Re: su does not work anymore

On Vi, 01 mai 20, 22:32:58, Rainer Dorsch wrote: > Hello, > > I had an accidential / in a > > # chown -R install-user /xyz/dfak / > > command. Changing the ownership / recursively is certainly not a good idea. Ugh. For such situations one should either have good backups or a reasonably fast a

Re: su won't work from a debian live USB install

On Sun, 2017-06-25 at 19:20 -0400, daniel theobald wrote: > I installed the Debian 9 from a Debian live amd64 image I downloaded > today.  Everything works great, but I can't su to apt-get anything > new. > > theo@debian:~$ su > Password:  > su: Authentication failure > > I have reinstalled twice

Re: su won't work from a debian live USB install

Hello, On 06/25/2017 07:20 PM, daniel theobald wrote: I installed the Debian 9 from a Debian live amd64 image I downloaded today. Everything works great, but I can't su to apt-get anything new. theo@debian:~$ su Password: su: Authentication failure I have reinstalled twice, being super caref

Re: "su is really a broken concept"

You're probably right, Jonathan. "Su" is so common that it easy to make that error. After looking at the current POSIX list, I did not find it. Thank you for pointing that out. Be well! T.J. On Wed, Sep 2, 2015 at 10:55 PM, Jonathan de Boyne Pollard < j.deboynepollard-newsgro...@ntlworld.com> wr

Re: "su is really a broken concept"

T.J. Duchene: If someone can do it better, and still keep it compatible with POSIX, more power to them. This is not the first place where someone has randomly thrown POSIX into the discussion. "su" is outwith the scope of the POSIX standard. It's in the SVID, but to my knowledge "su" never

Re: "su is really a broken concept"

On Tue, 2015-09-01 at 01:25 +0100, Jonathan de Boyne Pollard wrote: > Lennart Poettering > (https://github.com/systemd/systemd/issues/825#issuecomment-127917622): > > > Long story short: su is really a broken concept. > > > > Christian Seiler: > > > > So it's not like su is suddenly broken - it

Re: "su is really a broken concept"

Lennart Poettering (https://github.com/systemd/systemd/issues/825#issuecomment-127917622): Long story short: su is really a broken concept. Christian Seiler: So it's not like su is suddenly broken - it's just that some specific new use cases don't work properly with it. A fair number

Re: su chmod -755 /usr

Julian Brooks wrote: > Cheers Bob :) > > Uuummm - work files yes, system configs/settings not really. > > Any top tips, like where are the permission file/s? I think you are asking what backup software would be recommended? There are many different ones. Let me point to a reference. https:/

Re: su chmod -755 /usr

Cheers Bob :) Uuummm - work files yes, system configs/settings not really. Any top tips, like where are the permission file/s? On 12 June 2015 at 22:07, Bob Proulx wrote: > Julian Brooks wrote: > > All seems well, valuable lesson(s) learnt. > > Seriously thought it was terminal, appreciate th

Re: su chmod -755 /usr

Julian Brooks wrote: > All seems well, valuable lesson(s) learnt. > Seriously thought it was terminal, appreciate the wisdom people. Glad to hear you solved your problem. In the future with a similar problem you would be able to restore your current system permissions from your backup. Not the e

Re: su chmod -755 /usr

Many thanks for the replies. (I did say I'm sketchy here) I was attempting to alter permissions on a folder. I then read that all folders leding up to it must also have permission altered. So I then mistakenly actually ran 'sudo chmod -755 /usr/lib/TheFolderIMeantToAlter' and all folders leadin

Re: su chmod -755 /usr

Helllo Julian, Should just be to revert the change with 'chmod 755 /usr'. On 10 June 2015 at 05:40, Julian Brooks wrote: > Hey all, > > Yes I'm an idiot... > > Not very experienced user here - 1st post: > > I mistakenly ran 'chmod -755 /usr'. > > How can I fix my permissions? > > Haven't reboot

Re: su chmod -755 /usr

Julian Brooks writes: >Hey all, >Yes I'm an idiot... >Not very experienced user here - 1st post: >I mistakenly ran 'chmod -755 /usr'. >How can I fix my permissions? Run 'chmod 755 /usr'. All your command did was remove permissions from the /usr directory. Just set them back the default. No

Re: su - root

On Ma, 03 sep 13, 03:09:46, Zenaan Harkness wrote: > Can anyone explain to me the message here "Added user root.": > > $ su - root > Password: > Added user root. > ~# Doesn't happen here. > Did not happen with "sudo su -". What does it mean?? BTW, you don't need 'su -' with sudo, just use -i.

Re: su user -c

On Thu, Jun 6, 2013 at 9:22 AM, Pol Hallen wrote: > Hi all :-) > > this is the part of my script: > > email0=us...@domain0.org;email1=us...@domain1.org;name=user0;username=user1;domainname=domain0;echo > | mutt -s "test message $name" -b email0 email1 > > if I run this script of own user, runs cor

Re: "su" - timeout for dbus/system_bus_socket if $DISPLAY set but unreachable

Sven Uhlig wrote: > Bob Proulx wrote: > > getent baldur.asgard > > That is why I used C's getnameinfo(). > > How should getent work? > > # getent baldur.asgard > Unknown database: baldur.asgard Sorry. That was a bad example on my part. The first parameter is the map name and the second is the

Re: "su" - timeout for dbus/system_bus_socket if $DISPLAY set but unreachable

On 17.03.2013 03:12, Bob Proulx wrote: > Sven Uhlig wrote: >> Bob Proulx wrote: The problem is that "su" takes 25 seconds before it succeeds. >>> >>> That sounds like a DNS timeout. If you do a dns lookup of your >>> systems hostname does it respond? >> >> # nslookup baldur ** server c

Re: "su" - timeout for dbus/system_bus_socket if $DISPLAY set but unreachable

On 17.03.2013 02:53, Clive Standbridge wrote: >> The reasons seems to be my setup of the system. >> Debian runs in a VirtualBox environment, headless and w/o X server. >> I use ssh to connect to the system. (putty) >> I use X forwarding to run X applications on the system. >> The variable $DISPLAY

Re: "su" - timeout for dbus/system_bus_socket if $DISPLAY set but unreachable

> The reasons seems to be my setup of the system. > Debian runs in a VirtualBox environment, headless and w/o X server. > I use ssh to connect to the system. (putty) > I use X forwarding to run X applications on the system. > The variable $DISPLAY gets set to 10.0.2.2:0 after ssh auth. Sven, I'm

Re: "su" - timeout for dbus/system_bus_socket if $DISPLAY set but unreachable

Sven Uhlig wrote: > Bob Proulx wrote: > >> The problem is that "su" takes 25 seconds before it succeeds. > > > > That sounds like a DNS timeout. If you do a dns lookup of your > > systems hostname does it respond? > > # nslookup localhost > Name: localhost > Address: 127.0.0.1 > > # nslookup 1

Re: "su" - timeout for dbus/system_bus_socket if $DISPLAY set but unreachable

On 16.03.2013 05:45, Bob Proulx wrote: >> The problem is that "su" takes 25 seconds before it succeeds. > > That sounds like a DNS timeout. If you do a dns lookup of your > systems hostname does it respond? # nslookup localhost Name: localhost Address: 127.0.0.1 # nslookup 127.0.0.1 1.0.0.127.

Re: "su" - timeout for dbus/system_bus_socket if $DISPLAY set but unreachable

Sven Uhlig wrote: > this is my first message to this list. Welcome. > I noticed a little problem on my system after I installed the package > "virt-manager" and its dependencies on my system. One of the > dependencies is "dbus". Ugh. "dbus". I feel your pain. Too many applications have egregi

Re: su without a password (not root)

On 05/27/11 at 05:28pm, Stanisław Findeisen wrote: > On 2011-05-26 22:11, William Hopkins wrote: > > On 05/26/11 at 07:31pm, Stanisław Findeisen wrote: > >> pam_wheel lets you su to root without typing a password if you are a > >> member of a specific group. > >> > >> I need a PAM module with more

Re: su without a password (not root)

On 2011-05-26 22:11, William Hopkins wrote: > On 05/26/11 at 07:31pm, Stanisław Findeisen wrote: >> pam_wheel lets you su to root without typing a password if you are a >> member of a specific group. >> >> I need a PAM module with more flexible applicant user / target user >> pairs management. For

Re: su without a password (not root)

On 05/26/11 at 07:31pm, Stanisław Findeisen wrote: > pam_wheel lets you su to root without typing a password if you are a > member of a specific group. > > I need a PAM module with more flexible applicant user / target user > pairs management. For instance I'd like to be able to su with no > passw

Re: su without a password (not root)

How about using sudo + sudoers instead? 2011/5/26 Stanisław Findeisen : > pam_wheel lets you su to root without typing a password if you are a > member of a specific group. > > I need a PAM module with more flexible applicant user / target user > pairs management. For instance I'd like to be able

Re: su stopped working (after upgrade to squeeze)

On Wed, 2010-10-27 at 14:48 +0200, Hanspeter Kunz wrote: > On Tue, 2010-10-26 at 17:45 +, Camaleón wrote: > > On Tue, 26 Oct 2010 14:44:08 +0200, Hanspeter Kunz wrote: > > > > > I have a strange problem on one of my debian squeeze boxes. when I try > > > to become root (or any other local user

Re: su stopped working (after upgrade to squeeze)

On Tue, 2010-10-26 at 17:45 +, Camaleón wrote: > On Tue, 26 Oct 2010 14:44:08 +0200, Hanspeter Kunz wrote: > > > I have a strange problem on one of my debian squeeze boxes. when I try > > to become root (or any other local user), su fails with > > > > su: Authentication failure > > > > a

Re: su stopped working (after upgrade to squeeze)

On Tue, 26 Oct 2010 14:44:08 +0200, Hanspeter Kunz wrote: > I have a strange problem on one of my debian squeeze boxes. when I try > to become root (or any other local user), su fails with > > su: Authentication failure > > and no, the password is correct :) (...) > My best guess is, tha

Re: su?

On Monday 13 September 2010 15:12:48 hugo vanwoerkom wrote: > But you are > reading from this funny screen that is hanging some distance in front of > you. So you zero in on that backlit panel while your back is killing you > all the while being grateful to technology for putting you into such a >

Re: su?

David Jardine wrote: On Sat, Sep 11, 2010 at 04:36:48PM -0400, Doug wrote: Tried to run a program from command line needing admin capability. Input su /usr/sbin/synaptic Get message Unknown id: /usr/sbin/synaptic Logged in as root, put in password, ran /usr/sbin/synaptic and the file ran fin

Re: su?

Doug wrote: Tried to run a program from command line needing admin capability. Input su /usr/sbin/synaptic Get message Unknown id: /usr/sbin/synaptic Logged in as root, put in password, ran /usr/sbin/synaptic and the file ran fine. Is there no su in Debian? If not what replaces it? /bin/

Re: su?

On Sat, Sep 11, 2010 at 04:36:48PM -0400, Doug wrote: > Tried to run a program from command line needing admin > capability. > > Input su /usr/sbin/synaptic > > Get message Unknown id: /usr/sbin/synaptic > > Logged in as root, put in password, ran > /usr/sbin/synaptic > > and the file ran fine.

Re: su?

On 09/12/2010 02:06 AM, Doug wrote: Tried to run a program from command line needing admin capability. Input su /usr/sbin/synaptic Get message Unknown id: /usr/sbin/synaptic Logged in as root, put in password, ran /usr/sbin/synaptic and the file ran fine. Is there no su in Debian? If not w

Re: su?

On 11 September 2010 13:36, Doug wrote: > Is there no su in Debian?  If not what replaces it? Yes there is. There's also 'man'. :-) Try 'man su' and you'll see you need -c if you want to run a command. Maybe you are confused with 'sudo'? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.deb

Re: su and environment.

Thank You for Your time and answer, Bob: > > $ su -c 'abc' -l anotheruser > > > > but it returns > > > > -su: abc: command not found > > > > The abc is in the anotheruser's path, but it seems option '-l' does > > not work here. > > > > How I can accomplish the goal (without manually specifying

Re: su and environment.

Sthu Deus wrote: > $ su -c 'abc' -l anotheruser > -su: abc: command not found > > The abc is in the anotheruser's path, but it seems option '-l' does not > work here. A very confusing topic and one often discussed is the process bash uses to start up and what environment files are processed and a

Re: su and environment.

On 07/08/2010 02:27 AM, Sthu Deus wrote: > Good day. > > The following: > > $ su -c 'abc' -l anotheruser > > but it returns > > -su: abc: command not found > > The abc is in the anotheruser's path, but it seems option '-l' does not > work here. > > How I can accomplish the goal (without manua

Re: su doesn't work "Authentication failure"

"Dennis G. Wicks" <[EMAIL PROTECTED]> writes: > > Kevin Buhr wrote the following on 01/31/2008 12:50 PM: > > From aptitude show login ==>> 1:4.0.18.1-7 <<== >> should give: >> >> 1381ae1ac77b512258657b096522bb6a /bin/su >c80fc747e24fa8bfa099cbef0bfb926f /bin/su <<== > from md5

Re: su doesn't work "Authentication failure"

On Feb 1, 2008 1:10 PM, Dennis G. Wicks <[EMAIL PROTECTED]> wrote: > What should I be worried about and start looking for? > BTW, nobody can get access to my system unless they > break into my house, and that hasn't happened. I even > did a reinstall of the login package just to make sure > the abo

Re: su doesn't work "Authentication failure"

Kevin Buhr wrote the following on 01/31/2008 12:50 PM: > paul <[EMAIL PROTECTED]> writes: >> It is possible to do 'su someuser' from root but it's not possible to >> get back to root then using just 'su' or change from a normal user to >> another user account. > > [ . . . ] > >> Jan 31 15:44:18 m

Re: su doesn't work "Authentication failure"

Kevin Buhr <[EMAIL PROTECTED]> writes: > > If your version of the "login" package is the latest official Etch > version 1:4.0.18.1-7, then "md5sum /bin/su" should give: > > 1381ae1ac77b512258657b096522bb6a /bin/su Sorry. That was sloppy of me. The above hash is for the amd64 architecture.

Re: su doesn't work "Authentication failure"

paul <[EMAIL PROTECTED]> writes: > > It is possible to do 'su someuser' from root but it's not possible to > get back to root then using just 'su' or change from a normal user to > another user account. [ . . . ] > Jan 31 15:44:18 myserver su[27729]: (pam_unix) authentication failure; > logname=

Re: su doesn't work "Authentication failure"

paul wrote: Hello, on my debian etch machine 'su' doesn't work if a password is needed. It is possible to do 'su someuser' from root but it's not possible to get back to root then using just 'su' or change from a normal user to another user account. myserver:/tmp$ su Password: su: Authenticati

Re: su and administrator password fails in gnome

On Jan 3, 2:10 am, Sven Joachim <[EMAIL PROTECTED]> wrote: > Then your system is rather unusual, to say the least. The following > programs are 1755 on my system: > > /bin/su > /bin/mount > /bin/umount > /bin/ping > /bin/ping6 > > Not having /bin/su suid root is probably Rick's problem. > Thanks,

Re: su and administrator password fails in gnome

On Jan 3, 9:40 am, Ron Johnson <[EMAIL PROTECTED]> wrote: > No, just not noticing rws amongst all the rwx's. Use ls --color, and they jump out at you. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: su and administrator password fails in gnome

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/03/08 02:07, Sven Joachim wrote: > On 2008-01-03 05:07 +0100, Ron Johnson wrote: > >> On my system, all the non-symlinks in /bin are 755 root:root. > > Then your system is rather unusual, to say the least. The following > programs are 1755 on

Re: su and administrator password fails in gnome

On 2008-01-03 05:07 +0100, Ron Johnson wrote: > On my system, all the non-symlinks in /bin are 755 root:root. Then your system is rather unusual, to say the least. The following programs are 1755 on my system: /bin/su /bin/mount /bin/umount /bin/ping /bin/ping6 Not having /bin/su suid root is

Re: su and administrator password fails in gnome

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/02/08 21:28, Rick Dooling wrote: > Plot thickens. Not a sudoer problem, probably. > > Examining bash history, I mistakenly chowned /bin (instead of ~/bin) > to my username. I chowned it back to root, but I must have messed up > permissions the s

Re: su and administrator password fails in gnome

Plot thickens. Not a sudoer problem, probably. Examining bash history, I mistakenly chowned /bin (instead of ~/bin) to my username. I chowned it back to root, but I must have messed up permissions the setuid programs. I'll figure it out when I get back on that machine tomorrow. Thanks, rick -

Re: su and administrator password fails in gnome

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/02/08 16:39, Rick Dooling wrote: > Here's a weird one. > > On a new installation of Etch, I edited sudoers to give root > priveleges to myself (user rick). > > Suddenly when gnome asks for my administrator password or when I try > to do "su" it

Re: SU error

Jake & Betty Kraayenbrink wrote: I installed debian from the live knoppix CD it’s version 5.1. It works great, but I do have trouble when I try to run any thing that needs administrator privileges. When I click on something say to configure my printer I get this message “Su returned with an e

Re: SU error

On Sat, 19 May 2007, Jake & Betty Kraayenbrink wrote: I installed debian from the live knoppix CD it's version 5.1. It works great, but I do have trouble when I try to run any thing that needs administrator privileges. When I click on something say to configure my printer I get this message "Su

Re: SU error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/18/07 23:23, Jake & Betty Kraayenbrink wrote: > I installed debian from the live knoppix CD it’s version 5.1. It works > great, but I do have trouble when I try to run any thing that needs > administrator privileges. When I click on something say

Re: su and X question

On Fri, Apr 14, 2006 at 10:05:23AM +0200, Chris wrote: [...] > > Thanks for your suggestion. I do mostly use vi in console as root, but I'm > not a programmer, and I've never figured out how to move or copy blocks of > text in vi. I took a posters advice an installed sux which allows me to us

Re: su and X question

On Fri, 14 Apr 2006 10:05:23 +0200 Chris <[EMAIL PROTECTED]> wrote: > On Thursday 13 April 2006 06:07, Paul Johnson wrote: > > On Wednesday 12 April 2006 09:49, Chris wrote: > > > Hello, > > > > > > Hi I'd like to open X-applications like the in the example below from an > > > su Terminal, but get

Re: su and X question

On Thursday 13 April 2006 06:07, Paul Johnson wrote: > On Wednesday 12 April 2006 09:49, Chris wrote: > > Hello, > > > > Hi I'd like to open X-applications like the in the example below from an > > su Terminal, but get an Xlib connection error. I have set up sudo so > > that: sudo kwrite /etc/fsta

Re: su and X question

On 2006-04-12 15:00:31 -0400, Luis Finotti wrote: > Zen Garden wrote: > > user$ xhost + (press enter) > [snip] > > This seems to be a security risk... Yes. > "sux" seems to be a better idea... (Or so I heard.) :-) Or define $XAUTHORITY. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web:

Re: su and X question

On Wed, Apr 12, 2006 at 09:06:45PM -0700, Paul Johnson wrote: > Try sudo instead, and better to use the simplest software possible when > running as root... there are plenty of console editors, I suggest one of > those as your editor while root. There's also sudoedit(1), which invokes your edito

Re: su and X question

On Wednesday 12 April 2006 09:49, Chris wrote: > Hello, > > Hi I'd like to open X-applications like the in the example below from an su > Terminal, but get an Xlib connection error. I have set up sudo so that: > sudo kwrite /etc/fstab works, but how come it doesn't in a normal su > Terminal? Try

Re: su and X question

Thanks, I'll look into sux On Wednesday 12 April 2006 19:14, Casey T. Deccio wrote: > On Wed, 2006-04-12 at 18:49 +0200, Chris wrote: > > Hello, > > > > Hi I'd like to open X-applications like the in the example below from an > > su Terminal, but get an Xlib connection error. I have set up su

Re: su and X question

Zen Garden wrote: > I used to have te same problem. It is because root cannot access to the > X server. > Here the sollution: > > user$ xhost + (press enter) [snip] This seems to be a security risk... "sux" seems to be a better idea... (Or so I heard.) :-) HTH, Luis -- To UNSUBSCRIBE, ema

Re: su and X question

I used to have te same problem. It is because root cannot access to the X server.Here the sollution:user$ xhost + (press enter)And then:user$ su (without the "-") (press enter)password: (type your root password) root#Now you can launch windows from shell as root.Ciao!Matías.- On 4/12/06, Chris < [E

Re: su and X question

On Wed, 2006-04-12 at 18:49 +0200, Chris wrote: > Hello, > > Hi I'd like to open X-applications like the in the example below from an su > Terminal, but get an Xlib connection error. I have set up sudo so that: sudo > kwrite /etc/fstab works, but how come it doesn't in a normal su Terminal? >

Re: Re: su/sudo cannot X

On Wed, Jan 18, 2006 at 10:15:57PM -0500, [EMAIL PROTECTED] wrote: > I've been told that if a process has a window on an X server, it can > create fake events on any of the windows on the X server. This was, > ages ago, a building block for various nice user interfaces, decades > before anybody

Re: su/sudo cannot X

On Wed, Jan 18, 2006 at 10:53:01AM -0500, Peter McAlpine wrote: > Thanks, but I'm also interested in hearing how to disable all access > control for remote connections. How can I do this? Possibly by asking in your own thread: hijacking this one makes for some very confusing reading. -- Jon Dowl

Re: su/sudo cannot X

On Tue, 17 Jan 2006 17:29:35 -0500 Lei Kong <[EMAIL PROTECTED]> wrote: > I have a strange problem with my thinkpad z60t, running debian testing. > I ran these commands in konsole or xterm under kde: > > $xhost + > $ sudo -s > #kedit > kedit: cannot connect to X server > > What is wrong? If you

Re: Re: su/sudo cannot X

John Hasler wrote X and X applications are exceedingly complex, unaudited, and likely to be chock full of buffer overruns, format string vulnerabilities, and other I guess a checking on CERT's vulnerability list will reveal if this is true, X vs non-X. nasties. Consider the segfaults and m

Re: su/sudo cannot X

Le Mercredi 18 Janvier 2006 16:53, Peter McAlpine a écrit : > On Wed, Jan 18, 2006 at 03:37:25PM +, Noah Dain wrote: > > On 1/18/06, Peter McAlpine <[EMAIL PROTECTED]> wrote: > > > Security feature or not... when I'm troubleshooting I sometimes want > > > this disabled. If 'xhost +' no longer d

Re: su/sudo cannot X

I wrote: > Because neither X nor any X applications are secure. Lei writes: > True, root X session over network is insecure... True, but not what I meant. > What is the security concern for local root X session? X and X applications are exceedingly complex, unaudited, and likely to be chock ful

Re: Re: su/sudo cannot X

As about the security concern, why is it more secure not to let root log into X than otherwise? why is not letting root start X client after su/sudo by default a good policy? Because neither X nor any X applications are secure. True, root X session over network is insecure, but how about us

Re: su/sudo cannot X

Lei Kong wrote: > As about the security concern, why is it more secure not to let root log > into X than otherwise? why is not letting root start X client after > su/sudo by default a good policy? Because neither X nor any X applications are secure. -- John Hasler -- To UNSUBSCRIBE, email to [

Re: Re: su/sudo cannot X

On Wed, Jan 18, 2006 at 08:55:58PM -0500, Lei Kong wrote: > thanks, sux works beautifully. > but still I don't understand why sudo -s has problems, > and on my desktop, on problem at all, and I don't remember > doing special thing on it. > > As about the security concern, why is it more secure not

Re: Re: su/sudo cannot X

On Wed, 2006-01-18 at 20:55 -0500, Lei Kong wrote: > thanks, sux works beautifully. > but still I don't understand why sudo -s has problems, > and on my desktop, on problem at all, and I don't remember > doing special thing on it. > > As about the security concern, why is it more secure not to > l

Re: Re: su/sudo cannot X

$xhost + $ sudo -s #kedit kedit: cannot connect to X server Leave off the xhost line when using sudo. It inheirets the parent shell's environment. I did try it without xhost+ first, didn't work. The inherit thing is default, or I need to configure it? On my desktop, sudo -s does allow

Re: Re: su/sudo cannot X

thanks, sux works beautifully. but still I don't understand why sudo -s has problems, and on my desktop, on problem at all, and I don't remember doing special thing on it. As about the security concern, why is it more secure not to let root log into X than otherwise? why is not letting root start

  1   2   3   >