Tim Nelson wrote: > Is there a way to disable this error/authenticity check globally for a system? I understand it may not be the best practice in terms of security, but for an internal trusted host, I have no reservations making this change. > ssh -o StrictHostKeyChecking=no .... or add that option to ~/.ssh/ssh_config in each client user's account... _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: SSH Authenticity Messages... Disable/
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: CentOS mailing list <centos@xxxxxxxxxx>
- Subject: Re: SSH Authenticity Messages... Disable/
- From: John R Pierce <pierce@xxxxxxxxxxxx>
- Date: Mon, 29 Jun 2009 09:13:37 -0700
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <20335503.611246291053122.JavaMail.root@xxxxxxxxxxxxxxxxxxx>
- References: <20335503.611246291053122.JavaMail.root@xxxxxxxxxxxxxxxxxxx>
- User-agent: Thunderbird 2.0.0.22 (Windows/20090605)
- References:
- SSH Authenticity Messages... Disable/
- From: Tim Nelson
- SSH Authenticity Messages... Disable/
- Prev by Date: Re: SSH Authenticity Messages... Disable/
- Next by Date: Re: SSH Authenticity Messages... Disable/
- Previous by thread: Re: SSH Authenticity Messages... Disable/
- Next by thread: Re: SSH Authenticity Messages... Disable/
- Index(es):
 |