From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Tristan Gingold <gingold@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: gdb code signing on darwin?
Date: Fri, 18 Dec 2009 14:36:00 -0000 [thread overview]
Message-ID: <20091218143634.GA21285@bromo.med.uc.edu> (raw)
In-Reply-To: <A3A395B9-DF1B-423C-97FC-9F75D4E761BE@adacore.com>
On Fri, Dec 18, 2009 at 09:46:46AM +0100, Tristan Gingold wrote:
>
> On Dec 17, 2009, at 6:13 PM, Jack Howarth wrote:
>
> > Has anyone made progress on solving the issue of the code signing requirement
> > for FSF gdb on darwin 10.5.8 and Snow Leopard?
>
> Jack,
>
> did you read this wiki entry ?
>
> http://sourceware.org/gdb/wiki/BuildingOnDarwin
>
> I hope it explains how to codesign gdb.
>
> > I am wondering if it is possible to generate a self signed certificate from command
> > line tools which will solve the problem on a per-machine basis.
>
> I don't know if this is possible. But this is out of topic for the gdb mailing list.
> If you know the answer, do not hesitate to complete the wiki entry.
>
> Tristan.
Tristan,
Thanks for the pointer to the wiki. It appears that, in theory, one should be able
to replace the use of the Keychain Access application with explicit calls to the
'security' command line tool. I'll send you an update for the wiki if I can puzzle out
the exact form for such calls.
Jack
next prev parent reply other threads:[~2009-12-18 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 17:13 Jack Howarth
2009-12-18 8:46 ` Tristan Gingold
2009-12-18 14:36 ` Jack Howarth [this message]
2009-12-18 14:39 ` Tristan Gingold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091218143634.GA21285@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=gdb@sourceware.org \
--cc=gingold@adacore.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox