freeipmi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Freeipmi-devel] [bugs #8414] Poor handling of values that can only


From: Albert Chu
Subject: Re: [Freeipmi-devel] [bugs #8414] Poor handling of values that can only be set on certain platforms
Date: Thu, 15 Apr 2004 09:01:41 -0700

> These values are platform dependent. We cant guess if they
> correct. Correct way is to let the BMC report the status.

I think its fair to say BMC configuration support is platform specific,
but potential input values should still be checked.  For example:

###   values: Enable = 0, Disable = 1
non_volatile.per_message_authentication 0

If a vendor does not support "non_volatile.per_message_authentication".
bmc-config should output status from the BMC.

But according to the inline comments, the only available input for this
command is 0 or 1.  Therefore, an input of "9" or "FOO" should result in
a parse error and an error output from bmc-config.

Al

--
Albert Chu
address@hidden
Lawrence Livermore National Laboratory

----- Original Message -----
From: Anand Babu <address@hidden>
Date: Thursday, April 15, 2004 1:53 am
Subject: Re: [Freeipmi-devel] [bugs #8414] Poor handling of values that
can only be set on certain platforms

> ,----
> | tdev3|/home/achur 116>/usr/sbin/bmc-config --diff -f conf-new
> | BMC:  callback_level.max_privilege_auth_type.none 0
> | USER: callback_level.max_privilege_auth_type.none 9
> | 
> | tdev3|/home/achur 117>/usr/sbin/bmc-config --commit -f conf-new
> | 
> | We can atleast check that user has input 0 or 1.
> `----
> These values are platform dependent. We cant guess if they
> correct. Correct way is to let the BMC report the status.
> 
> -- 
> _.|_ 
> (_||_)
> Free as in Freedom <www.gnu.org>
> 
> 
> _______________________________________________
> Freeipmi-devel mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/freeipmi-devel
> 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]