bugtraq - Re: openssh 3.7.1 patched or not?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3F68E65A.30705@quickfire.org>
Date: Wed, 17 Sep 2003 17:55:22 -0500
From: Alex Lambert <alambert@...ckfire.org>
To: Tom Brown <tbrown@...emetal.com>
Cc: bugtraq@...urityfocus.com
Subject: Re: openssh 3.7.1 patched or not?

Tom:

3.7.p1 is 3.7, portable -- it is NOT 3.7.1.

"The portable OpenSSH follows development of the official version, but 
releases are not synchronized. Portable releases are marked with a 'p' 
(e.g. 3.7.1p1). The official OpenBSD source will never use the 'p' 
suffix, but will instead increment the version number when they hit 
'stable spots' in their development."

apl

Tom Brown wrote:
> why does the tarball for openssh-3.7p1.tar.gz have channels.c as:
> 
>   RCSID("$OpenBSD: channels.c,v 1.194 2003/08/29 10:04:36 markus Exp $");
> 
> when the advisory http://www.openssh.com/txt/buffer.adv shows
> 
>    --- channels.c	29 Aug 2003 10:04:36 -0000	1.194
>    +++ channels.c	16 Sep 2003 21:02:40 -0000	1.195
> 
> same problem with buffer.c:
> 
>    RCSID("$OpenBSD: buffer.c,v 1.17 2003/09/16 03:03:47 deraadt Exp $");
> vs
>    --- buffer.c	16 Sep 2003 03:03:47 -0000	1.17
>    +++ buffer.c	16 Sep 2003 21:02:39 -0000	1.18
> 
> it's like 3.7.1 doesn't have all the changes in it?! If I'm right, and
> others have missed this, there may be a lot of folks with a false sense of
> security.
> 
> -Tom
> 
>