05-11-2010
Accept fingerprint automaticaly secureCRT
Hello,
Is it any way to accept automaticaly the fingerprints?
The basic idea is to find a way to give a command to many servers at once.
So i thought to create a multiple session with all the connections opened them in multiple tabs and give the command at once to all the opened windows via chat window.
I saw an option /ACCEPTHOSTKEYS but i don't know how to use it.
I tried to run it via cmd SecureCrt.exe /ACCEPTHOSTKEYS but i just managed to run the program
Another way i saw in a closed thread here is to create a script and include /ACCEPTHOSTKEYS is the code.But when i try to run a sample script named "ConnectTomultipleSessionsAndSendCommands" needs a sessionList.txt file that does not exist.
I created the file but i don't know what i have to include so that i connect to all sessions(with saved username/password) and execute the commands to all sessions
Regards
7 More Discussions You Might Find Interesting
1. Solaris
hello
any way to avoid the fingerprint authenticity step when I ssh the first time to a server by always setting a 'yes' as a default answer?
thanks (10 Replies)
Discussion started by: melanie_pfefer
10 Replies
2. Shell Programming and Scripting
Post has been removed. Prakash K :) (0 Replies)
Discussion started by: bullz26
0 Replies
3. AIX
When I use SecureCRT software to connect with AIX servers, don't know why sessions always be kicked out from the SecureCRT if I don't do anything in a few minutes. I think this maybe the SecureCRT configuraiton problem, Who knows how to keep session conect even through I don't do anything?
... (3 Replies)
Discussion started by: rainbow_bean
3 Replies
4. Shell Programming and Scripting
i have a problem with the code I created (see below).
a. when I logged in as root and su to tomcat, i can execute all options. when I press X, it will exit properly.
b. when I logged in directly as user1, I can execute also all options. if I press X i will logout automatically to putty.... (2 Replies)
Discussion started by: lhareigh890
2 Replies
5. UNIX for Advanced & Expert Users
I'm a teacher who teaching computer programming languages.
Generally, I give each student a username in a Linux Server. Then each student use his username to login the Server and program their programming task by putty or secureCRT and so on.
But one fact had bothered me for a long... (9 Replies)
Discussion started by: cqlouis
9 Replies
6. Shell Programming and Scripting
Hi I am new to shell scripting,
Can you please help me in writing a script that can switch user in same server with different user name and same password.
I want to perform some functional task in a particular user and need to switch user and perform same activity in another user and so on ...
... (4 Replies)
Discussion started by: Dew
4 Replies
7. Shell Programming and Scripting
I am trying to create a bash script that will create new function by using the user input. The below will create the necessary files in the correct format, however when it comes to the # create function I am at a loss.
If the name entered was NEWNAME and the genes were GENE1,GENE2 then two files... (0 Replies)
Discussion started by: cmccabe
0 Replies
SETUID(1) General Commands Manual SETUID(1)
NAME
setuid - run a command with a different uid.
SYNOPSIS
setuid username|uid command [ args ]
DESCRIPTION
Setuid changes user id, then executes the specified command. Unlike some versions of su(1), this program doesn't ever ask for a password
when executed with effective uid=root. This program doesn't change the environment; it only changes the uid and then uses execvp() to find
the command in the path, and execute it. (If the command is a script, execvp() passes the command name to /bin/sh for processing.)
For example,
setuid some_user $SHELL
can be used to start a shell running as another user.
Setuid is useful inside scripts that are being run by a setuid-root user -- such as a script invoked with super, so that the script can
execute some commands using the uid of the original user, instead of root. This allows unsafe commands (such as editors and pagers) to be
used in a non-root mode inside a super script. For example, an operator with permission to modify a certain protected_file could use a
super command that simply does:
cp protected_file temp_file
setuid $ORIG_USER ${EDITOR:-/bin/vi} temp_file
cp temp_file protected_file
(Note: don't use this example directly. If the temp_file can somehow be replaced by another user, as might be the case if it's kept in a
temporary directory, there will be a race condition in the time between editing the temporary file and copying it back to the protected
file.)
AUTHOR
Will Deich
local SETUID(1)