The reason is you do not protect your variable by quoting it:
should do the trick. You might have to quote the variable inside the function too to preserve its contents. It is generally good style to quote as exactly as possible, even if it is not absolutely necessary.
[Moderator-mode on] Please notice that we do not have a shortage in thread slots here, so please open a new thread if you have a new question.
We are trying to build a knowledge base. That means, if some other user has the same problem like you ideally he should be able to find the solution without having to ask the question again, just by searching the forum.
Having several independent problems discussed in a single thread does not further this cause, because a user with your shell problem is likely not searching for a thread about ssh configuration.
Nobody will think bad about you if have several different problems and open several different threads, one for each of them. Quite contrary this is what we ask you to do.
Another point is forum specialization: you might notice that there are different parts of the forum, one for AIX and one for shell programming for instance. Sometimes it is difficult to decide where a thread should go, but in this case it would have been easy, but now we have a thread which deals with two (or three) different problems and each part would belong to a different part of the forum.
I hope you understand and i ask you follow these forum behavior standards more carefully in the future. Thank you.
[/Moderator Mode off]
I hope this helps.
Absolutly correct, bak! That simple, yet important--at least in my case--trick, did the job. Thanks alot.
Hi,
I am trying to scp a file from our Unix server to the local Windows machine.I have created the key pair in Unix server using ssh-keygen command in unix.
But I am not sure where can we put the public key(generated on Unix) in Windows machine so that scp from Unix machine to Windows is... (3 Replies)
I am writing a script that needs to access various servers some of which are not ssh enabled. In order to access the ssh enabled servers I am using the following command to generate the public key :
ssh-keygen -t rsa
Is there a similar command for the other servers as well.
If I try to use... (1 Reply)
I am writing a script that needs to access various servers some of which are not ssh enabled. In order to access the ssh enabled servers I am using the following command to generate the public key :
ssh-keygen -t rsa
Is there a similar command for the other servers as well.
If I try to use... (1 Reply)
Hi All;
I have an issue with password less authentication via ssh ( v2)
I have two servers Server A and Server B, following are the server details
Server A
OS - HP UX B.11.11 U 9000/800
SSH - OpenSSH_4.3p2-hpn, OpenSSL 0.9.7i 14 Oct 2005
HP-UX Secure Shell-A.04.30.000, HP-UX... (3 Replies)
Hi, I've used the following way to set ssh public key authentication and it is working fine on Solaris 10, RedHat Linux and SuSE Linux servers without any problem. But I got error 'Server refused our key' on Solaris 8 system. Solaris 8 uses SSH2 too. Why? Please help. Thanks.
... (1 Reply)
Hi,
please guide me create a public/private key using ssh-keygen, lets say I have been access to server named pngpcdb1with a userid and password ...!!! and also please explain in detail the concept of these keys and ssh as I was planning to use them in ftp related scripts..! Thanks in... (1 Reply)
My password-free ssh connection has worked in the past but has stopped working and I can't get it going again.
The files in .ssh on both source and target are set to 600:
drwx------ 2 ingres 1024 Mar 2 13:57 .
drwxr-xr-x 25 ingres 2048 Mar 29 09:38 ..
-rw------- 1 ingres ... (9 Replies)
Hi i am using solaris 10.I am trying to setup a public/private key but it is not working.Appreciate your repsonse on it
There are two servers DB1 server and DB2 server.
1)I have generated public/private key using below step on both servers.
ssh-keygen -t rsa
2)From DB1 server moved the... (6 Replies)
Discussion started by: muraliinfy04
6 Replies
LEARN ABOUT OPENDARWIN
ssh-keyscan
SSH-KEYSCAN(1) BSD General Commands Manual SSH-KEYSCAN(1)NAME
ssh-keyscan -- gather ssh public keys
SYNOPSIS
ssh-keyscan [-46cHv] [-f file] [-p port] [-T timeout] [-t type] [host | addrlist namelist] ...
DESCRIPTION
ssh-keyscan is a utility for gathering the public ssh host keys of a number of hosts. It was designed to aid in building and verifying
ssh_known_hosts files. ssh-keyscan provides a minimal interface suitable for use by shell and perl scripts.
ssh-keyscan uses non-blocking socket I/O to contact as many hosts as possible in parallel, so it is very efficient. The keys from a domain
of 1,000 hosts can be collected in tens of seconds, even when some of those hosts are down or do not run ssh. For scanning, one does not
need login access to the machines that are being scanned, nor does the scanning process involve any encryption.
The options are as follows:
-4 Forces ssh-keyscan to use IPv4 addresses only.
-6 Forces ssh-keyscan to use IPv6 addresses only.
-c Request certificates from target hosts instead of plain keys.
-f file
Read hosts or ``addrlist namelist'' pairs from file, one per line. If - is supplied instead of a filename, ssh-keyscan will read
hosts or ``addrlist namelist'' pairs from the standard input.
-H Hash all hostnames and addresses in the output. Hashed names may be used normally by ssh and sshd, but they do not reveal identify-
ing information should the file's contents be disclosed.
-p port
Port to connect to on the remote host.
-T timeout
Set the timeout for connection attempts. If timeout seconds have elapsed since a connection was initiated to a host or since the
last time anything was read from that host, then the connection is closed and the host in question considered unavailable. Default
is 5 seconds.
-t type
Specifies the type of the key to fetch from the scanned hosts. The possible values are ``dsa'', ``ecdsa'', ``ed25519'', or ``rsa''.
Multiple values may be specified by separating them with commas. The default is to fetch ``rsa'', ``ecdsa'', and ``ed25519'' keys.
-v Verbose mode. Causes ssh-keyscan to print debugging messages about its progress.
SECURITY
If an ssh_known_hosts file is constructed using ssh-keyscan without verifying the keys, users will be vulnerable to man in the middle
attacks. On the other hand, if the security model allows such a risk, ssh-keyscan can help in the detection of tampered keyfiles or man in
the middle attacks which have begun after the ssh_known_hosts file was created.
FILES
Input format:
1.2.3.4,1.2.4.4 name.my.domain,name,n.my.domain,n,1.2.3.4,1.2.4.4
Output format for RSA, DSA, ECDSA, and Ed25519 keys:
host-or-namelist keytype base64-encoded-key
Where keytype is either ``ecdsa-sha2-nistp256'', ``ecdsa-sha2-nistp384'', ``ecdsa-sha2-nistp521'', ``ssh-ed25519'', ``ssh-dss'' or
``ssh-rsa''.
/etc/ssh/ssh_known_hosts
EXAMPLES
Print the rsa host key for machine hostname:
$ ssh-keyscan hostname
Find all hosts from the file ssh_hosts which have new or different keys from those in the sorted file ssh_known_hosts:
$ ssh-keyscan -t rsa,dsa,ecdsa,ed25519 -f ssh_hosts |
sort -u - ssh_known_hosts | diff ssh_known_hosts -
SEE ALSO ssh(1), sshd(8)AUTHORS
David Mazieres <dm@lcs.mit.edu> wrote the initial version, and Wayne Davison <wayned@users.sourceforge.net> added support for protocol ver-
sion 2.
BUGS
It generates "Connection closed by remote host" messages on the consoles of all the machines it scans if the server is older than version
2.9. This is because it opens a connection to the ssh port, reads the public key, and drops the connection as soon as it gets the key.
BSD May 2, 2017 BSD