Displaying 3 results from an estimated 3 matches for "reg_export_node".
2017 Dec 29
0
[PATCH 1/1] hivexregedit: add --max-depth option for exports
...644
--- a/perl/lib/Win/Hivex/Regedit.pm
+++ b/perl/lib/Win/Hivex/Regedit.pm
@@ -487,11 +487,12 @@ sub reg_export
{
my $h = shift;
my $key = shift;
+ my $fh = shift;
my $node = _node_lookup ($h, $key);
croak "$key: path not found in this hive" unless $node;
- reg_export_node ($h, $node, @_);
+ reg_export_node ($h, $node, $fh, 0, @_);
}
=head2 reg_export_node
@@ -510,8 +511,17 @@ sub reg_export_node
my $h = shift;
my $node = shift;
my $fh = shift;
+ my $depth = shift;
my %params = @_;
+ my $max_depth = $params{max_depth};
+ if (defi...
2017 Dec 29
2
[PATCH 0/1] hivexregedit: add --max-depth option for exports
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)
2017 Feb 16
6
[PATCH v4 0/5] hivex: handle corrupted hives better.
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