Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Jan 2010 09:14:32 -0500
From:      jhell <jhell@DataIX.net>
To:        Miroslav Lachman <000.fbsd@quip.cz>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: patch for security/openssh-portable
Message-ID:  <alpine.BSF.2.00.1001130911270.68848@pragry.qngnvk.ybpny>
In-Reply-To: <4B4DD2A3.9030000@quip.cz>
References:  <alpine.BSF.2.00.1001130806170.55823@pragry.qngnvk.ybpny> <20100113132953.GH12583@sepulca.yandex.ru> <alpine.BSF.2.00.1001130838240.68848@pragry.qngnvk.ybpny> <20100113134720.GA17770@mx.hs.ntnu.edu.tw> <4B4DD2A3.9030000@quip.cz>

next in thread | previous in thread | raw e-mail | index | archive | help

On Wed, 13 Jan 2010 09:03, 000.fbsd@ wrote:
> Denny Lin wrote:
>> 
>>>> Probably you want VersionAddendum option in sshd_config?
>>>> 
>>> 
>>> No.
>>> 
>>> To my understanding and my last tests VersionAddendum and is only a
>>> Addendum or did not work which spurred me to patch up the Makefile in the
>>> first place.
>> 
>> I put VersionAddendum into sshd_config (with nothing trailing behind it),
>> and it works as expected:
>> telnet foo 22
>> Trying 192.168.0.1...
>> Connected to foo
>> Escape character is '^]'.
>> SSH-2.0-OpenSSH_5.2p1
>> 
>> I'm using OpenSSH from base, but it should be the same with ports.
>
> I am not sure, but I think VersionAddendum is option available only in base 
> SSH, not in portable from ports.
>

That's correct as far as I have seen so far. Personally I think that since 
openssh-portable is in ports why worry about a VersionAddendum at all and 
just patch it with the patch I submitted. Seems like a more secure option 
but that's only me.


-- 

  jhell




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1001130911270.68848>