README - Net::SSLeay Perl module for using Eric Young's implementation of SSL 24.6.1998, Sampo Kellomaki Version 1.01 Note: This module is _the_ `Net::SSLeay' namespace. Eric Young is working on another module, which comes in the perl sub directory of SSLeay-0.9.0, called `SSLeay'. These two modules are not related and perl scripts written for one will not work with the other (though, both modules can be simultaneously installed and your scripts are free to mix and match :-) By popular demand... -------------------- perl -e 'use Net::SSLeay; \ ($p)=Net::SSLeay::get_https("www.cryptsoft.com", 443, "/"); print $p' Prerequisites ------------- perl5.004 - though anything starting from perl5.002 probably works. SSLeay-0.9.0 - nothing earlier works and I do not guarantee that anything later works either (but chances are good, if SSLeay API stabilizes at this version). If the newest version does not work, downgrade to 0.9.0 before asking questions. Installing ---------- gunzip '-g'" line in Makefile.PL and then say make clean perl Makefile.PL make static make test_static gdb perl core gdb perl core # post mortem gdb perl # set break point in SSLeay.xs or in suspect function # in Eric's SSLeay > run yourscript.pl arg arg For gdb'ing make sure gdb finds all the relevant source code. This may mean that you must run perl and SSLeay from the directories where the respective makefiles build them. You can also enable PR and PRN macros in SSLeay.xs and sprinkle even some more around the code to figure out what's happening. If you need to tweak build for some platform, please let me know so I can fix it. Patches and gdb session dumps are also welcome. Recommended reading ------------------- If you run into build problems, especially regarding shared libraries, check your perl documentation, especially the perlxtut(1) man page, which gives excellent tutorial of the build process of XSUBs. perlxtut(1) perlxs(1) perlguts(1) perlcall(1) If you are newbie interested in grabbing web pages from https servers, please read HTTP documentation from http://www.w3c.org before asking trivial questions. --Sampo