> I am 100% certain that this code is not present in the generated object
> code, and don't need further assurance of that:
>
> $ nm -D /usr/bin/ssh /usr/sbin/sshd | grep jpake
> $
OK, good enough for me. Thanks!
Mike
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with
On Thu, Dec 16, 2010 at 04:47:27PM +, Colin Watson wrote:
> On Thu, Dec 16, 2010 at 11:18:09AM +0100, Arne Wichmann wrote:
> > It does not look like jpake is enabled in sid:
>
> That's correct. It's disabled upstream and we haven't enabled it. I
> have no intention of enabling it until upstr
On Fri, Dec 17, 2010 at 02:14:23AM -0500, Michael Gilbert wrote:
> On Fri, Dec 17, 2010 at 12:53 AM, Russ Allbery wrote:
> > Michael Gilbert writes:
> >> I apologize ahead of time for the bts ping pong, but according to the
> >> build log (which is where I checked for my original bug report) jpake
Processing commands for cont...@bugs.debian.org:
> tag 606922 patch
Bug #606922 [openssh] openssh: cve-2010-4478 jpake issue
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
606922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606922
Debian
tag 606922 patch
thanks
On Fri, Dec 17, 2010 at 12:53 AM, Russ Allbery wrote:
> Michael Gilbert writes:
>
>> I apologize ahead of time for the bts ping pong, but according to the
>> build log (which is where I checked for my original bug report) jpake
>> is indeed built.
>
>> $ debuild | grep jpa
Michael Gilbert writes:
> I apologize ahead of time for the bts ping pong, but according to the
> build log (which is where I checked for my original bug report) jpake
> is indeed built.
> $ debuild | grep jpake
jpake.c is run through the compiler, but the entire file is stubbed out if
the prep
Processing commands for cont...@bugs.debian.org:
> reopen 606922
Bug #606922 {Done: Colin Watson } [openssh] openssh:
cve-2010-4478 jpake issue
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
606922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606922
Debian
reopen 606922
thanks
> That's correct. It's disabled upstream and we haven't enabled it. I
> have no intention of enabling it until upstream say it's OK to do so
> (which will probably consist of enabling it by default).
>
> Here's the upstream commit message:
>
> - d...@cvs.openbsd.org 2010/0
It does not look like jpake is enabled in sid:
[130] ~/src/openssh-5.5p1
(518) a...@anhrefn $ find . -type f '!' -name '*.[ch]' |xargs zgrep -i jpake
./ChangeLog: disallow a hostile server from checking jpake auth by sending
an
./ChangeLog: - (dtucker) [auth2-jpake.c auth2.c canohost.h sessio
9 matches
Mail list logo
