Re: [RFC] bridge: STP timer management range checking

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Alan Cox
Date: Monday, September 1, 2008 - 1:38 am

> > Seems bogus extra code to me - stops things working that should be

That would be irrelevant. CAP_NET_ADMIN lets you make that size mess
anyway.


Spamming tree isn't secure, news at 11.


If you have CAP_NET_ADMIN you can trivially take out the network unless
it is properly switched.

Now you might want your pretty little GUI and/or config tools to warn
people that their configuration is outside 802 specs but that is a
different matter altogether

Alan
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: ksoftirqd high cpu load on kernels 2.6.24 to 2.6.27-rc ..., Stephen Hemminger, (Sun Aug 31, 10:05 am)
[RFC] bridge: STP timer management range checking, Stephen Hemminger, (Sun Aug 31, 10:43 am)
Re: [RFC] bridge: STP timer management range checking, Stephen Hemminger, (Sun Aug 31, 4:29 pm)
Re: [RFC] bridge: STP timer management range checking, Valdis.Kletnieks, (Sun Aug 31, 7:25 pm)
Re: [RFC] bridge: STP timer management range checking, Alan Cox, (Mon Sep 1, 1:38 am)
Re: [RFC] bridge: STP timer management range checking, David Miller, (Tue Sep 2, 4:41 pm)
Re: [RFC] bridge: STP timer management range checking, David Miller, (Tue Sep 2, 5:28 pm)
[PATCH] bridge: don't allow setting hello time to zero, Stephen Hemminger, (Thu Sep 4, 3:47 pm)
Re: [PATCH] bridge: don't allow setting hello time to zero, Dushan Tcholich, (Mon Sep 8, 2:35 pm)
Re: [PATCH] bridge: don't allow setting hello time to zero, Stephen Hemminger, (Mon Sep 8, 3:33 pm)