Login or Register to Ask a Question and Join Our Community


Shell Programming and Scripting

monitoring SSH authorized_keys

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting monitoring SSH authorized_keys
# 1  
Old 07-19-2007
monitoring SSH authorized_keys
Hi,

We have around 200 SUN Servers in production environment and I have one box from where I manage all the servers. It's setup such that I can SSH from my box onto all the 200 servers with without supplying password. It is working fine but sometimes we notice the keys getting changed and asking for password once in a while.

So, the requirement is to have a script that checks if I can login from my box to ALL 200 box without supplying password (i.e., ensuring no keys changed). The condition here we have is NOT to use RSH/RLOGIN for checking the keys or whatever it is for.

Any help highly appreciated

Thanks

Praveen RK
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Ubuntu

Help me to revert the file /root/.ssh/authorized_keys

Hi, I copied the key of rsa.pub to authorized_keys using the below command cat /root/.ssh/id_rsa.pub >> /root/.ssh/authorized_keys By mistake i have executed another command view cat /root/.ssh/id_rsa.pub >> /root/.ssh/authorized_keys so now additional keys are copied.so please help me... (3 Replies)
Discussion started by: SA_Palani
3 Replies

2. Shell Programming and Scripting

Appending authorized_keys on multiple servers using ssh

Hi I have an ssh 'for' loop script to login and put a key on multiple servers. I need to append a file on each server but the command which works ok from the prompt does not work via the script. I have cat filename | ssh user@servername "cat >>append.file.name" I have tried to 'spawn' this in... (0 Replies)
Discussion started by: Grueben
0 Replies

3. Red Hat

Choosing best location for authorized_keys!

Hello Friends, I am trying to troubleshoot one scenario for the customer. In their server configuration, each vhost has it's own user. The option is to shell access chrooted. The question is where would be the best place to store the authorized_keys file so that we can ssh in from the... (0 Replies)
Discussion started by: user3528
0 Replies

4. Shell Programming and Scripting

SSH Process monitoring and Exit Status evaluation

Hi All, I have a peculiar requirement as follows, I have a some hosts on which i have to run a script, so i am using the following code piece for i in $HOSTLIST do ssh ${i} "~/task.sh" done Now i want to run this same thing in parallel on all the hosts and then monitor the ssh process... (1 Reply)
Discussion started by: mihirvora16
1 Replies

5. Shell Programming and Scripting

SSH w/ command in authorized_keys apparently needs pty

I'm trying to have an unattended remote PC log some data on home PC. man sshd says I should be able to put a command in authorized_keys. This is what I have on the remote machine. The key is a special key that isn't used elsewhere. In my ~/.ssh/authorized_keys file on my desktop:... (12 Replies)
Discussion started by: KenJackson
12 Replies

6. UNIX for Advanced & Expert Users

bigbrother monitoring:conn ssh on server clients goes purple green alternatively

i am using big brother 1.9i.some clients are shut down.but server and other clients are on and bb is running successfullly on all of them.But network tests like conn ssh,telnet etc are going purple for some time and become green for some time on all clients and server reports are not updating..i... (1 Reply)
Discussion started by: pankajd
1 Replies

7. Red Hat

authorized_keys and passwordless login

I am trying to set up ssh/scp to be able to login in w/o using a password. The man pages for ssh and ssh-keygen explain how to do this. So, using "rsa1" style, I created the public and private keys by way of ssh-keygen, then added the contents of "$HOME/.ssh/identity.pub" to a newly created... (6 Replies)
Discussion started by: mcrouch_2003
6 Replies

8. Shell Programming and Scripting

sftp using authorized_keys in unix

I am creating public and private key for sftp in ksh. then copy the name1.pub file into /.ssh/authorized_keys directory in remote server. Now my question is how to write that script which do not ask me for the password from prompt. please help. thanks in advance. (1 Reply)
Discussion started by: rinku
1 Replies

9. UNIX for Dummies Questions & Answers

ssh keys monitoring

Hi, I have ssh keys (id_rsa and id_rsa.pub). However, every once in a while, someone deletes these keys. here's what i want to do : 1. on my server, it will ssh user@password into the target machine(where ssh keys are located). 2. check the date/filesize of id_rsa, id_rsa.pub). 3.... (0 Replies)
Discussion started by: tungaw2004
0 Replies

10. UNIX for Advanced & Expert Users

monitoring SSH authorized_keys

Hi, We have around 200 SUN Servers in production environment and I have one box from where I manage all the servers. It's setup such that I can SSH from my box onto all the 200 servers with without supplying password. It is working fine but sometimes we notice the keys getting changed and asking... (1 Reply)
Discussion started by: prvnrk
1 Replies
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

sslh

SSLH(1p)						User Contributed Perl Documentation						  SSLH(1p)

NAME

       sslh - Switch incoming connection between SSH and SSL/HTTPS servers

SYNOPSIS

       sslh [ -v ] [ -p [host:]port ] [ -t timeout ]
	    [ --ssh [host:]port ] [ --ssl [host:]port ]

DESCRIPTION

       sslh is a simple script that lets you switch an incoming connection on a single port between distinct SSH and SSL/HTTPS servers.

       sslh listens for connections on a port and is able to redirect them either to an HTTPS web server or a SSH server.

       This lets one setup both a HTTPS web server and a SSH server and access them through the same host+port.

OPTIONS

       The program follows the usual GNU command line syntax, with long options starting with two dashes.

       -p, --port [host:]port
	   The port the proxy will listen to.  If no port is given, 443 is used by default.  If no host is given, "localhost" is used by default.

       -s, --ssh [host:]port
	   The SSH server which the SSH connections must be forwarded to.  If omitted, the default is localhost:22.

       -l, --ssl, --https [host:]port
	   The HTTPS server which the HTTPS connections must be forwarded to.  If omitted, the default is localhost:443.

       -t, --timeout delay
	   Timeout in seconds before a silent incoming connection is considered as a SSH connection. The number can be fractional.

	   The default is 2seconds.

       -v, --verbose
	   Verbose output.  This option can be used several times for more verbose output.

EXAMPLE OF USE

       Is this tool actually useful? Yes.

       For example one can use it to access both a SSH server and a secure web server via a corporate proxy that only accepts to relay connections
       to port 443. Creating a tunnel that passes SSH connection through a CONNECT-enabled web proxy is easy with connect-tunnel (also included in
       the "Net::Proxy" distribution).

       The proxy will let both SSH and HTTPS connections out (since they all point to port 443), and the home server will connect those incoming
       connections to the appropriate server. This only requires to run the HTTPS server on a non standard port (not 443).

TECHNICAL NOTE

       How can this proxy find out what kind of protocol is using a TCP connection to port 443, without being connected (yet) to the server?  We
       actually rely on a slight difference between the SSL and SSH protocols (found thanks to ethereal):

       SSH Once the TCP connection is established, the server speaks first, presenting itself by saying something like:

	       SSH-2.0-OpenSSH_3.6.1p2 Debian 1:3.6.1p2-1

       SSL With SSL, it's always the client that speaks first.

       This means that sslh can be used with any pair of protocols/services that share this property (the client speaks first for one and the
       server speaks first for the other).

AUTHORS

       Original idea and C version
	   Frederic Ple "<sslh@wattoo.org>".

       Perl versions
	   Philippe 'BooK' Bruhat "<book@cpan.org>".

SCRIPT HISTORY

       Version 0.01 of the script was a quick hack designed in 2003 as a proof of concept.

       Version 0.02 (and higher) are based on "Net::Proxy", and included with the "Net::Proxy" distribution. Version 0.02 didn't work, though.

       Version 0.03 correctly initialised the "in" connector.

       Version 0.04 lets the proxy listen on any address (instead of "localhost", which is still the default). Thanks to Dieter Voegtli for
       spotting this.

SEE ALSO

       Net::Proxy, Net::Proxy::Connector::dual.

COPYRIGHT

       Copyright 2003-2006, Philippe Bruhat. All rights reserved.

LICENSE

       This module is free software; you can redistribute it or modify it under the same terms as Perl itself.

perl v5.10.1							    2009-10-18								  SSLH(1p)