At 16.52 1998.02.24, Peter Prymmer wrote: >Another means for doing client side execution of perl is via the >Penguin module - which in turn requires that you have Safe.pm, and PGP.pm >modules. Penguin relies on PGP for implementation of its security >hence requires the full public key trust setup that that entails. I >understand there are a number of ports of PGP to the Mac. I also >recall Felix Gallo's (author of Penguin.pm) frustration with the >Mac end of line issue when it came to socket communications - hence it >was made to work there at one time. I think Bill Middleton had Mac >Penguin clients working against a Penguin daemon running on Solaris. >That was more than a year ago though. Really, getting Penguin to work in MacPerl is not tough. I rewrote the PGP parts to use Apple Events with MacPGP 2.6.3, and hacked up the newline stuff. But it really needs to be rewritten so it does not have a dependency on local newlines at all. I was thinking of submitting patches, but a new version of Penguin has not been uploaded to CPAN since last May, and I don't know if it is still being developed, and what to make patches against, etc. Bottom line: if Netscape 5.0 is to use Penguin or something like it for its security, we'll have to rewrite it to be portable, which shouldn't take too long. I had it working inside of a couple days last fall, but the fixes were somewhat incomplete and very ugly. -- Chris Nandor mailto:pudge@pobox.com http://pudge.net/ %PGPKey=('B76E72AD',[1024,'0824 090B CE73 CA10 1FF7 7F13 8180 B6B6']) #== New Book: MacPerl: Power and Ease ==# #== Publishing Date: Early 1998. http://www.ptf.com/macperl/ ==# ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch