Package: openssh-server
Version: 4.3p2-9
Hi,
It seems that when upgrading openssh-server from sarge to etch it
doesn't change the (default) /etc/ssh/sshd_config. When looking at the
diff between the config files, it seems a few things changed.
What I missed was the default "AcceptEnv LANG LC_*"
On Tue, Nov 25, 2008 at 07:39:50PM +, Adam D. Barratt wrote:
>
> The submitter also filed #506846 (CCed) against openssl, which indicates
> the relevant version is 0.9.8g-14.
>
> However, having upgraded one of my amd64 unstable machines to the quoted
> versions of openssl and openssh, I'm un
On Wed, Apr 06, 2011 at 12:45:03AM +0200, Julien Cristau wrote:
> On Sun, Feb 13, 2011 at 00:27:51 +0100, Kurt Roeckx wrote:
>
> > Hi,
> >
> > I would like to upload version 1.0.0(d) to unstable soon. It
> > changes soname, but as far as I know the API is still c
Source: openssh
Version: 1:5.9p1-3
Severity: important
Hi,
I was preparing a new version of openssl 1.0.1, and after I
installed it and wanted to use ssh, I got this:
OpenSSL version mismatch. Built against 107f, you have 1000100f
At some point we removed that check, but then there is this
c
: unstable
Urgency: medium
Maintainer: Debian OpenSSH Maintainers
Changed-By: Kurt Roeckx
Description:
openssh-client - secure shell (SSH) client, for secure access to remote
machines
openssh-client-udeb - secure shell client for the Debian installer (udeb)
openssh-server - secure shell (SSH) server
Package: openssh-server
Version: 1:6.4p1-2
Hi,
After the NMU I did for I upgraded my openssh-client. Later apt
complained that openssh-server was broken because of the Depends
on openssh-client.
The changelog says:
* Use ${binary:Version} rather than ${Source-Version} in openssh-server ->
(1:6.4p1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Adjust check for openssl version (Closes: #732940)
+
+ -- Kurt Roeckx Mon, 23 Dec 2013 10:33:59 +0100
+
openssh (1:6.4p1-1) unstable; urgency=high
* New upstream release. Important changes:
diff -Nru openssh-6.4p1
Package: openssh-client
Version: 1:6.4p1-1
Hi,
When I use ssh with the -i option to use a different key, it seems
to be offering my default key anyway. It seems this is only the
case when an ssh-agent is running. The key that is given isn't
added to the agent.
ssh -v shows:
debug1: identity fi
Package: openssh-client
Version: 1:6.4p1-2
Severity: wishlist
Hi,
I wanted to check which type of keys where in my
~/.ssh/authorized_keys file. I've noticed 2 problems:
- It only returns the first key it finds. I would like it
to return all the keys which it seems to do for things like
the
On Sat, Jun 28, 2014 at 02:23:19PM +0100, Colin Watson wrote:
> Kurt, perhaps it would be worth considering "Breaks: openssh-server (<<
> 1:6.4p1-2)" in libssl1.0.0 in jessie?
I was supposed to add the Breaks again when using the git snapshot,
but forgot about it. I'll add it again.
Kurt
--
Source: openssh
Version: 7.2p2-5
Severity: important
Control: block 827061 by -1
Hi,
OpenSSL 1.1.0 is about to released. During a rebuild of all packages using
OpenSSL this package fail to build. A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted
tags 828475 + patch
thanks
Hi,
I've send a patch to the upstream mailinglist, and it's also
avaiable at:
https://github.com/openssh/openssh-portable/pull/48
Kurt
On Sat, Nov 05, 2016 at 03:40:02PM +, Colin Watson wrote:
> Control: severity 828475 important
> Control: unblock 827061 by 828475
>
> I know it isn't the option you'd prefer, but I've uploaded openssh
> 1:7.3p1-3 with an adjusted Build-Depends ("libssl1.0-dev | libssl-dev
> (>= 0.9.8g)") so t
Hi,
Any update on this?
There are very few packages in testing that still use OpenSSL
1.0.2, and it looks like openssh is the only reason to keep it
around.
Kurt
On Mon, Oct 29, 2018 at 07:11:17PM +0100, Michael Biebl wrote:
> On Mon, 29 Oct 2018 18:22:08 +0100 Kurt Roeckx wrote:
> > reassign 912087 openssh-server,systemd
> > thanks
> >
> > On Mon, Oct 29, 2018 at 08:38:15AM +0100, Kurt Roeckx wrote:
> > > On Mon, Oct
On Tue, Oct 30, 2018 at 10:15:44AM -0400, Theodore Y. Ts'o wrote:
> On Tue, Oct 30, 2018 at 01:18:08AM +0100, Sebastian Andrzej Siewior wrote:
> > Using ioctl(/dev/urandom, RNDADDENTROPY, ) instead writting to
> > /dev/urandom would do the trick. Or using RNDADDTOENTCNT to increment
> > the entropy
On Thu, Nov 01, 2018 at 07:50:35PM -0400, Theodore Y. Ts'o wrote:
> On Thu, Nov 01, 2018 at 11:18:14PM +0100, Sebastian Andrzej Siewior wrote:
> > Okay. So you wrote what can be done for a system with HW-RNG/kvm. On
> > bare metal with nothing fancy I have:
> > [3.544985] systemd[1]: systemd 23
Note that systemd created an option so you can say you trust the
file. But in Debian we don't want to enable that by default. If
you need this in stable, I suggest talk to the systemd maintainer.
Package: ssh
Version: 3.8p1-2
It seems configure is unable to detect res_query and others in
libresolv because resolv.h wasn't included. It changes it to
__res_query, which is how it's called in the lib too.
The reason this works on some architectures is that they have a
weak alias from res_quer
On Wed, May 12, 2004 at 12:26:05PM +1000, Darren Tucker wrote:
> Hi.
> Could you please confirm that the latest patch attached to the
> upstream bug report resolves the problem for you?
>
> The bug is http://bugzilla.mindrot.org/show_bug.cgi?id=867 , and at the
> moment the latest pa
reassign 334590 libssl0.9.8 0.9.8a-1
close 334590 0.9.8a-2
thanks
This is a bug in libssl0.9.8, that is present only in 0.9.8a-1
and has been fixed in 0.9.8a-2 which should be available
tommorrow. You could downgrade to libssl0.9.8 0.9.8-3.
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
21 matches
Mail list logo
