Re: [Touch-packages] [Bug 103436] Re: sshd not reconfigured by /etc/network

2017-03-20 Thread Martin Pitt 
Hey Perry,

Perry E. Metzger [2017-03-20 13:11 -0400]:
> That bug report was a decade ago.

Yeah, I know :-)

> So far as I know, this is still an issue for your users, because sshd
> does not, on its own, change its network address when one changes
> networks. I would not remove this because if you remove it you're
> going to harm anyone who changes addresses frequently.

That's what I've thought, but it am puzzled that I cannot actually produce this
situation (when removing the script). That, and the fact that Fedora or SUSE
don't have this indicate that this was dealt with by something else in the
meantime.

> However, I have not used Ubuntu in many years (this is 2017, the bug
> report was 2007) and I am no longer in a position to help you.

No worries, it was a long shot anyway. Thanks for your fast response!

Martin

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/103436

Title:
  sshd not reconfigured by /etc/network

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: openssh-server

  If you have a device that roams a lot (like a laptop), you want
  daemons like sshd to be tweaked/restarted by scripts in /etc/network
  so that they re-open the socket they listen on when the network
  address changes. (Yes, some of us really do want to be able to
  remotely log in to our laptops after we bring them home and they roam
  onto the home WiFi network etc.)

  Right now there is no sshd script in /etc/network/* but it would be
  trivial to create one and add it to the package. For sshd, it would be
  simplest just to restart the daemon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/103436/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 103436] Re: sshd not reconfigured by /etc/network

2017-03-20 Thread Perry E. Metzger 
On Mon, 20 Mar 2017 13:18:54 - Martin Pitt
 wrote:
> Perry, I just revisited this:

That bug report was a decade ago.

So far as I know, this is still an issue for your users, because sshd
does not, on its own, change its network address when one changes
networks. I would not remove this because if you remove it you're
going to harm anyone who changes addresses frequently.

However, I have not used Ubuntu in many years (this is 2017, the bug
report was 2007) and I am no longer in a position to help you.

Perry
-- 
Perry E. Metzgerpe...@piermont.com

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/103436

Title:
  sshd not reconfigured by /etc/network

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: openssh-server

  If you have a device that roams a lot (like a laptop), you want
  daemons like sshd to be tweaked/restarted by scripts in /etc/network
  so that they re-open the socket they listen on when the network
  address changes. (Yes, some of us really do want to be able to
  remotely log in to our laptops after we bring them home and they roam
  onto the home WiFi network etc.)

  Right now there is no sshd script in /etc/network/* but it would be
  trivial to create one and add it to the package. For sshd, it would be
  simplest just to restart the daemon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/103436/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 103436] Re: sshd not reconfigured by /etc/network

2017-03-20 Thread Martin Pitt 
I filed bug 1674330 about dropping the hack.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/103436

Title:
  sshd not reconfigured by /etc/network

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: openssh-server

  If you have a device that roams a lot (like a laptop), you want
  daemons like sshd to be tweaked/restarted by scripts in /etc/network
  so that they re-open the socket they listen on when the network
  address changes. (Yes, some of us really do want to be able to
  remotely log in to our laptops after we bring them home and they roam
  onto the home WiFi network etc.)

  Right now there is no sshd script in /etc/network/* but it would be
  trivial to create one and add it to the package. For sshd, it would be
  simplest just to restart the daemon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/103436/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 103436] Re: sshd not reconfigured by /etc/network

2017-03-20 Thread Martin Pitt 
Perry, I just revisited this:

 - /etc/network/if-up.d/openssh-server hack introduces a race (you run
into connection errors after bringing up a new interface as sshd stops
listening briefly while being reloaded).

 - I can't seem to be able to actually reproduce that issue: I can start
a VM with no network interfaces, remove the above hack, then start sshd,
then bring up an ethernet interface, and I can connect to ssh via
ethernet just fine. Also, e. g. Fedora has no counterpart of this hack,
and these days a lot of people would complain if that would cause
problems, as hotpluggable/roaming network devices are everywhere.

 - /etc/network/if-up.d/ isn't being run when using networkd/netplan,
thus in our cloud instances. So far this doesn't seem to have caused any
issues.

So my questions:

  (1) Can you please describe more precisely what exactly you did back
then? Do you have a nonstandard SSH configuration with some
ListenAddresses/AddressFamily restrictions or similar?

  (2) Can you please disable the hack (sudo chmod 0 /etc/network/if-up.d
/openssh-server) and check if your use case works without it?

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/103436

Title:
  sshd not reconfigured by /etc/network

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: openssh-server

  If you have a device that roams a lot (like a laptop), you want
  daemons like sshd to be tweaked/restarted by scripts in /etc/network
  so that they re-open the socket they listen on when the network
  address changes. (Yes, some of us really do want to be able to
  remotely log in to our laptops after we bring them home and they roam
  onto the home WiFi network etc.)

  Right now there is no sshd script in /etc/network/* but it would be
  trivial to create one and add it to the package. For sshd, it would be
  simplest just to restart the daemon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/103436/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp