Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 1 Mar 2003 08:18:34 -0600
From:      "Jacques A. Vidrine" <nectar@FreeBSD.org>
To:        cjclark@alum.mit.edu
Cc:        KIMURA Yasuhiro <yasu@utahime.org>, freebsd-security@FreeBSD.org
Subject:   Re: Updated OpenSSL patches
Message-ID:  <20030301141834.GA75133@madman.celabo.org>
In-Reply-To: <20030301011427.GA66850@blossom.cjclark.org>
References:  <20030227005035.GA99420@madman.celabo.org> <20030228.010621.58864322.yasu@utahime.org> <20030227160944.GA3238@madman.celabo.org> <20030228.014901.81279435.yasu@utahime.org> <20030227235901.GA84362@blossom.cjclark.org> <20030228140201.GA61833@madman.celabo.org> <20030301011427.GA66850@blossom.cjclark.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 28, 2003 at 05:14:27PM -0800, Crist J. Clark wrote:
> On Fri, Feb 28, 2003 at 08:02:01AM -0600, Jacques A. Vidrine wrote:
> > Huh.  *boggle*
> > Applying the patch to an entire source tree succeeds as well.
> > e.g.
> > 
> >   cvs -Q co -rRELENG_4_7_0_RELEASE src
> 
> I still get the errors when I apply against a whole, freshly
> checked-out tree. README and Makefile do not get patched and I end up
> with README.rej and Makefile.rej in src. In addition, mem_clr.c ends
> up in src, although the patch succeeds, and no copy resides in
> src/crypto/openssl/crypto... Although mem.c and mem_dbg.c in the same
> directory get patched fine. This is really weird.
> 
>   $ patch -v
>   Patch version 2.1

Maddening.
Hmm, I can't remember now whether or not I used `-P' when checking out,
but I likely did ... I wonder if that makes a difference in this case.
 
> > You didn't write anything after that last `zcat ...' line, but I'm led
> > to believe that getting rid of the relative path in the patch file
> > resolved the problem?  If that is the case, I will remove that path
> > from the existing patches and re-sign the patches.
> 
> Yeah. Clearing that path worked.

I've done that and re-uploaded the patches.

> > Thanks for narrowing down the problem!  Now, I don't suppose you want
> > to find and fix the issue in patch(1), do you? :-)
> 
> Patch(1) is not pretty. I definately am not going to have time this
> weekend.

:-)
Cheers,
-- 
Jacques A. Vidrine <nectar@celabo.org>          http://www.celabo.org/
NTT/Verio SME          .     FreeBSD UNIX     .       Heimdal Kerberos
jvidrine@verio.net     .  nectar@FreeBSD.org  .          nectar@kth.se

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message




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