Hey dudes, I think my mail client screwed up some headers and somehow  
buried my SSL update in the middle of our thread on the list (sure...  
blame the client!) so I wanted to repost to make sure someone else  
saw it. I'd really like it if someone could help test this update out  
a little bit and perhaps even get it moved into trunk? I know Brad is  
busy retiring... so hopefully this will reach the appropriate parties.

The Patch: http://lists.danga.com/pipermail/pe...2007-September/ 
000645.html

Greg Thornton

Senior Developer | EmmaŽ
greg@myemma.com
800.595.4401 or 615.292.5888 x112
615.292.0777 (fax)

Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com

P please consider the environment before printing this e-mail

[ Post a follow-up to this message ]

>
> Hey dudes, I think my mail client screwed up some headers and somehow
> buried my SSL update in the middle of our thread on the list (sure... blam
e
> the client!) so I wanted to repost to make sure someone else saw it. I'd
> really like it if someone could help test this update out a little bit and
> perhaps even get it moved into trunk? I know Brad is busy retiring... so
> hopefully this will reach the appropriate parties.
>
> The Patch: http://lists.danga.com/pipermail/pe.../changeset/708/

Would love to get some eyes and hands on that.  I still don't recommend
Perlbal SSL for production load.

Thanks Greg for motivating this.  


--
Mark Smith / xb95
smitty@gmail.com