On Sun, 09 Jan 2005 20:59:46 -0800 Wes wrote: WH> Robert> mention new option to disable set requests WH> WH> Um, what's the purpose of this? I am some what hesitant about WH> implementing something like this since I'd bet (not having looked at WH> the code admittedly) that it doesn't properly change the VACM tables WH> as well?
No it doesn't. All it does is replace the vacm check call with a return not writable. The eventual idea would be to exclude set processing code, also reducing library/agent footprint. WH> Why are we even trying to make this an option in the first place? WH> It's taken SNMP years to try and become something usable for SETs and WH> this seems like a step backwards not forwards. It came up in IRC. Someone wanted a read-only system that couldn't turn into a read-write system if misconfigured. It's not the default. I see it akin to --disable-mibs. If they don't need the functionality, why have it in the library/app? -- Robert Story; NET-SNMP Junkie Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
