Hi all,
I configured sudo in order to use LDAP and set the corrisponding defaults on
the DIT set to ignore_local_sudoers.
After populating the DIT with the rules, sudo works perfectly but I have a
problem with the list options of sudo (-l).
It seems like sudo -l for NORMAL users (i.e. not root
On Monday 01 March 2010 00:57:17 William Hubbs wrote:
> On Mon, Mar 01, 2010 at 12:16:14AM +0200, Alan McKinnon wrote:
> > "sudo su" and "su" have a fundamental difference, vital in corporate
> > networks:
> >
> > The former uses the use
On Sat, 30 Jun 2012 21:55:27 -0500, Alecks Gates wrote:
> Did you use it interactively? It should look like this:
> alecks@linux:~$ sudo -i
> root@linux: ~# echo "sys-boot/grub:2 **" >>
> /etc/portage/package.accept_keywords/package.keywords.grub2
>
> Just t
I'm noticing a problem using sudo where the builtin cd command is not
known under sudo.
User attempts to `ls dir', receives `permission denied' ( its a root
owned dir)
User uses `sudo ls dir', and is queried for password, sudo then prints the
ls display when password is su
Harry Putnam wrote:
> I'm noticing a problem using sudo where the builtin cd command is not
> known under sudo.
>
> User attempts to `ls dir', receives `permission denied' ( its a root
> owned dir)
>
> User uses `sudo ls dir', and is queried for passwor
On Mon, Mar 01, 2010 at 12:16:14AM +0200, Alan McKinnon wrote:
> "sudo su" and "su" have a fundamental difference, vital in corporate networks:
>
> The former uses the user's password for authentication and sudoers for
> authorization. The latter us
On a recent update, `sudo` got upgraded from sudo-1.9.6_p1-r2 to
sudo-1.9.8_p2. Since then, any call to `sudo` other than `sudo --help`
resulted in a Segmentation Fault. I have tried remerging sudo again or
remerging the PAM-related dependencies, but it did not help. Switching
back to 1.9.6
On Sunday 28 February 2010 23:27:57 William Hubbs wrote:
> > 7 years ago a veteran Linux user taught me to always use su - for the
> > very reason you stated.
>
>
> Actually, you are safe with either "su -" (without sudo) or "sudo -i".
> "sud
Neil Bothwick wrote:
> On Sun, 28 Feb 2010 13:06:43 +0800, ubiquitous1980 wrote:
>
>
>>> Some ENV variables are unset by sudo.
>>>
>
> You can alter that behaviour in /etc/sudoers. I have
>
> Defaults:%wheel !env_reset
>
> and don't see
JimD schreef:
> I have been using Linux for a number of years and the one "trick" I
> have never read how to do is something like:
>
> sudo echo "app-portage/porthole ~*" >> /etc/portage/package.keywords
Well this one I do with a set of revised comm
On Sun, 28 Feb 2010 13:06:43 +0800, ubiquitous1980 wrote:
> > Some ENV variables are unset by sudo.
You can alter that behaviour in /etc/sudoers. I have
Defaults:%wheel !env_reset
and don't see this.
> > But anyway, "sudo su" makes zero sense :P
> sudo su make
On 2021.11.09 15:36, Anton wrote:
On a recent update, `sudo` got upgraded from sudo-1.9.6_p1-r2 to
sudo-1.9.8_p2. Since then, any call to `sudo` other than `sudo
--help` resulted in a Segmentation Fault. I have tried remerging sudo
again or remerging the PAM-related dependencies, but it did
On 3/23/06, Holly Bostick <[EMAIL PROTECTED]> wrote:
> JimD schreef:
> > I have been using Linux for a number of years and the one "trick" I
> > have never read how to do is something like:
> >
> > sudo echo "app-portage/porthole ~*" >>
On 2021-11-09 22:36+0200 Anton wrote:
> On a recent update, `sudo` got upgraded from sudo-1.9.6_p1-r2 to
> sudo-1.9.8_p2. Since then, any call to `sudo` other than `sudo
> --help` resulted in a Segmentation Fault. I have tried remerging sudo
> again or remerging the PAM-related
Hi all,
And recent upgrade sudo-1.6.8_p9 make sudo with password inpossible.
After update sudo to the mentioned version, I get the problem and fixed
by FAQ section in
http://www.courtesan.com/sudo/troubleshooting.html
Q) Sudo says 'Account expired or PAM config lacks an &qu
On Wed, Sep 14, 2005 at 05:45:08PM +0200, Holly Bostick wrote:
> OK, you're right. I think that the problems that I was working around
> may have been based in *sudo*, not su itself, which works fine (now), as
> does sudo su. But when I was setting up my system with sudo (like a
>
On 04/18/10 11:02, Jonathan wrote:
> On Sun, 18 Apr 2010 08:29:37 +1000
> Lie Ryan wrote:
>
>> sudoedit is mainly just a shortcut for "sudo $EDITOR" (plus doing a
>> few things).
>
> sudoedit is safer then sudo because sudoedit runs as root but nano
> (T
On Sunday 29 May 2005 04:42 pm, Pupeno <[EMAIL PROTECTED]> wrote:
> On Sunday 29 May 2005 16:53, Boyd Stephen Smith Jr. wrote:
> > I never use rsync myself, but why not just use --rsh="ssh 'su -'"
> > instead of --rsh="ssh"?
>
> It'd
Neil Bothwick wrote:
> On Sun, 28 Feb 2010 18:48:56 +0800, ubiquitous1980 wrote:
>
>
>>> The root account is hardly locked if you can log into it with sudo su
>>> (or sudo screen) but sudo -s or sudo -i make more sense in this
>>> situation.
>>&
Le lun. 21 janv. 2019 à 19:04, Nikos Chantziaras a
écrit :
>
> I can't see why "emerge -uv bash" would ever invoke sudo. So I'd say
> that you should first find out what command is being executed with sudo.
> To do that, try to emerge bash, and when the sudo pro
ser, like maybe some little kid, getting root access for any
> > reason.
>
> No, it's pretty standard across Unix.
>
> The BSD's for example have had it since forever - members of the wheel
> group
> being allowed to sudo anything only came along much later.
>
&
On Mon, Aug 09, 2010 at 05:30:40PM -0700, Kevin O'Gorman wrote:
> On Mon, Aug 9, 2010 at 1:20 PM, Bill Longman wrote:
>
> > On 08/09/2010 01:08 PM, Robert Bridge wrote:
> > > On Mon, Aug 9, 2010 at 8:09 PM, Mick wrote:
> > >> There have been discussions o
I have use your method , it didn't work .
Like:
sudo echo "sys-boot/grub:2 **" >>
/etc/portage/package.accept_keywords/package.keywords.grub2 echo
"sys-boot/grub:2 **" | sudo tee
/etc/portage/package.accept_keywords/package.keywords.grub2
And the result :
zjhu
; >> Best regards,
> > > >> Yann
> > >
> > > I think that is a Gentoo thing. It does add some security if you don't
> > > want a user, like maybe some little kid, getting root access for any
> > > reason.
> >
> > No, it'
On Sun, Jul 01, 2012 at 10:41:12AM +0800, Penguin Lover 赵佳晖 squawked:
> I have use your method , it didn't work .
> Like:
> sudo echo "sys-boot/grub:2 **" >>
> /etc/portage/package.accept_keywords/package.keywords.grub2 echo
> "sys-boot/grub:2 **" | s
I was wrong. Sorry.
I realize now that this cannot be your problem, sudo tell you that it
is not setuid if it's not.
$ sudo chmod -s sudo
$ sudo ls
sudo: must be setuid root
>
> Thanks Christer, never saw that command before, but
> like I told Walter, a listing for sudo is
On 3/23/06, JimD <[EMAIL PROTECTED]> wrote:
> I have been using Linux for a number of years and the one "trick" I
> have never read how to do is something like:
>
> sudo echo "app-portage/porthole ~*" >> /etc/portage/package.keywords
if you do this,
On 2005-04-08 08:06:47 -0400, Bill Roberts wrote:
> $ sudo echo something >> /etc/portage/package.keywords
> -/bin/bash: /etc/portage/package.keywords: Permission denied
Chris already gave one solution, but I can explain the problem. In
your original command, the redirection is happe
Le Sat, 30 Jun 2012 19:48:28 +0100,
Neil Bothwick a écrit :
> On Sun, 1 Jul 2012 01:27:49 +0800, 赵佳晖 wrote:
>
> > In some cases , when i run somethings with "sudo" , it tells me
> > "Permission Denied" , then i should turn to root . i forgot to
> > r
rt my network?
>
>
Obviously the answers depends completely on how you are managing
services and what executables you have on your highly customizable
Gentoo machine, but possibly:
sudo service network-manager restart
sudo systemctl restart NetworkManager.service
sudo nmcli networking of
Harry Putnam wrote:
sudo cd dir
sudo: cd: command not found
sudo will execute its arguments. 'cd' can't be executed, it is a shell
builtin.
Try:
$ sudo bash -c "cd dir; do_what_you like"
Christoph
--
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..
you
> don't
> > > > want a user, like maybe some little kid, getting root access for any
> > > > reason.
> > >
> > > No, it's pretty standard across Unix.
> > >
> > > The BSD's for example have had it since forever - members
Oh,yes , i misunderstand it . Thank you
2012/7/3 Willie WY Wong
> On Sun, Jul 01, 2012 at 10:41:12AM +0800, Penguin Lover 赵佳晖 squawked:
> > I have use your method , it didn't work .
> > Like:
> > sudo echo "sys-boot/grub:2 **" >>
> > /etc/portag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/08/2010, at 11:44 AM, Frank Steinmetzger wrote:
> Am Dienstag, 10. August 2010 schrieb Paul Hartman:
>
>> Typing that long password into sudo every time I ran a command was a
>> hassle
>
> I’ve never used sudo, an
:
> Hi all,
> And recent upgrade sudo-1.6.8_p9 make sudo with password inpossible.
>
> After update sudo to the mentioned version, I get the problem and fixed
> by FAQ section in
>
> http://www.courtesan.com/sudo/troubleshooting.html
>
> Q) Sudo says 'Acc
On Sun, Feb 28, 2010 at 03:56:13PM -0500, stosss wrote:
> On Sun, Feb 28, 2010 at 7:28 AM, pk wrote:
> > ubiquitous1980 wrote:
> >
> >>> http://lists.debian.org/debian-security/2006/07/msg00059.html
> >
> >> With "sudo su - " the man pages do n
On 4/6/2014 06:44, Nikos Chantziaras wrote:
> I have a problem where commands preceded by "sudo" are not always
> auto-completed. This happens with executables that don't have user
> execute permission. For example, net-analyzer/tcptraceroute installs
> this binary:
&g
staticsafe wrote:
On 4/6/2014 06:44, Nikos Chantziaras wrote:
I have a problem where commands preceded by "sudo" are not always
auto-completed. This happens with executables that don't have user
execute permission. For example, net-analyzer/tcptraceroute installs
this binary:
thing change here?
What do I need to do to restart my network?
Obviously the answers depends completely on how you are managing
services and what executables you have on your highly customizable
Gentoo machine, but possibly:
sudo service network-manager restart
sudo systemctl re
I have created an issue at their Git repository. Maybe there will be
solution for this:
https://github.com/sudo-project/sudo/issues/190
-Ramon
On 26/10/2022 21:28, Grant Taylor wrote:
On 10/26/22 12:22 PM, Neil Bothwick wrote:
You need to be root to write to /etc/sudoers.d. If someone
On 08:51 Fri 08 Apr , Daniel Westermann-Clark wrote:
> On 2005-04-08 08:06:47 -0400, Bill Roberts wrote:
> > $ sudo echo something >> /etc/portage/package.keywords
> > -/bin/bash: /etc/portage/package.keywords: Permission denied
>
> Chris already gave one solu
ug 9, 2010 at 8:09 PM, Mick
wrote:
> > > >> There have been discussions on this list why sudo is a bad idea and
> > > >> sudo
> > >
> > > on
> > >
> > > >> *any* command is an even worse idea. You might as well be running
> > >
On 21/01/2019 20:25, Jacques Montier wrote:
Le lun. 21 janv. 2019 à 19:04, Nikos Chantziaras <mailto:rea...@gmail.com>> a écrit :
I can't see why "emerge -uv bash" would ever invoke sudo. So I'd say
that you should first find out what command is being exec
On Sun, Mar 22, 2015 at 03:30:49AM -0400, German wrote
> Thanks, I decide to go with sudo on this one. However when I try
> to run it, it says: "Username is not in the sudoers file." Where is
> this file located and how can I add the user to it? Thanks
Here's how it
lete"
echo "press to chroot into gentoo environment."
read
sudo mount /dev/sda3 /mnt/gentoo
sudo mount /dev/sda1 /mnt/gentoo/efi
sudo swapon /dev/sda2
sudo cp --dereference /etc/resolv.conf /mnt/gentoo/etc
sudo mount --types proc /proc /mnt/gentoo/proc
sudo mount --rbind /sys /
Holly Bostick wrote:
> JimD schreef:
>> I have been using Linux for a number of years and the one "trick" I
>> have never read how to do is something like:
>>
>> sudo echo "app-portage/porthole ~*" >> /etc/portage/package.keywords
>
> W
On Sun, 17 Apr 2016 20:02:54 +0200
Ralf wrote:
> ... What about aliasing emerge to sudo emerge? :-)
Because sometimes I want to use sudo with emerge and sometimes not. I
do have sudo-included aliases for a couple of the more common cases,
alias upworld='sudo emerge -auvD --changed-us
On Wed, 2005-07-06 at 15:52 +0200, Holly Bostick wrote:
> Echo is in the sudo-ed group, and echo isn't the problem-- the problem
> is that permission is refused to write to the file itself (which is an
> error *from* echo, so it would seem that echo itself is OK as far as
> sudo g
Boyd Stephen Smith Jr. wrote:
>
> You want:
> sudo "echo 'media-video/xine-ui ~x86' >> /etc/portage/package.keywords"
>
No, I'm sorry, this is completely false.
Running
sudo "echo 'media-video/xine-ui ~x86' >> /etc/portage
On Thursday 23 March 2006 16:33, JimD <[EMAIL PROTECTED]> wrote
about 'Re: [gentoo-user] sudo echo':
> If you type something like the following:
>
> "> /tmp/myfile.foo"
>
> It will truncate the file. I use it when I want to clear out logs real
> qu
On Sunday 28 February 2010 07:06:43 ubiquitous1980 wrote:
> Nikos Chantziaras wrote:
> > On 02/28/2010 05:57 AM, ubiquitous1980 wrote:
> >> If I have logged in through sudo such as $ sudo su, when I then use man
> >> pages, they are covered in "ESC".
On Sun, 28 Feb 2010 18:48:56 +0800, ubiquitous1980 wrote:
> > The root account is hardly locked if you can log into it with sudo su
> > (or sudo screen) but sudo -s or sudo -i make more sense in this
> > situation.
> localhost ubiquitous1980 # passwd -l root
> Passw
"Walter Dnes" <[EMAIL PROTECTED]> writes:
> On Wed, May 23, 2007 at 06:14:53PM -0700, maxim wexler wrote
>> Hi group,
>>
>> I connect to the web using
>>
>> $sudo /usr/sbin/pon
>>
>> on one machine(2.6.20-gentoo-r6). On another
Eric Martin wrote:
> Tim wrote:
>> Tonight, for no apparent reason, a problem has started cropping up when
>> I 'sudo su'. The root shell will start up fine, but after the first time
>> I hit a key, the shell terminates - apparently normally. A sample try
>
echo "once disk setup from gentoo handbook is complete"
> echo "press to chroot into gentoo environment."
> read
> sudo mount /dev/sda3 /mnt/gentoo
> sudo mount /dev/sda1 /mnt/gentoo/efi
> sudo swapon /dev/sda2
> sudo cp --dereference /etc/resolv.conf /mnt/ge
On 02/28/2010 05:57 AM, ubiquitous1980 wrote:
If I have logged in through sudo such as $ sudo su, when I then use man
pages, they are covered in "ESC". This does not occur when using normal
user accounts or the root account through su. Wondering what is going
on. Thanks.
Some ENV
On 09/25/10 01:35:16, Nikos Chantziaras wrote:
...
>
> But if some reason you want sudo, /etc/sudoers has some info:
>
>## Run X applications through sudo
>
> Read the comments there and uncomment what suits you. Did I mention
> that you should use kdesu instea
Edward Catmur schreef:
> On Wed, 2005-07-06 at 15:52 +0200, Holly Bostick wrote:
>
>>Echo is in the sudo-ed group, and echo isn't the problem-- the problem
>>is that permission is refused to write to the file itself (which is an
>>error *from* echo, so it would seem
Nikos Chantziaras wrote:
> On 02/28/2010 05:57 AM, ubiquitous1980 wrote:
>> If I have logged in through sudo such as $ sudo su, when I then use man
>> pages, they are covered in "ESC". This does not occur when using normal
>> user accounts or the root account throu
JimD wrote:
> I have been using Linux for a number of years and the one "trick" I
> have never read how to do is something like:
>
> sudo echo "app-portage/porthole ~*" >> /etc/portage/package.keywords
echo whatnot | sudo sh -c ">> foo"
If
On Thu, 23 Mar 2006 16:03:08 -0500
JimD wrote:
> I have been using Linux for a number of years and the one "trick" I
> have never read how to do is something like:
>
> sudo echo "app-portage/porthole ~*" >> /etc/portage/package.keywords
>
> Another o
On 06/04/14 18:58, staticsafe wrote:
On 4/6/2014 06:44, Nikos Chantziaras wrote:
I have a problem where commands preceded by "sudo" are not always
auto-completed. This happens with executables that don't have user
execute permission. For example, net-analyzer/tcptraceroute insta
pk wrote:
> ubiquitous1980 wrote:
>
>> If I have logged in through sudo such as $ sudo su, when I then use man
>> pages, they are covered in "ESC". This does not occur when using normal
>> user accounts or the root account through su. Wondering what is g
On Wed, April 5, 2006 8:06 pm, Grant wrote:
>
> I actually tried that first and when that failed I tried something
> like that specified here:
>
> www.gentoo.org/doc/en/sudo-guide.xml
>
> Either way I get:
>
> [EMAIL PROTECTED] ~ $ /sbin/shutdown -h now shutdown: you
Hello,
On Tue, 15 Oct 2019, Mick wrote:
>I have very limited sudo commands configured, but I better resync to see
>what's the latest stable sudo on the tree.
>
>https://www.engadget.com/2019/10/14/linux-unix-sudo-command-security-flaw/?
>guccounter=1
Yeah right, that
On 10/26/22 12:22 PM, Neil Bothwick wrote:
You need to be root to write to /etc/sudoers.d. If someone has that
access, you are already doomed!
And what happens if someone uses the existing root-via-sudo access to
break sudo?
You loose root-via-sudo access.
Someone could become root, via
Hi,
On Thu, 23 Mar 2006 16:03:08 -0500
JimD <[EMAIL PROTECTED]> wrote:
> I have been using Linux for a number of years and the one "trick" I
> have never read how to do is something like:
>
> sudo echo "app-portage/porthole ~*" >> /etc/portage/pac
chrome://messenger/locale/messengercompose/composeMsgs.properties:
Nikos Chantziaras wrote:
On 02/28/2010 05:57 AM, ubiquitous1980 wrote:
If I have logged in through sudo such as $ sudo su, when I then use man
pages, they are covered in "ESC". This does not occur when us
HI,
I have been using ubuntu for a while and have come to like sudo.
Now I am moving over to gentoo and would like to set this up as for me it is
far more convenient to just type sudo rather than the su business.
However when I emerge sudo, install and run it the following comes up
On Mon, Aug 9, 2010 at 6:18 PM, William Hubbs wrote:
> On Mon, Aug 09, 2010 at 05:30:40PM -0700, Kevin O'Gorman wrote:
> > On Mon, Aug 9, 2010 at 1:20 PM, Bill Longman
> wrote:
> > > I actually prefer "sudo su -" -- as long as I'm giving it away! :o)
&
Paul Melvin wrote:
HI,
I have been using ubuntu for a while and have come to like sudo.
Now I am moving over to gentoo and would like to set this up as for me
it is far more convenient to just type sudo rather than the su business.
However when I emerge sudo, install and run it
On Tuesday 10 August 2010 15:03:19 Kevin O'Gorman wrote:
> On Mon, Aug 9, 2010 at 6:18 PM, William Hubbs wrote:
> > On Mon, Aug 09, 2010 at 05:30:40PM -0700, Kevin O'Gorman wrote:
> > > On Mon, Aug 9, 2010 at 1:20 PM, Bill Longman
> >
> > wrote:
> >
Norberto Bensa schreef:
> Holly Bostick wrote:
>
>> you're using sudo. I find many anomolies in sudo;
>
>
> Why does people hate sudo so much?
>
Actually, I don't hate sudo at all; I use it all the time, and it saves
a lot of difficulty. I just get annoyed bec
I have very limited sudo commands configured, but I better resync to see
what's the latest stable sudo on the tree.
https://www.engadget.com/2019/10/14/linux-unix-sudo-command-security-flaw/?
guccounter=1
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
On Fri, 8 Apr 2005, Bill Roberts wrote:
> I've started using sudo in preference to su'ing, but I've found that
> "echo" doesn't seem to work with sudo.
>
> When I:
>
> $ sudo echo something >> /etc/portage/package.keywords
> -/bin/bash: /e
#x27;s a better way, I'm just too lazy to look for it...
>>
>
> Man, running "sudo visudo" and just running "visudo" is not the same.
> Be careful. Nano is hardcoded in sudo's ebuild.
>
>
OK, for the Nth time on this thread - it is all about *YOUR* c
"Nicolas Richard" writes:
> I don't understand where sudo finds the value for the PATH env
> variable.
Finally, I found where the problem lied. Recall that my problem was the
following : I had a path in `sudo env | grep ^PATH' which did not seem
to originate from
> Example:
>
> $ pwd
> /usr/bin
> $ ls -li sudo
> 8803772 ---s--x--x 2 root root 107240 2007-05-21
> 11:11 sudo*
> $ find . -inum 8803772
> ./sudo
> ./foo
> $ ls -li foo
> 8803772 ---s--x--x 2 root root 107240 2007-05-21
> 11:11 foo*
>
etc/init.d/net.enp1s0 link or other interesting candidate.
Do something change here?
What do I need to do to restart my network?
Obviously the answers depends completely on how you are managing
services and what executables you have on your highly customizable
Gentoo machine, but possibly:
su
Neil Bothwick wrote:
> On Fri, 24 Mar 2006 00:58:09 +0100, Renat Golubchyk wrote:
>
>> Alright, then run
>> sudo bash -c 'echo some_string >> some_file'
>> No problem here :)
>
> Except this means you have to give the user permission to run bash,
I've rebooted many times since.
I can login from ssh or console.
One odd behaviour:
[EMAIL PROTECTED] ~ $ sudo ifconfig
Password:
Password:
eth0 Link encap:Ethernet HWaddr 00:08:74:E0:5C:3B
inet addr:172.16.35.234 Bcast:172.16.63.255 Mask:255.255.224.0
...
Wh
On Thursday 23 March 2006 23:38, Renat Golubchyk wrote:
> On Thu, 23 Mar 2006 18:27:46 -0300 "Daniel da Veiga"
>
> <[EMAIL PROTECTED]> wrote:
> > Sudo takes a command as parameter, enclose the whole command in quotes
> > and try again, like this:
>
On Sat, May 28, 2005 at 09:47:20AM -0400, Mark Shields wrote
> Obviously, if you've never used sudo you'll have to emerge the package
> app-admin/sudo. Then, configure /etc/sudoers with the visudo command.
> Find #%wheel ALL=(ALL)ALL and uncomment it. Then, add the
I've not figured this out yet, so reposting in case someone has any ideas...
I did find this link:
http://www.mail-archive.com/openpkg-users@openpkg.org/msg01747.html
But I tried to add this:
authrequiredtry_first_pass
To my /etc/pam.d/sudo file and it didn't work
Holly Bostick wrote:
[EMAIL PROTECTED] schreef:
I think the problem come from the fact that echo is sudo-ed but the shell
redirection isn't.
Compare this:
su -c "echo foo > /etc/portage/whatever"
and
su -c "echo foo" > /etc/portage/whatever
The first one w
ples.
Huh?
The package you are talking about is sudo. Might I add that sudo follows the
grand time honoured tradition of the principle of least priviledge whereas su
does not?
su offers no means to selectively allow what a user may and may not be
authorised to do. It's an all or nothing ap
Hi everybody,
I don't understand where sudo finds the value for the PATH env variable.
Here is the output of the relevant (at least I thought they were)
commands. Can somebody explain to me why I still have
/usr/local/texlive/*2011*/bin/i386-linux in the first sudo output ? I
don't g
John Dangler wrote:
> I’m looking into setting up sudo on my latest test box
> (stage3/genkernel 2.6.12—r9)
>
> In portage, sudo says “Allows users or groups to run commands as other
> users”. The latest stable shows *1.6.8_p9 (although the one before is
> it unstable, and the
On 09/12/2018 12:24 AM, J. Roeleveld wrote:
Does sudo have a shell-mode?
You can use "-i" to invoke a shell, but that's just the target users
destination shell.
I prefer to use a utility (wrapper) that I wrote that allows me to
leverage sudo in my user shell without having
Le lun. 21 janv. 2019 à 21:38, Nikos Chantziaras a
écrit :
> On 21/01/2019 20:25, Jacques Montier wrote:
> > Le lun. 21 janv. 2019 à 19:04, Nikos Chantziaras > <mailto:rea...@gmail.com>> a écrit :
> >
> > I can't see why "emerge -uv bash" wou
On Wednesday 11 August 2010 18:58:02 Stroller wrote:
> On 10 Aug 2010, at 19:50, Alan McKinnon wrote:
> > ... The major threat by analysis on a workstation is stepping away
> > for a
> > leak and forgetting to lock the screen. sudo is adequate protection
> > against
>
On 09/23/2010 04:18 AM, Dale wrote:
Nikos Chantziaras wrote:
On 09/22/2010 09:48 PM, Andrey Vul wrote:
When I launch X programs via sudo, I get the following:
$sudo gui-admin
No protocol specified
gui-admin: cannot connect to X server :0
( Assume gui-admin is an X program )
But (gk|kde)su
; To: gentoo-user@lists.gentoo.org
> Subject: [gentoo-user] sudo requires password twice
>
> I recently did an update world and had that 'pam'/'shadow' issue.
> Followed these pages:
> http://planet.gentoo.org/developers/flameeyes/2006/03/19/the_s
> hadow_and_pam
Rainer,
using sudo does not makes you a root user. To become a root user you have to
switch with "su -" (and login with root password).
Sudo has its own configuration file. If you can do something with sudo on other
systems means there is a different configuration for sudo.
Check
c involved.
>
> Sebastian, I already fixed the problem for my local host. But I know
> other users have same problem. That's strange for me that you first
> login as root to use visudo program. What is the matter of having sudo
> then?
Maybe you should READ what people write BE
Holly Bostick wrote:
>>I don't just give myself blanket permissions to sudo to all commands; I
>>made a Cmd_Alias group which includes a lot of utility apps. And, like
>>many of you, I included emerge in this group.
>>
>
>Christoph Gysin schreef:
>
&g
On Tue, Dec 20, 2011 at 10:04 AM, Tanstaafl wrote:
> Hi all,
>
> I'm guessing this is a sudo question, but I'm unfamiliar with the nuances of
> sudo (never had to use it before).
>
> I have a new hosted VM server that I want to allow a user to be able to edit
> f
gentoo
> > environment to install the gentoo system. I started with stage3 and chose
> > openrc and went down that path.
> >
> > #!/usr/bin/bash
> > # file: sgentoo.sh - setup gentoo mounts
> > echo "once disk setup from gentoo handbook is complete"
&
On 10/26/22 12:31 AM, Walter Dnes wrote:
My regular user has script "settime" in ${HOME}/bin
#!/bin/bash
date
/usr/bin/sudo /usr/bin/rdate -nsv ca.pool.ntp.org
/usr/bin/sudo /sbin/hwclock --systohc
date
/etc/sudoers.d/001 has, amongst other things, two lines...
waltdnes x89
I've started using sudo in preference to su'ing, but I've found that
"echo" doesn't seem to work with sudo.
When I:
$ sudo echo something >> /etc/portage/package.keywords
-/bin/bash: /etc/portage/package.keywords: Permission denied
I look at
1 - 100 of 1938 matches
Mail list logo