From: Jack Howarth <howarth@bromo.med.uc.edu>
To: gdb@sourceware.org
Subject: codesigning gdb on darwin?
Date: Sat, 03 Apr 2010 23:49:00 -0000 [thread overview]
Message-ID: <20100403234836.GA20199@bromo.med.uc.edu> (raw)
Has anyone managed to codesign a local build of
FSF gdb 7.1 on darwin9/10 using a local self-signed
certificate? In my attempt, I first created and trusted
a self-signed certificate in the KeyChain Access
application, created a Info.plist for the fsf-gdb
(built with a fsf- prefix) using the common name
from that self-signed certificate, built fsf-gdb
using -sectcreate __TEXT __info_plist ./gdb/Info.plist
added on LDFLAGS and then codesigned the installed
binary using the common name of the self signed
certificate. This doesn't provided access to the
required Mach port and 'codesign -d -r - /sw/bin/fsf-gdb'
shows...
Executable=/sw/bin/fsf-gdb
library => identifier "libz.1.2.3.dylib" and anchor apple or identifier "libSystem.B.dylib" and anchor apple
# designated => identifier "org.gnu.gdb" and certificate root = H"eee294eed062a327b66695ce2e283f03c31107da"
Has anyone tried this? Before I sign the fsf-gdb binary
'codesign -d -r' reports it as unsigned, but signing it
seems to silently default to org.gnu.gdb.
Jack
next reply other threads:[~2010-04-03 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 23:49 Jack Howarth [this message]
2010-04-04 1:46 ` Jack Howarth
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=20100403234836.GA20199@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=gdb@sourceware.org \
/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