[Bug 424371] Re: Logins to OpenSSH server slow due to "UseDNS yes" config

2016-02-28 Thread Colin Watson
We don't modify this in Debian/Ubuntu. The default was changed to "UseDNS no" in OpenSSH 6.8p1, which is in Ubuntu 15.10 and later. ** Changed in: openssh (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team,

[Bug 424371] Re: Logins to OpenSSH server slow due to "UseDNS yes" config

2016-02-28 Thread beej
the bug i filed with openssh was marked WONTFIX. the developer who did so claims that the openssh default is UseDNS=no. can somebody check if the latest ubuntu default is still UseDNS=yes? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed

[Bug 424371] Re: Logins to OpenSSH server slow due to "UseDNS yes" config

2016-02-26 Thread beej
instead of asking the OpenSSH project to change their default configuration, i filed a bug to have the lookup not be blocking. Bug 2545 - reverse DNS lookups shouldn't block login https://bugzilla.mindrot.org/show_bug.cgi?id=2545 ** Bug watch added: OpenSSH Portable Bugzilla #2545

[Bug 424371] Re: Logins to OpenSSH server slow due to "UseDNS yes" config

2016-02-26 Thread Alexander
Does someone sent this upstream? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/424371 Title: Logins to OpenSSH server slow due to "UseDNS yes" config To manage notifications

[Bug 424371] Re: Logins to OpenSSH server slow due to UseDNS yes config

2014-12-08 Thread Roderick Smith
Just to note: This problem still exists in Ubuntu 14.04LTS and 14.10. It's annoying because I have to make changes to every new installation. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu.

[Bug 424371] Re: Logins to OpenSSH server slow due to UseDNS yes config

2014-03-05 Thread Rodney Beede
I'd propose submitting a request upstream to make the default setting for UseDNS be No. Additionally add comments in the sshd_config and man page: # UseDNS - Determines whether IP Address to Hostname lookup and comparison is performed # Default value is No which avoids login delays when the

[Bug 424371] Re: Logins to OpenSSH server slow due to UseDNS yes config

2009-10-26 Thread Brian
I have this same issue, but on Fedora (yes, I realize this is an ubuntu forum) On Fedora, I have the issue on 5.2 openssh (FC10+) but not on 5.1 (FC9) If a host is in the hosts file, it connects instantly. If it needs to check DNS, it takes 15 seconds or more to connect. There's no slowness to

[Bug 424371] Re: Logins to OpenSSH server slow due to UseDNS yes config

2009-10-13 Thread Brian Kelley
Lunch, I did not have that line in the nsswitch.conf file, I had already checked. And yes Chuck, I am still experiencing it (and I found another computer that is also doing it, Cent OS 4.5, same version of OpenSSH) -- Logins to OpenSSH server slow due to UseDNS yes config

[Bug 424371] Re: Logins to OpenSSH server slow due to UseDNS yes config

2009-10-12 Thread Chuck Short
Hi, I was wondering if you were still having this problem? Regards chuck ** Changed in: openssh (Ubuntu) Importance: Undecided = Low ** Changed in: openssh (Ubuntu) Status: New = Incomplete -- Logins to OpenSSH server slow due to UseDNS yes config

[Bug 424371] Re: Logins to OpenSSH server slow due to UseDNS yes config

2009-09-15 Thread lunch
I found this and it worked... go into your /etc/nsswitch.conf file and comment out the hosts line - apparently the delay is caused by mdns time outs... Restart your ssh server and you should be good to go. -- Logins to OpenSSH server slow due to UseDNS yes config

[Bug 424371] Re: Logins to OpenSSH server slow due to UseDNS yes config

2009-09-04 Thread Brian Kelley
After reading more about UseDNS, the more pertinent issue is what is the point of it at all if a false IP for the hostname is still accepted as a valid connection. Also, why is there no setting to make it timeout after a certain number of seconds (aka, what if the DNS request didn't time out for