
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-08-2010 07:12 PM
We have a domain environment where we are using Likewise Free for non-Windows domain workstation access (well, we are in testing right now). Likewise Free works really well with a few configuration changes to support what need the implementation to feel like!! The workstation in question (a MAC) is configured to allow the domain account of the local user and an administrative domain group for access. We also have sudo configured to allow both the user and the admin group to perform elevated things.
Thus, here's the problem. We'd like to use a domain admin user for the scanning access (which will allow us to configure a subnet scan using that account for all domain bound non-windows systems). Remote SSH access actually works as the Lansweeper service account CAN log in via SSH but after that, it really can't do anything of importance since it needs to sudo first.
Is it possible to get a sudo configuration option built into the scanning?
Thus, here's the problem. We'd like to use a domain admin user for the scanning access (which will allow us to configure a subnet scan using that account for all domain bound non-windows systems). Remote SSH access actually works as the Lansweeper service account CAN log in via SSH but after that, it really can't do anything of importance since it needs to sudo first.
Is it possible to get a sudo configuration option built into the scanning?
Labels:
- Labels:
-
Product Feedback
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-08-2010 10:34 PM
This probably won't make the 4.0 release, I'll add it to the wishlist.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-08-2010 10:26 PM
Actually, that pretty much covers it for my needs. I would have the ability to 'sudo su' and do elevated tasks, but there might be cases for others where the logged in user would not be able to sudo to root, so they would have to sudo the command itself (as opposed to sudo to root and then running the commands).
I love to have this work for me, but there is a larger segment of potential configurations that should be addressed so the most correct resolution is put into place.
To specifically answer your question...
ssh <user>@<server.host>
sudo su
<passwd>
<command1>
<command2>
<etc>
I love to have this work for me, but there is a larger segment of potential configurations that should be addressed so the most correct resolution is put into place.
To specifically answer your question...
ssh <user>@<server.host>
sudo su
<passwd>
<command1>
<command2>
<etc>

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-08-2010 08:06 PM
Could you give a detailed description of how this should work?
1) you log in with a normal user
2) you use sudo with another user and password
3) you execute the necessary commands.
1) you log in with a normal user
2) you use sudo with another user and password
3) you execute the necessary commands.
