search for: requiretti

I've got a Cento 6.2 server I'm putting together that will become a mailserver. It will have on it MailScanner and MailWatch for MailScanner. I'm using the latest stuff available and have run into a problem with changes I need to make in the /etc/sudoers file. It doesn't seem to take affect after I make the changes, so either the syntax within the file has changed or the way

Thanks for the responses. I think this is what I want to do. I commented out #Defaults requiretty in /etc/sudo. But what I really wanted to do was just place it in VPNUSERS: %vpnusers ALL=NOPASSWD: /sbin/service myciscovpn start, \ /sbin/service myciscovpn stop, \ /sbin/service myciscovpn status, \ /usr/bin/mycisco,

I need to remove empty files out of a directory that are over 6 hours old so I created this script and put it in cron.hourly. #!/bin/sh cd /var/list sudo -u matt find /var/list -mmin +360 -empty -user matt -exec rm {} \; I want to run it as matt rather than root for just an added bit of safety. Problem is I get this. "sudo: sorry, you must have a tty to run sudo" Is there another

Hi, I was previously using an EC2 AMI where i was logging as root, and i could bootstrap nodes. I am now using Amazon AMIs ( http://aws.amazon.com/fr/amazon-linux-ami ) and they require login as ec2-user. The problem is that if i run puppet node bootstrap --login ec2-user, it will detect it and run my install script as with sudo, which is fine, but sudo will not run it because it is configured by

> > What does the sudo log say? This is all the secure logs say about the ssh session: [root at logs:~] #tail -f /var/log/secure Oct 31 19:15:20 logs sshd[24407]: Accepted publickey for bluethundr from 47.18.111.100 port 47469 ssh2: RSA ae:62:1f:de:54:89:af:2c:10:16:0e:fd:8d:7e:81:06 Oct 31 19:15:21 logs sshd[24407]: pam_unix(sshd:session): session opened for user bluethundr by (uid=0)

Hi all, I need to restart a service on a few elasticsearch nodes. I'm trying to do it with pssh. I'm getting this error when I try to do that: pssh -h es_list "/bin/sudo -S /bin/systemctl restart elasticsearch" [1] 17:01:50 [FAILURE] bluethundr at es2.example.com Exited with error code 1 [2] 17:01:51 [FAILURE] bluethundr at es3.example.com Exited with error code 1 [3]

Hello, I used Lingon for Leopard Server to create a launchd job that would execute the following rsync (v3.0.4) command when logged in as admin at 12:01 AM each day. sudo rsync -aAHvWX /Volumes/File_Storage/docs/ /Volumes/File_Storage_Mirror/docs When launchd executed this command, it did not work. The system.log file reads "Exited with exit code: 1". It called it at 12:01 AM,

Greetings All- I'm about to embark on some remote management testing and need a way to login to a remote system running CentOS 4.x/5.x via SSH, su to root (using a password), then execute a command. I currently login to the boxes using key based SSH like this: ssh -i ~/remote_key admin@$REMOTEIP Then, I SU to root. However, if I try to do this automatically like this: ssh -i ~/remote_key

Hi... Im problem is this, i have a asterisk server (FC8 - kernel 2.6.24) a the asterisk version is 1.4.18. If in the machine is all ok, i can stop start the asterisk service no prob, my problem is when in another server (in my case, debian etch 4) using the ssh the stop service is ok, but the start service dosend finalise. Like this: ssh etx9 'sudo /etc/init.d/asterisk stop' operacao at

Everyone, I am working on a Centos 5.9 system. I have an need to be able to activate a piece of software from /etc/smrsh that is activated when sendmail delivers the e-mail to this piece of software. I would like this piece of software to take on the user and group identities that are different than 'mail' which is what happens now. I want to use a user and group that is not root), so

On Thu, February 12, 2015 12:32 pm, Matt wrote: > I need to remove empty files out of a directory that are over 6 hours > old so I created this script and put it in cron.hourly. > > #!/bin/sh > cd /var/list > sudo -u matt find /var/list -mmin +360 -empty -user matt -exec rm {} \; > > I want to run it as matt rather than root for just an added bit of > safety. Problem is

On Thu, Feb 12, 2015 at 12:32:12PM -0600, Matt wrote: > I need to remove empty files out of a directory that are over 6 hours > old so I created this script and put it in cron.hourly. For what it's worth, we no longer have requiretty in the package in Fedora, so eventually that change will probably make it down to CentOS. Overall, security benefit vanishingly small and inconvenience

On 10/31/2015 02:04 PM, Tim Dunphy wrote: > pssh -h es_list "/bin/sudo -S /bin/systemctl restart elasticsearch" The default configuration prohibits use if input echo can't be disabled. That means no "-S". I modify that for users where necessary: /etc/sudoers.d/myuser: Defaults:myuser !requiretty, visiblepw

On 10/31/2015 04:16 PM, Tim Dunphy wrote: > Got the same exact message! > > Anything else I can try? I think you need to double-check your sudoers file. Use the '-i' argument to pssh to get more information. # cat /etc/sudoers.d/gordon gordon ALL=(ALL) NOPASSWD: ALL $ pssh -h t -i sudo echo true [1] 16:02:12 [FAILURE] MYHOST Exited with error code 1 Stderr: sudo: sorry,

Hello I need to know a way to have scp allocate a tty on a remote machine so I can have it run sudo and activate a vpn which it will need to activate. scp with "-S" does not work. I can't chmod +s the cisco vpn client because when I try to run it it says it can not have setuser. I could have the user scp via root but I do not want to do that. Any way to have scp allocate a tty?

Hey Gordon, Sorry, man my bad! Disabling the tty requirement for my sudo user does indeed work. I had a type-o in the sudoers file, and when I corrected it, my sudo command via pssh started working! #pssh -i -h es_list "/bin/sudo /bin/systemctl restart elasticsearch; sleep 10" [1] 20:31:32 [SUCCESS] bluethundr at es3.jokefire.com Stderr: sudo: sorry, you must have a tty to run sudo

We've been using rsync since forever to back up all our servers and it's worked without a problem. But in a recent security review, we noted that our specific rsync backup host is using root keys to access the server, meaning that if the keys on the backup server were leaked/compromised in any fashion, that would provide r00t access to the servers being backed up. Since this

Hi, OpenSSH 5.4 is almost ready for release, so we would appreciate testing on as many platforms and systems as possible. This is a big release, with a number of major new features and many bug fixes. Snapshot releases for portable OpenSSH are available from http://www.mindrot.org/openssh_snap/ The OpenBSD version is available in CVS HEAD: http://www.openbsd.org/anoncvs.html Portable OpenSSH