[Freeipmi-devel] [bugs #8724] bmc-config does not check for legit input from user on key-value pair

[Balamurugan]

This mail is an automated notification from the bugs tracker
 of the project: FreeIPMI.

/**************************************************************************/
[bugs #8724] Latest Modifications:

Changes by: 
                Balamurugan <address@hidden>
'Date: 
                Thu 09/02/04 at 23:37 (GMT)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Fixed
         Assigned to | None                      | balamurugan
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
new bmc-config supports data validation






/**************************************************************************/
[bugs #8724] Full Item Snapshot:

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=8724>
Project: FreeIPMI
Submitted by: Albert Chu
On: Wed 04/28/04 at 16:46

Category:  bmc-config
Severity:  3 - Ordinary
Item Group:  User Interface Bug
Resolution:  Fixed
Privacy:  Public
Assigned to:  balamurugan
Status:  Closed


Summary:  bmc-config does not check for legit input from user on key-value pair

Original Submission:  tdev3|/home/achu 30>/usr/sbin/bmc-config --checkout | 
grep flow_control
flow_control 0
tdev3|/home/achu 31>/usr/sbin/bmc-config --commit -k flow_control=57
tdev3|/home/achu 32>/usr/sbin/bmc-config --checkout | grep flow_control
flow_control 1


Follow-up Comments
------------------


-------------------------------------------------------
Date: Thu 09/02/04 at 23:37         By: Balamurugan <balamurugan>
new bmc-config supports data validation

-------------------------------------------------------
Date: Thu 05/13/04 at 00:45         By: Ian Zimmerman <itz>
This (and #8725 which is the same) will be hard to fix
because there's no shared knowledge in the fish code about
which values are valid for which keys.

Perhaps the checkout code should output the comment line
preceding a setting in a fixed, easily parsed format; then
the commit code could get the information from there.













For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=8724>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/