From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tom@tromey.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [RFA] Add --enable-codesign to gdb's configure
Date: Fri, 29 Jun 2018 22:19:00 -0000 [thread overview]
Message-ID: <20180629221908.GF2511@adacore.com> (raw)
In-Reply-To: <87bmbupqd4.fsf@tromey.com>
> I'm not sure there's a way for gdb to know whether it's been signed, I
> guess other than invoking codesign itself. I'm going to check this in,
> but if it still needs the change, let me know and I will see if I can
> implement it.
I just gave it a try, and basically, you do it using the -d option
of codesign. I also added -v, to get a bit more information about
the signature -- otherwise, you either get "not signed", or the name
of the executable. Here is an example of both situations:
| $ codesign -dv simple_main
| simple_main: code object is not signed at all
| $ codesign -dv gdb
| Executable=/[...]/gdb
| Identifier=org.gnu.gdb
| Format=Mach-O thin (x86_64)
| CodeDirectory v=20100 size=82012 flags=0x0(none) hashes=2559+2 location=embedded
| Signature size=1572
| Signed Time=23 Feb 2017 09:29:17
| [...]
--
Joel
prev parent reply other threads:[~2018-06-29 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 16:37 Tom Tromey
2018-06-28 17:31 ` Joel Brobecker
2018-06-28 18:31 ` Eli Zaretskii
2018-06-28 19:20 ` Joel Brobecker
2018-06-28 21:12 ` Tom Tromey
2018-06-29 22:19 ` Joel Brobecker [this message]
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=20180629221908.GF2511@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).