| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20080831230247.76b5a193@lxorguk.ukuu.org.uk> Date: Sun, 31 Aug 2008 23:02:47 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Stephen Hemminger <shemminger@...tta.com> Cc: David Miller <davem@...emloft.net>, "Dushan Tcholich" <dusanc@...il.com>, "Francois Romieu" <romieu@...zoreil.com>, "Robert Hancock" <hancockr@...w.ca>, netdev@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>, bridge@...ts.linux-foundation.org Subject: Re: [RFC] bridge: STP timer management range checking On Sun, 31 Aug 2008 10:43:09 -0700 Stephen Hemminger <shemminger@...tta.com> wrote: > The Spanning Tree Protocol timers need to be set within certain boundaries > to keep the internal protocol engine working, and to be interoperable. > This patch restricts changes to those timers to the values defined in IEEE 802.1D > specification. Why do we care ? You have to be the network administrator to set values, there are cases you may want to be out of the spec and you are privileged. The kernel does need to stop things being done which are fatal but running around restricting privileged administrators who have the ability to bring the network down anyway isn't its job. Seems bogus extra code to me - stops things working that should be allowed too. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists