Hi Ferenc,
On Tue, Jan 31, 2017 at 04:23:07PM +0100, Ferenc Wágner wrote:
> Hi,
>
> How is this supposed to work now? On a fresh stretch install, with
> /etc/ssh/sshd_config being identical to /usr/share/openssh/sshd_config,
> dpkg-reconfigure openssh-server does not ask anything:
>
> #
Hi,
How is this supposed to work now? On a fresh stretch install, with
/etc/ssh/sshd_config being identical to /usr/share/openssh/sshd_config,
dpkg-reconfigure openssh-server does not ask anything:
# DEBCONF_DEBUG=developer dpkg-reconfigure openssh-server
debconf (developer): starting
On Thu, 2015-04-30 at 23:00 +0200, Ferenc Wagner wrote:
By usual means do you mean preseeding late_command with a sed script
editing sshd_config?
No I rather meant by using the installation system or configuration
system you use (FAI, puppet, etc.)
Cheers,
Chris.
smime.p7s
Description:
The preseed possibility is actually documented in the jessie release
notes, see
https://www.debian.org/releases/jessie/amd64/release-notes/ch-information.en.html#openssh
I tried to use it in vain, then found this bug.
Please raise its urgency. :)
--
Thanks,
Feri.
--
To UNSUBSCRIBE, email to
What's the problem with simply changing the configuration by usual means
as with all other options which are not specifically handled by debconf?
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
On Apr 25, Marco d'Itri m...@linux.it wrote:
Some environments need PermitRootLogin=yes.
They will configure it no matter what the openssh maintainers think
about it, so please let's save time for everybody and allow this to be
preseeded for new installs as well.
Would you accept a patch to
6 matches
Mail list logo
