in reply to Module with ioperm/inb/outb usage?

Your assessment of the situation is commendably clear and correct.

The usual way to deal with situations like this is to have a child process which runs suid from a root owned file, and is carefully constructed to only assert high privilege where needed. A typical example is a device driver which asserts privilege only to change state, and serializes inputs by connection, preventing interactions.

XS or Inline::C are very likely to be useful in obtaining that. Neither is portable while there exists an OS which officially considers any but their own programming to be pure poison.

After Compline,
Zaxo

Replies are listed 'Best First'.
Re: Re: Module with ioperm/inb/outb usage?
by LogicalChaos (Beadle) on Dec 26, 2002 at 16:18 UTC
    Thanks for the confirmation.

    Interestingly enough, you answered a slightly different question than I thought I asked. I was thinking of creating the executables from a standard Makefile, in addition to installing the module.

    Your comment opened the possibility of still having all code within the module, and having the Makefile change permissions on the appropriate files, rather than building the executables directly.

    Thanks,
    Rob