10 More Discussions You Might Find Interesting
1. Solaris
Trying to figure out the best method of security for oracle user accounts. In Solaris 10 they are set as regular users but have nologin set forcing the dev's to login as themselves and then su to the oracle users.
In Solaris11 we have the option of making it a role because RBAC is enabled but... (1 Reply)
Discussion started by: os2mac
1 Replies
2. Shell Programming and Scripting
Hi
I'm writing a script which based on a condition, restarts a set of servers. The problem I'm facing is, say if one of the server is down, my script stops there and fails to proceed. How can I ensure to set a timeout value on that script, so when the server is not reachable, the script should... (2 Replies)
Discussion started by: mathbalaji
2 Replies
3. Solaris
Hi All
I need to set timeout of login session of a user if a user is idle for some time.
I know the TMOUT setting but it work with only BASH & KORN shell only as I need to set for Bourne shell also. I am trying to put "ClientAliveInterval 300" in sshd_config & restart or refreshing the... (1 Reply)
Discussion started by: sb200
1 Replies
4. Shell Programming and Scripting
Hi
I am using mpssh client for parallel ssh connections. I need help in setting the timeout for the parallel sessions say 30 seconds. Plz Help.
Thanks in advance
M.S.Srivatsa
Double post, continued here (0 Replies)
Discussion started by: mssrivatsa
0 Replies
5. Red Hat
Is there a Linux tunable to reduce the amount of time a socket waits before considering the remote side dead?
Its the same senario when you try to telnet to a dead machine, telnet sits and waits for ~30seconds, before the socket timer expires and cancels the request. (5 Replies)
Discussion started by: mrmurdock
5 Replies
6. AIX
Hi all
Can any one solve my problem? I want to change the default timeout setting for telnet in aix, pls help me. (1 Reply)
Discussion started by: vjm
1 Replies
7. Solaris
Hello;
I have Solaris 2.6 installed on many Sun AXI Ultra Sparc IIi systems. I want to set the Lock Screen global timeout for all users to 15 minutes. I read the Solaris CDE guide which instructed me to create a /etc/dt/config/C/sys.resources file and changed the timout to 15 minutes in... (1 Reply)
Discussion started by: rambo15
1 Replies
8. Solaris
Hello everyone
I am a new one,I want to know how to get the solaris force the loginer out if he do not in a time
thanks (4 Replies)
Discussion started by: lyh003473
4 Replies
9. HP-UX
How can I kick a user out after being idle for a certain amount of time, would prefer not to use scripts, will TMOUT work on HP-UX? (5 Replies)
Discussion started by: csaunders
5 Replies
10. UNIX for Advanced & Expert Users
Hi! Experts,
Could someone tell me how to set a time out for xterm users.. I have set TMOUT which logs out telnet users after sometime..
The users here use exceed to connect to Xterm server. So, it doesnt kill xterm windows that have not been used even for 7 days..
Is there any work... (1 Reply)
Discussion started by: jyotipg
1 Replies
LEARN ABOUT MOJAVE
ssh-keyscan
SSH-KEYSCAN(1) BSD General Commands Manual SSH-KEYSCAN(1)
NAME
ssh-keyscan -- gather SSH public keys
SYNOPSIS
ssh-keyscan [-46cDHv] [-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, the format of which is documented in sshd(8). 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 sshd(8). 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 Force ssh-keyscan to use IPv4 addresses only.
-6 Force ssh-keyscan to use IPv6 addresses only.
-c Request certificates from target hosts instead of plain keys.
-D Print keys found as SSHFP DNS records. The default is to print keys in a format usable as a ssh(1) known_hosts file.
-f file
Read hosts or ``addrlist namelist'' pairs from file, one per line. If '-' is supplied instead of a filename, ssh-keyscan will read
from the standard input. Input is expected in the 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
-H Hash all hostnames and addresses in the output. Hashed names may be used normally by ssh(1) and sshd(8), but they do not reveal
identifying information should the file's contents be disclosed.
-p port
Connect to port 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, the connection is closed and the host in question considered unavailable. The default is
5 seconds.
-t type
Specify 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: print debugging messages about progress.
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
/etc/ssh/ssh_known_hosts
EXAMPLES
Print the RSA host key for machine hostname:
$ ssh-keyscan -t rsa 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)
Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints, RFC 4255, 2006.
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.
BSD
March 5, 2018 BSD