public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Galder Zamarreno <galder@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: PermissionsDarwin wiki fix
Date: Fri, 24 Jan 2020 10:12:00 -0000	[thread overview]
Message-ID: <20200124101241.GF31233@adacore.com> (raw)
In-Reply-To: <CAAcPREvx_caajB-aN5gjz8BNDe8pY0pXFraHHLPf4a5dcxGgOg@mail.gmail.com>

Hello Galder,

> Information is missing in https://sourceware.org/gdb/wiki/PermissionsDarwin
> 
> On macOS 10.15, when you create the certificate, the default alias is set
> to your email address. This needs to be set to gdb-cert too. This is
> implicit in the `security find-certificate -c gdb-cert` output but is not
> specified.
> 
> Without that, when you get to the `codesign --entitlements
> gdb-entitlement.xml -fs gdb-cert $(which gdb)` stage, you get:
> 
> error: The specified item could not be found in the keychain.
> 
> Can someone update the wiki?

Would it be an option for you to update the wiki? All you need
is an account on the wiki and for me to add you to the list of
authorized editors. The purpose of that list of editors is
purely there to stop spamming.

I think it would be more effective if you maintained it yourself.
I could update it for you, but I might not always undertand
your instructions correctly and thus might say something
incorrect or incomplete.

If you are happy to do so, please send me your wiki ID, and I will
set you up (the wiki ID can be sent to me privately).

Thank you,
-- 
Joel

  parent reply	other threads:[~2020-01-24 10:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23 14:22 Galder Zamarreno
2020-01-23 14:41 ` Willgerodt, Felix
2020-01-23 14:50   ` Galder Zamarreno
2020-01-23 19:44   ` Simon Marchi
2020-01-24 10:12 ` Joel Brobecker [this message]
2020-05-29 13:56   ` Galder Zamarreno

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=20200124101241.GF31233@adacore.com \
    --to=brobecker@adacore.com \
    --cc=galder@redhat.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).