Databases
StackOverflow2013
Postsdbo
POWriting a privileged helper tool with SMJobBless()
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWriting a privileged helper tool with SMJobBless()
    primarykey
    data
    text
    <p>Even though the API has been open since Mac OS X Leopard, there's surprisingly, and unfortunately, very little documentation on how to correctly use <code>SMJobBless()</code> for creating privileged helper tools. There are a lot of gotchas, even when copying code directly from Apple's sample project. Luckily, I've found my way around this, and have gotten the basis for my helper tool working.</p> <p>However, it would seem that <code>SMJobBless()</code> only blesses the tool and copies it over, but doesn't run it. I've included code in my helper tool's <code>main()</code> function that <em>should</em> run, but doesn't (since <code>NSLog()</code> inexplicably doesn't work–according to the tiny bit of information I <em>have</em> found–I've tried <code>syslog()</code>ing some "Hello world" type strings, but nothing appears on the system console). There's no indication that the helper tool is launched at all.<br> The documentation is mostly useless. It simply says that after <code>SMJobBless()</code> is called, the helper tool is 'ready', with no indication of what 'ready' even means.</p> <p>Furthermore, Apple's sample doesn't include any interprocess communication code, and doesn't explain how one is supposed to interact with the helper tool. Do you use Distributed Objects? Mach ports? Who knows? There's no official word on how to do it.</p> <p>So, does anyone have any information on how to get this done? I've confirmed that the helper tool is installed, and authentication works, but I simply can't figure out how to launch the helper tool and communicate with it - there's simply such a gap in the documentation that this is a mystery for now. It's very frustrating; I can't be the <em>only</em> one with this problem (but there's little mention of it <em>anywhere</em>), and <code>SMJobBless()</code> obviously works <em>somehow</em>, since it's what Apple uses.</p> <p>(Please don't mention <code>AuthorizationExecuteWithPrivileges()</code>. I'm not using it: it's deprecated, sure to go away, and is a major security hole. No thanks.)</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USItai Ferber
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWriting a privileged helper tool with SMJobBless()
      1. USItai Ferber
      1. VTBountyStart
    2. VO
      singulars
      1. POWriting a privileged helper tool with SMJobBless()
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWriting a privileged helper tool with SMJobBless()
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWell, just to get started here, XPC Services seems like a good place to start for interprocess communication.
      singulars
      1. POWriting a privileged helper tool with SMJobBless()
      1. USItai Ferber
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload