[Touch-packages] [Bug 1576353] Re: Install openssh-server with disabled password auth by default on servers

2018-10-09 Thread Scott Moser
@Adam, > See the comment on the linked debian-cd MP from Marc Deslauriers. Note > that the goal of removing the cloud-image seed is still entirely > reasonable and doable, openssh-server should just move to livecd-rootfs > as something always added to cloud images. Done and done. There's no Your

[Touch-packages] [Bug 1576353] Re: Install openssh-server with disabled password auth by default on servers

2018-10-05 Thread Adam Conrad
** Changed in: ubuntu-cdimage Status: In Progress => Won't Fix -- 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/1576353 Title: Install openssh-server with disabled

[Touch-packages] [Bug 1576353] Re: Install openssh-server with disabled password auth by default on servers

2018-10-05 Thread Dimitri John Ledkov
This is won't fix at the moment, please see comments at https://code.launchpad.net/~vorlon/debian-cd/lp.1576353/+merge/348112 ** Changed in: livecd-rootfs (Ubuntu) Status: New => Won't Fix ** Changed in: ubuntu-meta (Ubuntu) Status: New => Won't Fix -- You received this bug

[Touch-packages] [Bug 1576353] Re: Install openssh-server with disabled password auth by default on servers

2018-10-05 Thread Adam Conrad
See the comment on the linked debian-cd MP from Marc Deslauriers. Note that the goal of removing the cloud-image seed is still entirely reasonable and doable, openssh-server should just move to livecd-rootfs as something always added to cloud images. Done and done. There's no reason that one

[Touch-packages] [Bug 1576353] Re: Install openssh-server with disabled password auth by default on servers

2018-06-20 Thread Francis Ginther
** Tags added: id-5a4c19be676c7709fe6b2d20 -- 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/1576353 Title: Install openssh-server with disabled password auth by default on

[Touch-packages] [Bug 1576353] Re: Install openssh-server with disabled password auth by default on servers

2018-06-15 Thread Launchpad Bug Tracker
** Branch linked: lp:~vorlon/debian-cd/lp.1576353 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1576353 Title: Install openssh-server with disabled password auth by

[Touch-packages] [Bug 1576353] Re: Install openssh-server with disabled password auth by default on servers

2018-06-15 Thread Steve Langasek
** Changed in: ubuntu-cdimage Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1576353 Title: Install openssh-server with disabled

[Touch-packages] [Bug 1576353] Re: Install openssh-server with disabled password auth by default on servers

2018-06-15 Thread Steve Langasek
AIUI the required openssh piece of this is now done: openssh (1:7.6p1-4) unstable; urgency=medium * Move VCS to salsa.debian.org. * Add a preseeding-only openssh-server/password-authentication debconf template that can be used to disable password authentication (closes: #878945).

[Touch-packages] [Bug 1576353] Re: Install openssh-server with disabled password auth by default on servers

2016-04-30 Thread Colin Watson
I've sent the proposed text of a debconf template for review to the debian-l10n-english list. -- 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/1576353 Title: Install

[Touch-packages] [Bug 1576353] Re: Install openssh-server with disabled password auth by default on servers

2016-04-30 Thread Colin Watson
Incidentally, my reasoning for "true by default" in the package is basically the bootstrapping problem; I don't want this to be a nasty surprise for people with existing deployment strategies. Changing PermitRootLogin was controversy enough. But I don't mind what the setting of this on server