I'm running testing. A little while ago, a normal dselect update broke the usual behavior of my ssh sessions. I can no longer connect from work. I use a SOCKS proxy for ssh sessions outside my company's firewall. From my server logs: Aug 23 09:56:03 syed sshd[1960]: warning: /etc/hosts.allow, line 13: host name/name mismatch: proxy-ppv1.jf.intel.com != proxy-socks.jf.intel.com Aug 23 09:56:03 syed sshd[1960]: refused connect from 134.134.248.17 I have in my hosts.allow: ALL: .intel.com and it was working fine. I suppose the new default tcp behavior is more paranoid--this is good. I want to retain this behavior, except for this specific instance. Any suggestions? Sincerely, Jonathan -- Jonathan David Pearce <jonathan@pearce.name> http://www.andrew.cmu.edu/~jpearce/jpearce_keys.txt
Attachment:
pgpWUNBkafXep.pgp
Description: PGP signature