[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openssh (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openssh (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876910
Hello Clint,
No, upstart jobs are designed to be short and pointed ways to define how
a daemon starts and stops. /etc/init.d is only for backward compatibility
in an upstart system. The ssh init.d script was left the way it is because
of chroot jails for sshd, but it is not necessary for
Excerpts from Jon's message of Tue Oct 18 19:10:18 UTC 2011:
Hello Clint,
No, upstart jobs are designed to be short and pointed ways to define how
a daemon starts and stops. /etc/init.d is only for backward compatibility
in an upstart system. The ssh init.d script was left the way it is
Hello Clint,
No, upstart jobs are designed to be short and pointed ways to define how
a daemon starts and stops. /etc/init.d is only for backward compatibility
in an upstart system. The ssh init.d script was left the way it is because
of chroot jails for sshd, but it is not necessary for
Excerpts from Jon's message of Tue Oct 18 19:10:18 UTC 2011:
Hello Clint,
No, upstart jobs are designed to be short and pointed ways to define how
a daemon starts and stops. /etc/init.d is only for backward compatibility
in an upstart system. The ssh init.d script was left the way it is
** Patch added: Added subroutine to check and create SSH Host keys if they are
not present
https://bugs.launchpad.net/bugs/876910/+attachment/269/+files/ssh_init_fix.patch
** Description changed:
+ System Information
1) lsb_release -rd
Description:Ubuntu 11.10
Release:
Hi Jon, sshd is no longer started and/or stopped with /etc/init.d/ssh
unless you are running inside a chroot.
The host keys are typically generated in the postinstall script of
openssh-server. You can find the copy that should be used for this at
/var/lib/dpkg/info/openssh-server.postinst. So if
Hello Clint,
sshd is no longer started and/or stopped with /etc/init.d/ssh unless you are
running inside a chroot.
I'm new to upstart, so forgive my ignorance, but I thought upstart still used
the init scripts to start and/or stop the jobs.
The host keys are typically generated in the
** Patch removed: Added subroutine to check and create SSH Host keys if they
are not present
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/876910/+attachment/269/+files/ssh_init_fix.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team,
After further testing, determined that my patch did not actually resolve
the issue.
Seems to be an issue with triggering the following sub:
check_rsa_keys () {
#Checks for the existance of RSA keys and generates them if necessary
RSA1_KEY=/etc/ssh/ssh_host_key
Excerpts from Jon's message of Mon Oct 17 23:27:30 UTC 2011:
Hello Clint,
sshd is no longer started and/or stopped with /etc/init.d/ssh unless you
are running inside a chroot.
I'm new to upstart, so forgive my ignorance, but I thought upstart still used
the init scripts to start and/or
** Patch added: Added subroutine to check and create SSH Host keys if they are
not present
https://bugs.launchpad.net/bugs/876910/+attachment/269/+files/ssh_init_fix.patch
** Description changed:
+ System Information
1) lsb_release -rd
Description:Ubuntu 11.10
Release:
Hi Jon, sshd is no longer started and/or stopped with /etc/init.d/ssh
unless you are running inside a chroot.
The host keys are typically generated in the postinstall script of
openssh-server. You can find the copy that should be used for this at
/var/lib/dpkg/info/openssh-server.postinst. So if
Hello Clint,
sshd is no longer started and/or stopped with /etc/init.d/ssh unless you are
running inside a chroot.
I'm new to upstart, so forgive my ignorance, but I thought upstart still used
the init scripts to start and/or stop the jobs.
The host keys are typically generated in the
** Patch removed: Added subroutine to check and create SSH Host keys if they
are not present
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/876910/+attachment/269/+files/ssh_init_fix.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
After further testing, determined that my patch did not actually resolve
the issue.
Seems to be an issue with triggering the following sub:
check_rsa_keys () {
#Checks for the existance of RSA keys and generates them if necessary
RSA1_KEY=/etc/ssh/ssh_host_key
Excerpts from Jon's message of Mon Oct 17 23:27:30 UTC 2011:
Hello Clint,
sshd is no longer started and/or stopped with /etc/init.d/ssh unless you
are running inside a chroot.
I'm new to upstart, so forgive my ignorance, but I thought upstart still used
the init scripts to start and/or
18 matches
Mail list logo
