On Tue, Feb 11, 2014 at 07:25:19AM +0100, Sven Joachim wrote:
Thank you very much for switching to git! There is a problem with that
change, though: repositories converted from bzr are *huge* in size,
debcheckout openssh downloaded 383.65 MiB and took a while to
complete. Running git gc
Package: openssh-client
Version: 1:6.5p1-1
Severity: important
Tags: upstream
Hi Colin,
Since the 6.5p1 update, uppercase Host specifications in .ssh/config
don't work anymore:
I had the following in my .ssh/config that allowed me to correctly
connect with 6.4p1:
Host Icterus
On Tue, Feb 11, 2014 at 12:32:34AM +0100, Michael Biebl wrote:
I noticed that you added systemd .service files in openssh 1:6.5p1-1.
Thanks a lot for that!
There are a few issues though that I noticed which I'd like to discuss.
SSH supports two modes:
a/ The traditional way of being
On Tue, Feb 11, 2014 at 11:56:08AM +0100, Didier Raboud wrote:
Since the 6.5p1 update, uppercase Host specifications in .ssh/config
don't work anymore:
Yes, I happened to spot a fix for this go by in the Arch packages. In
my next upload I'll cherry-pick the same patch from upstream as they
On Tue, Feb 11, 2014 at 01:26:29AM +0100, Christoph Anton Mitterer wrote:
As far as I'd understand the changelog entry
* Generate ED25519 host keys on fresh installations. Upgraders who wish
to add such host keys should manually add 'HostKey
/etc/ssh/ssh_host_ed25519_key' to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 11 Feb 2014 11:28:35 +
Source: openssh
Binary: openssh-client openssh-server ssh ssh-krb5 ssh-askpass-gnome
openssh-client-udeb openssh-server-udeb
Architecture: source i386 all
Version: 1:6.5p1-2
Distribution: unstable
openssh_6.5p1-2_i386.changes uploaded successfully to ftp-master.debian.org
along with the files:
openssh_6.5p1-2.dsc
openssh_6.5p1-2.debian.tar.xz
openssh-client_6.5p1-2_i386.deb
openssh-server_6.5p1-2_i386.deb
ssh_6.5p1-2_all.deb
ssh-krb5_6.5p1-2_all.deb
openssh_6.5p1-2_i386.changes uploaded successfully to localhost
along with the files:
openssh_6.5p1-2.dsc
openssh_6.5p1-2.debian.tar.xz
openssh-client_6.5p1-2_i386.deb
openssh-server_6.5p1-2_i386.deb
ssh_6.5p1-2_all.deb
ssh-krb5_6.5p1-2_all.deb
ssh-askpass-gnome_6.5p1-2_i386.deb
Your message dated Tue, 11 Feb 2014 12:33:48 +
with message-id e1wdcx6-0004mw...@franck.debian.org
and subject line Bug#738619: fixed in openssh 1:6.5p1-2
has caused the Debian Bug report #738619,
regarding Upper-case Host specification in .ssh/config doesn't work anymore in
6.5p1
to be
On Tue, 2014-02-11 at 11:19 +, Colin Watson wrote:
Oops, right.
No real problem... I'm just a perfectionist... even regarding typos in
changelogs ;)
I'll retroactively correct the changelog. (You still need
to add the HostKey entry manually on upgrades.)
Actually I didn't understand
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 11 Feb 2014 11:28:35 +
Source: openssh
Binary: openssh-client openssh-server ssh ssh-krb5 ssh-askpass-gnome
openssh-client-udeb openssh-server-udeb
Architecture: source i386 all
Version: 1:6.5p1-2
On Tue, Feb 11, 2014 at 01:30:35PM +0100, Christoph Anton Mitterer wrote:
On Tue, 2014-02-11 at 11:19 +, Colin Watson wrote:
I'll retroactively correct the changelog. (You still need
to add the HostKey entry manually on upgrades.)
Actually I didn't understand that at all.. why do you
* Source package: openssh
* Version: 1:6.5p1-2
* Architecture: armhf
* State: failed
* Suite: sid
* Builder: hoiby.debian.org
* Build log:
https://buildd.debian.org/fetch.cgi?pkg=openssharch=armhfver=1%3A6.5p1-2stamp=1392133808file=log
Please note that these notifications do not
On Tue, Feb 11, 2014 at 05:39:26PM +0100, Axel Beckert wrote:
~ # ssh-add
Enter passphrase for /home/abe/.ssh/id_rsa:
Identity added: /home/abe/.ssh/id_rsa (/home/abe/.ssh/id_rsa)
Enter passphrase for /home/abe/.ssh/id_dsa:
Identity added: /home/abe/.ssh/id_dsa (/home/abe/.ssh/id_dsa)
* Source package: openssh
* Version: 1:6.5p1-2
* Architecture: kfreebsd-i386
* State: failed
* Suite: sid
* Builder: fils.debian.org
* Build log:
https://buildd.debian.org/fetch.cgi?pkg=openssharch=kfreebsd-i386ver=1%3A6.5p1-2stamp=1392139768file=log
Please note that these notifications
* Source package: openssh
* Version: 1:6.5p1-2
* Architecture: kfreebsd-amd64
* State: failed
* Suite: sid
* Builder: fayrfax.debian.org
* Build log:
https://buildd.debian.org/fetch.cgi?pkg=openssharch=kfreebsd-amd64ver=1%3A6.5p1-2stamp=1392140964file=log
Please note that these
Colin Watson wrote:
On Tue, Feb 11, 2014 at 12:32:34AM +0100, Michael Biebl wrote:
Do you think it would be helpful if we write a small paragraph in
README.Debian explaining the two different modes and how to enable/use them?
I already did. :-)
systemd socket activation
On Tue, Feb 11, 2014 at 10:18:52PM +0200, Uoti Urpala wrote:
Colin Watson wrote:
I already did. :-)
systemd socket activation
-
If you want to reconfigure systemd to launch sshd using socket activation,
then you can run:
I think this would
On Tue, 2014-02-11 at 21:52 +, Colin Watson wrote:
On Tue, Feb 11, 2014 at 10:18:52PM +0200, Uoti Urpala wrote:
I think this would benefit from a more clear explanation of the
OK. I've pushed this commit:
On Tue, Feb 11, 2014 at 03:37:28PM -0800, Shawn Landden wrote:
After upgrading to sid I ended up getting only the socket-activated
sshd, and having ssh.service fail to the port being already taken by
ssh.socket. I had to
systemctl disable ssh.socket
Yes, Michael spotted that earlier in this
On Wed, Feb 12, 2014 at 01:15:39AM +0200, Uoti Urpala wrote:
On Tue, 2014-02-11 at 21:52 +, Colin Watson wrote:
OK. I've pushed this commit:
http://anonscm.debian.org/gitweb/?p=pkg-ssh/openssh.git;a=commitdiff;h=a92ab9ee301bc9196bb20f4923886f021f070521
Let me know if that
On Wed, 2014-02-12 at 00:12 +, Colin Watson wrote:
On Wed, Feb 12, 2014 at 01:15:39AM +0200, Uoti Urpala wrote:
At least a script from another package could trigger a daemon-reload
call between unpacking openssh-server and configuring it. So the system
could at least be in a somewhat
On Wed, Feb 12, 2014 at 02:48:59AM +0200, Uoti Urpala wrote:
I think you've misunderstood something about how systemd sysvinit
compatibility works. SSH started through the compatibility layer DOES
count as active, and is under systemd control - which is why for
example dependencies between
Colin Watson cjwat...@debian.org writes:
On Wed, Feb 12, 2014 at 02:48:59AM +0200, Uoti Urpala wrote:
I think you've misunderstood something about how systemd sysvinit
compatibility works. SSH started through the compatibility layer DOES
count as active, and is under systemd control - which
On Tue, 2014-02-11 at 17:33 -0800, Russ Allbery wrote:
Colin Watson cjwat...@debian.org writes:
Aha, I see. Just inverting the check wouldn't be the right fix, IMO,
but I'll retest this and sort out a proper fix. Thanks for the
clarification.
Not quite right, as in it would enter the
Package: openssh-client
Version: 1:6.5p1-2
Severity: normal
Client and server use the same version.
md@bongo:~$ ssh -vvv -a -x -W server2.example.net:22 localhost
OpenSSH_6.5, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /home/md/.ssh/config
debug3: cipher ok: arcfour128
Uoti Urpala uoti.urp...@pp1.inet.fi writes:
Simplest fix would be to stop sshd in preinst, but then it would of
course be nice to have a way to tell dpkg to not wait arbitrarily long
after that before running postinst...
Yes, that's exactly why the openssh-server package doesn't do this.
Am 12.02.2014 03:09, schrieb Uoti Urpala:
On Tue, 2014-02-11 at 17:33 -0800, Russ Allbery wrote:
Colin Watson cjwat...@debian.org writes:
Aha, I see. Just inverting the check wouldn't be the right fix, IMO,
but I'll retest this and sort out a proper fix. Thanks for the
clarification.
Not
28 matches
Mail list logo
