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

In reply to Re: Module with ioperm/inb/outb usage? by Zaxo
in thread Module with ioperm/inb/outb usage? by LogicalChaos

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.