Red Hat Bugzilla – Bug 479252
[RHEL5] ipmitool doesn't accept hex codes for k_g
Last modified: 2010-10-23 02:49:53 EDT
The ipmitool shipped with OpenIPMI doesn't allow to specify the non-printable characters in the k_g key even though IPMI specification permits them.
The freeipmi ipmiconsole allows to enter the key beginning with "0x" to be treated as hexadecimal value. OpenIPMI should have this functionality as well.
Version-Release number of selected component (if applicable):
Created attachment 328460 [details]
Here's the code stolen from freeipmi which should allow the user to enter the k_g key as a hex value.
I'd rather add new parameter, say '-K', which accepts only hexa-codes as key. What if an user has key starting with "0x"? The attached patch would do something what the user doesn't expect. Is there any customer request to mimic FreeIPMI behaviour?
(In reply to comment #2)
> I'd rather add new parameter, say '-K', which accepts only hexa-codes as key.
> What if an user has key starting with "0x"? The attached patch would do
> something what the user doesn't expect. Is there any customer request to mimic
> FreeIPMI behaviour?
I think the user would be OK with any option that would allow him to enter the hexa values (but "-K" is taken already). And yes, I believe he would be OK even if we just mimicked the FreeIPMI... The patch is just a suggestion.
Patch sent upstream:
I had to rewrite the hex parsing, stealing from GPL FreeIPMI is not a good idea.
The patch was accepted upstream.
Fixed by rebase to ipmitool-1.8.11
~~ Attention - RHEL 5.4 Beta Released! ~~
RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner!
If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity.
Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value.
Questions can be posted to this bug or your customer or partner representative.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.