On Sun, 2009-04-12 at 12:21 -0700, Tom Eastep wrote:
> Karsten Bräckelmann wrote:
> > Ah, you got me there -- could you elaborate? Does it actually supersede
> > the Limit action?
>
> Well, I'm not going to remove the Limit action, if that's what you are
> asking.
I didn't assume you would, for backward compatibility -- even if they'd
result in the very same rules.
I guess what I'm asking is, if they are equivalent in functionality and
just a new/shorter/different way to write it. Up until 4.3.7 the LIMIT
column was not even close to the Limit action when it comes to things
like SSH brute-force limiting and still retaining the possibility to ssh
yourself while under attack...
So, are they functionally equivalent? Any advantage, any drawbacks?
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel
