-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Colin,
Am Do den 3. Dez 2015 um 18:54 schrieb Colin Watson:
> > > You can always override global ssh_config at a per-user level. Your
> > > report is about accessing other systems from an upgraded ssh client,
> > > which means that it is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Do den 3. Dez 2015 um 17:36 schrieb Colin Watson:
> On Thu, Dec 03, 2015 at 05:11:17PM +0100, Klaus Ethgen wrote:
> > Am Do den 3. Dez 2015 um 16:23 schrieb Colin Watson:
> > > (http://www.openssh.com/txt/release-7.1) but it hasn't been yet. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Do den 3. Dez 2015 um 17:57 schrieb Colin Watson:
> On Thu, Dec 03, 2015 at 05:49:19PM +0100, Klaus Ethgen wrote:
> > Am Do den 3. Dez 2015 um 17:36 schrieb Colin Watson:
> > > Ah, so this is not quite accurate. "blowfish" is an SSH1-only
On Thu, Dec 03, 2015 at 05:11:17PM +0100, Klaus Ethgen wrote:
> Am Do den 3. Dez 2015 um 16:23 schrieb Colin Watson:
> > (http://www.openssh.com/txt/release-7.1) but it hasn't been yet. I just
> > diffed 1:6.9p1-3 against 1:7.1p1-1 and there are no changes affecting
> > blowfish; furthermore,
On Thu, Dec 03, 2015 at 04:14:16PM +0100, Klaus Ethgen wrote:
> The new version comes without blowfish cipher.
Erm, no it doesn't? Upstream issued a future deprecation notice
indicating that it will be disabled in future
(http://www.openssh.com/txt/release-7.1) but it hasn't been yet. I just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Do den 3. Dez 2015 um 16:23 schrieb Colin Watson:
> On Thu, Dec 03, 2015 at 04:14:16PM +0100, Klaus Ethgen wrote:
> > The new version comes without blowfish cipher.
>
> Erm, no it doesn't? Upstream issued a future deprecation notice
>
On Thu, 3 Dec 2015 16:14:16 +0100 Klaus Ethgen wrote:
> Source: openssh
> Version: 1:7.1p1-1
> Severity: important
>
> The new version comes without blowfish cipher. That breaks access to
> systems that only allows blowfish cipher. This is a major concern as
> afterwards it is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Source: openssh
Version: 1:7.1p1-1
Severity: important
The new version comes without blowfish cipher. That breaks access to
systems that only allows blowfish cipher. This is a major concern as
afterwards it is not possible anymore to get back
On Thu, Dec 03, 2015 at 06:15:44PM +0100, Klaus Ethgen wrote:
> Am Do den 3. Dez 2015 um 17:57 schrieb Colin Watson:
> > This is true, although I rather suspect that it was in fact an
> > ineffective configuration in the first place (i.e. blowfish was never in
> > fact selected). You could
9 matches
Mail list logo