That's my fault, I posted exec as that was my last test live.
I had tried backticks, system and exec.
I recall last time I attempted this I was going after the IPC2/3 modules without success. I have not or did not notice IPC::Run itself. I shall give that a look when I get home.
I understand that not liking io::socket::SSL is just a personal choice. Until I understand perl better, I want to stay away from sysread and I was "forced" to use that with IO::S::SSL. Doing multiple handles without threading knowledge, sysread would read whatever was on the buffer. And the buffer itself would cause me issues for size and I spent more time dealing with it than I cared to.
</p
It comes down to, using openssl raw in terminal, I'm able to do everything i want in about 25 seconds. Using io:s:SSL, it takes me a lot longer and I spend time troubleshooting all types of noon bugs.
That's why I was hoping to pipe in and out directly to openssl. I'll check out IPC again when I'm home.
Thanks.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.