From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6858 invoked by alias); 22 Sep 2009 12:59:06 -0000 Received: (qmail 6849 invoked by uid 22791); 22 Sep 2009 12:59:05 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (80.101.103.228) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 22 Sep 2009 12:58:59 +0000 Received: from springer.wildebeest.org ([192.168.1.34]) by gnu.wildebeest.org with esmtp (Exim 4.63) (envelope-from ) id 1Mq4xL-0000NG-Jp; Tue, 22 Sep 2009 14:58:56 +0200 Subject: Re: [ANNOUNCEMENT] GDB 7.0 release process created From: Mark Wielaard To: Jim Ingham Cc: gdb@sourceware.org In-Reply-To: <187A0C0A-28B7-4A51-BE99-47C0F650C1F8@apple.com> References: <20090920143231.GQ7961@adacore.com> <8ac60eac0909200802m45f2675epa6e56001af4b491@mail.gmail.com> <20090920152741.GR7961@adacore.com> <8ac60eac0909200914g39a2d471j601aebd995da1d02@mail.gmail.com> <20090920171154.GT7961@adacore.com> <20090920173607.GA18628@bromo.med.uc.edu> <8ac60eac0909201137h3b357f95hc9471ed186575c06@mail.gmail.com> <20090921043410.GA25454@adacore.com> <20090921125654.GA30075@bromo.med.uc.edu> <3D48AF75-6E1F-401C-8411-8388B7D893B9@elis.ugent.be> <20090921134617.GA30967@bromo.med.uc.edu> <187A0C0A-28B7-4A51-BE99-47C0F650C1F8@apple.com> Content-Type: text/plain Date: Tue, 22 Sep 2009 12:59:00 -0000 Message-Id: <1253624335.20668.32.camel@springer.wildebeest.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00285.txt.bz2 On Mon, 2009-09-21 at 12:18 -0700, Jim Ingham wrote: > The gdb that Apple ships gets special treatment because it is > codesigned by the Apple codesigning authority. I forget all the > details, but I don't think that this treatment is available to non- > Apple codesigned apps. If the gdb binary as conveyed to the user depends on being codesigned by a particular authorization key, then that should be part of the corresponding source code that the user receives. So then the signing authorization keys would be available for any rebuild gdb binary that the user creates. Cheers, Mark