Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 519078 - net-misc/openssh-6.6.1_p1 reports incorrect version number
Summary: net-misc/openssh-6.6.1_p1 reports incorrect version number
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2014-08-04 19:46 UTC by Mira Ressel
Modified: 2014-08-09 22:13 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mira Ressel 2014-08-04 19:46:16 UTC
The patch between OpenSSH 6.6 and 6.6.1 as applied in OpenSSH's gentoo ebuild changes OpenSSH's version identifier in version.h. But because the ebuild handles version.h specially, that change is lost. Therefore openssh-6.6.1_p1 still reports itself as a 6.6 version.

To fix this, the "epatch "${FILESDIR}"/${P}.patch #508604" line in the ebuild has to be moved in front of the "cp version.h version.h.pristine" line.

This is *not* only an cosmetic bug, as other OpenSSH 6.6.1 instances (non-gentoo OpenSSH instances, that is, see bug 519076) refuse to use the curve25519 key exchange algorithm when communicating with older OpenSSH versions -- and those older versions are identified by means of their version strings.
Comment 1 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2014-08-04 19:57:54 UTC
+*openssh-6.6.1_p1-r2 (04 Aug 2014)
+
+  04 Aug 2014; Lars Wendler <polynomial-c@gentoo.org>
+  -openssh-6.6.1_p1-r1.ebuild, +openssh-6.6.1_p1-r2.ebuild:
+  Fixed version number reported by openssh. Thanks to Luis Ressel for reporting
+  this in bug #519078.
+
Hrm... should not have done the -r1 revbump that quick...
Comment 2 Navid Zamani 2014-08-09 22:12:47 UTC
P.S.: Even worse: SSH flooded my RAM and was killed by the kernel’s OOM handler. So it could even be a kind of buffer overflow with security implications.

All is in flames…
Comment 3 Navid Zamani 2014-08-09 22:13:51 UTC
Ignore my previous comment. Wrong bug. :/