Subject: re: new sysctl - privilaged ports runtime option?
To: Joe Reed <jnr@po.cwru.edu>
From: matthew green <mrg@eterna.com.au>
List: tech-kern
Date: 08/08/2002 13:25:21
   i've added a check such that the sysctl fail with EOPNETSUPP when securelevel 
   is >0. i did this by simply checking the value of the integer securelevel.  
   is there a better way to check the securelevel value?  or just directly 
   referencing the value good enough?
   
   also, to go along with the naming of the kernel option, i've changed the 
   sysctl name from reservedports to privports.  the functionality remains the 
   same (other than the securelevel check).  does that make sense?
   
   On Tuesday 06 August 2002 23:42, matthew green wrote:
   > it seems to me maybe this should depend on securelevel.  perhaps
   > only securelevel > 1, so that it still works for a default install
   > but someone who really care about securelevel (and thus sets it
   > to > 1) will not have this option suddenly enabled on them...


this all seems fine, but i think it would be better to check for
securelevel > 1, not >= 1...


.mrg.