If you are not worried about the security try these in your ~/.ssh/config .
NOTE: This is not secure so make your call. I am working on intranet and do not worry about man in the middle attack.
Host *
# Ignore Host ID changes.
StrictHostKeyChecking no
# Do not store the known hosts.
UserKnownHostsFile /dev/null
# -X option by default.
ForwardX11 yes
Irritating message:
~$ ssh -o "StrictHostKeyChecking no" username@host.domain
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
82:e7:bc:0c:6d:cc:3c:e2:c7:de:ee:2a:b2:af:31:f9.
Please contact your system administrator.
Add correct host key in /home/myacct/.ssh/known_hosts to get rid of this message.
Offending key in /home/myacct/.ssh/known_hosts:5
Password authentication is disabled to avoid man-in-the-middle attacks.
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
Permission denied (publickey,gssapi-with-mic,password).