search for: unsafe_printable_strings

...registry hive is large / bloated. +This behavior can also be achieved by providing a negative max depth. + =back =cut @@ -271,6 +285,7 @@ GetOptions ("help|?" => \$help, "encoding=s" => \$encoding, "unsafe-printable-strings" => \$unsafe_printable_strings, "unsafe" => \$unsafe, + "max-depth=i" => \$max_depth, ) or pod2usage (2); pod2usage (1) if $help; @@ -332,7 +347,8 @@ if ($merge) { # --merge (reg_import) reg_export ($h, $key, \*STDOUT, prefix =>...

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

This new option allows you to only export what you care about from a registry hive by specifying a max recursion depth. Michael Meyer (1): hivexregedit: add --max-depth option for exports perl/lib/Win/Hivex/Regedit.pm | 14 ++++++++++++-- regedit/hivexregedit | 18 +++++++++++++++++- 2 files changed, 29 insertions(+), 3 deletions(-) -- 2.14.3 (Apple Git-98)

...nnect|c=s" => \$uri, "debug|d" => \$debug, @@ -229,7 +229,9 @@ GetOptions ("help|?" => \$help, "merge" => \$merge, "encoding=s" => \$encoding, "unsafe-printable-strings" => \$unsafe_printable_strings, - ) or pod2usage (2); + "long-options" => \&display_long_options, + "short-options" => \&display_short_options); +GetOptions (%opts) or pod2usage (2); pod2usage (1) if $help; if ($version) { my $g = Sys::Guestfs->new (); @@ -238,...