From owner-freebsd-security Tue Apr 14 09:14:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10248 for freebsd-security-outgoing; Tue, 14 Apr 1998 09:14:08 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10197 for ; Tue, 14 Apr 1998 16:13:58 GMT (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id JAA08920; Tue, 14 Apr 1998 09:14:09 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: tweten@frihet.com cc: freebsd-security@FreeBSD.ORG Subject: Re: FreeBSD-SA-98:02.mmap In-reply-to: Your message of "Tue, 14 Apr 1998 09:02:39 PDT." <199804141602.JAA18069@ns.frihet.com> Date: Tue, 14 Apr 1998 09:14:09 -0700 Message-ID: <8917.892570449@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk Huh? That was already acknowledged to be a mistaken repost and we moved on. Just ignore it. > It's been ten days, now, since security advisory FreeBSD-SA-98:02.mmap was > sent, ten days since the signature on it failed to check using my copies of > exmh and pgp, and ten days since I sent a report of that fact to Stefan > Powell. Since then, silence. Nobody else seems to have mentioned any > signature failure, and Powell has also been silent. > > Is it just me? Should I start debugging my copies of exmh and MIT pgp (as > opposed to the crippled pgp in ports)? > -- > David E. Tweten | 2047-bit PGP fingerprint: | tweten@frihet.com > 12141 Atrium Drive | E9 59 E7 5C 6B 88 B8 90 | tweten@and.com > Saratoga, CA 95070-3162 | 65 30 2A A4 A0 BC 49 AE | (408) 446-4131 > Those who make good products sell products; those who don't, sell solutions. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe security" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message