[Seaside] Combating a possible DoS attack.

[Boris Popov]

I would say that if you're thinking of coding DoS protection in your
Squeak server, it's already way too late. Those types of attacks should
never get this far and should be dealt with on the client facing load
balancers such as BIG-IP and the like. This white paper might shed some
light on the subject,

http://www.f5.com/pdf/white-papers/securing-enterprise-wp.pdf

Cheers,

-Boris

-- 
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

boris at deepcovelabs.com

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Nevin Pratt
> Sent: Friday, January 11, 2008 1:21 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Combating a possible DoS attack.
> 
> Randal L. Schwartz wrote:
> >
> >
> > Well, you're trading one kind of DoS for another.
> 
> And that would be worse than the alternative?  Or better?
> >
> > What you need is a bit more smarts... someone coming in from the
same
> > IP for example... a bit harder to fake.
> >
> >
> 
> Do you have some suggested code?
> 
> Nevin
> 
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside