in reply to Module recommendations to send encrypted email

I don't lose any sleep over perl :)
Just noticed that you're trying to get data from a SSL connection though, which (my understanding) can't really be done. My recollection is that whilst you can establish a SSL connection and pass data to it, the data coming back is encrypted and can't really be read as such. you can receive the data and present it, but can't parse encrypted data for your sanitize requirement.
the hardest line to type correctly is: stty erase ^H
  • Comment on Re: Module recommendations to send encrypted email

Replies are listed 'Best First'.
Re^2: Module recommendations to send encrypted email
by mr_mischief (Monsignor) on Sep 01, 2010 at 01:54 UTC

    I think stevieb means he's doing CGI (or some variation like mod_perl or FastCGI) behind the web server, and that the web connection between the browser and the web server is SSL. There's no need to intercept SSL, the web server will serve a CGI program over an SSL connection with no problems.

      stevieb shouldn't have mentioned the web portion of the work, as it is quite irrelevant ;)

      For completeness, I'm taking care of the web side of things with a mix of CGI::Application, DBIx::Class, a bunch of other modules along with some custom code, which is of course topped off at the presentation layer by Apache. SSL was mentioned to express that the input would be encrypted as it came in, and that the only unencrypted handoff would be in between the acceptance by a CGI app sanitizer/handler from the ass-end of the web server, and a hop (hopefully) right into another piece of code that would PGP it up for me for delivery

      Steve