search for: hivex_open_write

..."close", (RErrDispose, [AHive]), diff --git a/lib/handle.c b/lib/handle.c index d33c1d0..a4982dd 100644 --- a/lib/handle.c +++ b/lib/handle.c @@ -83,6 +83,7 @@ hivex_open (const char *filename, int flags) DEBUG (2, "created handle %p", h); h->writable = !!(flags & HIVEX_OPEN_WRITE); + h->unsafe = !!(flags & HIVEX_OPEN_UNSAFE); h->filename = strdup (filename); if (h->filename == NULL) goto error; diff --git a/lib/hivex-internal.h b/lib/hivex-internal.h index 26f4964..9a497ed 100644 --- a/lib/hivex-internal.h +++ b/lib/hivex-internal.h @@ -41,6 +41,7 @...

The following patches address issues when dealing with hives that have corrupted data in them but are otherwise readable/writable. Those were found on some rather rare Windows installations that seem to work fine but current hivex fails to even open. Those patches change hivex to simply log and ignore such "corrupted" regions instead of aborting because the caller might be looking at

Map the HIVEX_OPEN_UNSAFE flag into the libguestfs API and use it in various places. Rich.

This adds most of the hivex APIs directly to the libguestfs API, so that you can read and write Windows Registry hive files from libguestfs without needing to download and upload hive files from the guest. This is analogous to how Augeas APIs are exposed already (guestfs_aug_*) Also, inspection is now done using the new APIs, which fixes the following bug:

This is, hopefully, a full fix for handling of li-records. See: https://bugzilla.redhat.com/show_bug.cgi?id=717583 https://bugzilla.redhat.com/show_bug.cgi?id=987463 Rich.