** Also affects: sshuttle (Ubuntu Bionic) Importance: Undecided Status: New
** Also affects: sshuttle (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1787245 Title: Auto-hosts do not include fqdn Status in sshuttle package in Ubuntu: Confirmed Status in sshuttle source package in Xenial: New Status in sshuttle source package in Bionic: New Bug description: The --H, --auto-hosts option does not currently include fqdn and in fact removes the fqdn entries. This is blocking the use of sshuttle for things like accessing a Graylog server which links back to itself via fqdn. This has been fixed with pull request #173 [0] in Oct of 2017 adds this functionality and works for the Graylog forwarding which I've been trying to use it for. [0]: https://github.com/sshuttle/sshuttle/pull/173 [Impact] Some services which may be remotely accessed over an sshuttle vpn tunnel may require full fqdn access to remote machines. Depending on the remote application, it may fail to function properly if the initiator system cannot resolve hosts by fqdn's. Graylog mentioned above, is one such example of this. This patch works by changing the host watch functionality to match more than just hostnames found at the remote site. If fqdns are also found, then this patch will ensure they get included in the initator's local /etc/host file. [Test Case] 1. Initiate an sshuttle connection at a remote endpoint w/ the -H or --auto-hosts parameter. $ sshuttle 10.5.0.0/16 -r 10.230.65.47 --daemon -H 2. Observe the initiator's /etc/hosts file - Without the patch, observe only hostnames are populated - With the patch, hostnames and fqdns are populated [Regression Potential] This area of code is limited to only affecting those users using the --auto-hosts parameter. That being said, the change is to expand the regular expressions which identify remote hostnames to include/allow fqdns. It may be possible that this introduces a naming collision with the initiator's DNS resolution where they relied on foo and foo.some.domain resolve to uniquely different hosts. This may be an unwanted side-effect, but upstream seems not to be concerned with this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1787245/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp