site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Thanks to all for your replies. I've tried Jean-Daniel's excellent lldb steps for fully trusting a self-signed certificate, and I have today also tried creating a different code signing certificate from an external CA (not a public one, just company test one, but still set up such that the Mac has an entry for the CA as a trusted root.) In both cases this has now removed the need to interactively authenticate once per login, but I still get the same problem as I have always had: if I run from Terminal using sudo, the task_for_pid() call succeeds. If I run any other way, either from Terminal not using sudo, or interactively from the Finder, I get told that I do have the correct privilege, but then the call fails. (Output from the code in my original post; I won't re-post it again) system.privilege.taskport acquired com.apple.TextEdit pid is <id> Failed; machErr=(os/kern) failure (5) Is there a way to get a bit more diagnostic info on what is causing the failure that might give me a clue? Thanks, -- Ben. On 13 Oct 2011, at 09:23, Jean-Daniel Dupas wrote:
Not true. It's perfectly possible to use a self signed cert, as long as it is properly installed.
I'm using custom lldb build that required to be signed to works, and didn't have issue with a self signed cert.
The instruction to sign lldb are available here. The interesting section is the one that start with:
«The next steps are necessary on SnowLeopard, but are probably because of a bug how Keychain Access makes certificates. [Note: These also apply for Lion.]»
_______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com