https://bugzilla.mindrot.org/show_bug.cgi?id=1952
--- Comment #2 from Adam <[email protected]> 2011-12-02 19:07:52 EST --- If you are talking about "/opt/ssh/utils/ssh_chroot_setup.sh", yes, I've used this script to init chroot directory, which is /adamroot in my test. So there are two nsswitch.conf files at /adamroot/etc/ and /etc/. I changed "ipnodes" in "/etc/nsswitch.conf", removing "nds" part. Meantime, "ipnodes" in "/adamroot/etc/nsswitch.conf" as the default value, "nds nis file". I also had the tunneling problem in this scenario. Here's another interesting part. If I put nds at the beginning of ipnodes, tunneling will be OK. But if I put either of other two methods at the beginning, but still have dns behind, I will still has this problem. Looks that even the order of "resolve from" will affect the results. If "dns nis files" passed, why just something like "files dns nis" should failed? (In reply to comment #1) > This looks like a misconfiguration: > > When you are in chroot mode, you will need to populate the chroot with > whatever support files your OS needs to support name resolution. This > may include nsswitch.conf, resolv.conf, hosts and possibly even shared > objects for NSS (depending on the platform). -- Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
