Hide Forgot
Description of problem: We previously rebased hivex in RHEL 6.1 (bug 642631). It is likely to be a good idea to rebase again. Note that the hivex library is API and ABI compatible upstream, so there is no possibility of a regression from rebasing. Here are some of the significant fixes we would get by rebasing: - The syntax for deleting registry keys has been fixed so that standard Microsoft format .reg files work correctly (bug 737944). - hivexml output is now safe when the hive contains XML metacharacters. - Fix 2 x segfaults in the OCaml bindings. - Compat fixes for new Python versions. - Fix for Perl 5.14. - Ruby bindings have been added. Not clear if we would enable these for RHEL, but it's a possibility. - Extra APIs (backwards compatible) for getting last modified timestamps of registry nodes, getting the physical offset of hive data. - Add --unsafe-printable-strings option. This is the requirement for libguestfs rebase (bug 719879). - Fixed endianness bugs which affect RHEL on non-x86-like platforms. - Fix buggy Python-on-32-bit bindings (affects RHEL). - Fix segfault in hivex_value_multiple_strings where it could read uninitialized data or over the end of the file (affects RHEL). - Handle incorrect UTF-16 data that could cause it to read an uninitialized byte (affects RHEL). - hivex_value_value returns real length of buffer instead of whatever the file declares (affects RHEL, possible security issue). - Fix use-after-free in hivex_close (affects RHEL).- (For a complete list of changes, see http://git.annexia.org/?p=hivex.git;a=log)
*** This bug has been marked as a duplicate of bug 734208 ***