Whatever is building the command line is doing it wrong:

-passin pass:'test me'

[download]

... should likely be

-passin 'pass:test me'

[download]

For example, the following line building some command line will also not deal well with spaces in your password:

$cmd = "-des3 -passout pass:$args->{keypass} ".$cmd if defined($args->
+{keypass});

[download]

Also, this line:

my $common_args = "-$args->{digest} -days $args->{days} ".
" -key $cakey -passin pass:$args->{keypass}";

[download]

As a general rule, if it doesn't work on the command line/shell prompt, there is very little that IPC::Run can do to make it work either.

In reply to Re^2: IPC::Run command is correctly constructed but does not have effect by Corion
in thread IPC::Run command is correctly constructed but does not have effect by byrnejb

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.