Search results

I created a new user following the digitalocean tutorial you sent with the same result.

Does it ssh in and then run the command or does it ssh in and run the command at the same time like I've been doing in the examples I've sent?

Adding the user to the wheel group resulted in the same sudo: no tty present and no askpass program specified as the sudo rules

I don't know if it would count as a feature request to allow NOPASSWD: support for unprivileged users to run commands via sudo, but if you were looking for features to add, there's at least one organization that would appreciate that one :)

I get these results depending on which sudo option I have: fwcloudapi ALL=(root) NOPASSWD: /usr/sbin/ip * This one works when I do ssh fwcloudapi@mysystem sudo ip address show. It asks me for my password for the login, but not for the sudo command. fwcloudapi ALL=(root) NOPASSWD: /usr/sbin/ip...

Is there a way to configure FWCloud to use the password to connect via SSH and then run the sudo command without waiting for a password prompt?

The -t flag works when I do it manually, but I am unsure how to configure that within FWCloud. root@myothersystem ~ $ ssh -t fwcloudapi@mysystem sudo ip address show fwcloudapi@mysystem's password: [sudo] password for fwcloudapi: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state...

I do not believe my organization's security team would allow such access, sorry.

I might be on to something: root@myothersystem ~ $ ssh fwcloudapi@mysystem sudo ip address show fwcloudapi@mysystem's password: sudo: no tty present and no askpass program specified This error was not present until I enabled asking for password with the sudo command. It wouldn't have bugged...

Thank you for all your help, Carles. I appreciate it a lot.

Previously I had sudo run with no password, but requiring a password for sudo didn't help. ~ » ssh fwcloudapi@mysytem fwcloudapi@mysytem's password: Last login: Wed Apr 28 13:13:04 2021 from myothersytem [fwcloudapi@mysytem ~]$ sudo ip a [sudo] password for fwcloudapi: 1: lo...

[pengels@myothersystem]~% ssh fwcloudapi@mysystem sudo /sbin/ip address show fwcloudapi@mysystem's password: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo...

I've added a sudo rule that allows any command with "sudo ip" such as "sudo ip a" or "sudo ip addr sh". I've also tried using an LDAP user instead of a local user without any luck. Thank you for all your patience so far.

Note that the "myothersystem" machine is the one with fwcloud installed on it.

I've verified that sudo ip a works with the user and that the user can log in to the system. fwclouduserthing@mysystem's password: Last login: Wed Apr 28 12:27:29 2021 from myothersystem [fwclouduserthing@mysystem ~]$ sudo ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN...

It worked running as root, though. I DEFINITELY don't want to use the root account for this sort of thing. Do you know what commands the UI is sending along the SSH session?

Same result running it as a user that can sudo anything without a password.

Yup! Sameip a result with the user am connecting as. The only line that results from trying the discovery is this: 2021-04-28 11:30:13|ERROR|Error getting network interface information: {}

root@mysystem ~ $ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: eth0...

Hello! I'm trying to get the "Discover Interfaces" tool working. I provided the correct address and username and password, and I can verify that a session was opened for that user. Does the user need to be an admin? Does this depend on networkmanager? Right now, my machine is configured...