Ah, the program requires you to arrange for it to be able to read from FD 3... hmm, I think that is probably a bad design on their part, but...

I don't have time to write a solution at the moment. I guess you are supposed to create a pipe(), fork(), have the child close FD 3 and then use dup2() to make FD 3 the read end of the pipe, and finally exec() 'checkpassword'.

You should be able to do this in Perl, but it may be a little tricky. [I don't think Perl gives the script writer full access to dup2() but you can still fake Perl into closing FD 3 and then just dup() the read end of the pipe with open(ANY,"<&READER")]

Note also that to get the program to read from FD 3 does not require that you be writing to FD 3 (in case their documentation needs to be updated).

        - tye (but my friends call me "Tye")

In reply to (tye)Re3: Writing to descriptor 3 by tye
in thread Writing to descriptor 3 by JPaul

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.