So my understanding of your question is that you want to have passwordless ssh command only work if its invoked by a particular script?
Really, the only reasonable way I can think to do that is:
1) push the passwordless ability to some other user
2) have that script be invoked via a sudo to that user and only that script.
That would get you to the point where you would do something like:
Ultimately, it's about removing the shared account's ability to directly use the public/private key associated with the remote login. Whether that involves pushing the passwordless functionality to a different user and just control who can run the script as the newer user (as described above) or leaving it in place and having people use a different shared account, that's what needs to happen.
Hi @ all!
I've a problem with a ssh-connection.
I want to establish a ssh-connection between an AIX-System and an SunOS-System without a password.
The Users are different one's.
Command :
user1@server1 /home/user1 > ssh user2@server2
Is it possible?
Greetings olli-h (1 Reply)
When i was connecting the Solaris system by sftp . i got the following error.
"Warning: child process (/usr/local/bin/ssh2) exited with code 74."
Could any one help, how to fix it ? (1 Reply)
My problem is this....:eek:
Platform=Sun Solaris UNIX / Oracle 10g
1) I'm trying to SSH from my local system A to remote system B
2) Once connected, I need to sudo to ID that has the ability to connect to the Oracle database
3) Then run a script that connects via sqlplus and... (2 Replies)
Hi i am trying to do ssh without password between 2 aix servers.
before i generate the keys, i am able to do the ssh & it is asking for password & i am able to login.
========================
# ssh 172.29.150.77
root@172.29.150.77's password:
========================
but when i generate rsa... (1 Reply)
Hi everybody,
I am running a program on a supercomputer via my personal computer through a ssh connection. My program take more than a day to run, so when I left work with my PC I stop the connection with the supercomputer and the program stop.
I am wondering if someone know how I can manage... (2 Replies)
Hi!
I know its a recurring problem, but I am failing to sort this out, I have two servers ( A and B), in which I am able to connect without having to put password from server B to server A, but the connect from server A to server B.
takes 7 minutes to establish???
on Server A, I have the... (7 Replies)
Hello guys!
I am setting up a script to access a unix remote server. My problem is that when I put the ssh line "my host", the script does not wait for the server response asking for the password to execute the line in which I put the password, that is, I need to put a form in which script has a... (1 Reply)
Hi,
I want to validate ssh connection one after one for multiple servers..... password less keys already setup but now i want to validate if ssh is working fine or not...
I have .sh script like below and i have servers.txt contains all the list of servers
#/bin/bash
for host in $(cat... (3 Replies)
Discussion started by: sreeram4
3 Replies
LEARN ABOUT DEBIAN
gksu
GKSU(1) User Commands GKSU(1)NAME
gksu - GTK+ frontend for su and sudo
SYNOPSIS
gksu
gksu [-u <user>] [options] <command>
gksudo [-u <user>] [options] <command>
DESCRIPTION
This manual page documents briefly gksu and gksudo
gksu is a frontend to su and gksudo is a frontend to sudo. Their primary purpose is to run graphical commands that need root without the
need to run an X terminal emulator and using su directly.
Notice that all the magic is done by the underlying library, libgksu. Also notice that the library will decide if it should use su or sudo
as backend using the /apps/gksu/sudo-mode gconf key, if you call the gksu command. You can force the backend by using the gksudo command,
or by using the --sudo-mode and --su-mode options.
If no command is given, the gksu program will display a small window that allows you to type in a command to be run, and to select what
user the program should be run as. The other options are disregarded, right now, in this mode.
OPTIONS --debug, -d
Print information on the screen that might be useful for diagnosing and/or solving problems.
--user <user>, -u <user>
Call <command> as the specified user.
--disable-grab, -g
Disable the "locking" of the keyboard, mouse, and focus done by the program when asking for password.
--prompt, -P
Ask the user if they want to have their keyboard and mouse grabbed before doing so.
--preserve-env, -k
Preserve the current environments, does not set $HOME nor $PATH, for example.
--login, -l
Make this a login shell. Beware this may cause problems with the Xauthority magic. Run xhost to allow the target user to open win-
dows on your display!
--description <description|file>, -D <description|file>
Provide a descriptive name for the command to be used in the default message, making it nicer. You can also provide the absolute
path for a .desktop file. The Name key for will be used in this case.
--message <message>, -m <message>
Replace the standard message shown to ask for password for the argument passed to the option. Only use this if --description does
not suffice.
--print-pass, -p
Ask gksu to print the password to stdout, just like ssh-askpass. Useful to use in scripts with programs that accept receiving the
password on stdin.
--su-mode, -w
Force gksu to use su(1) as its backend for running the programs.
--sudo-mode, -S
Force gksu to use sudo(1) as its backend for running the programs.
SEE ALSO su(1), sudo(1)gksu version 2.0.x August 2006 GKSU(1)