Displaying 3 results from an estimated 3 matches for "hive_t_qword".
Did you mean:
hive_t_dword
2013 Jun 19
2
[PATCH] Relax size checks for integer types
...mp;& t != hive_t_dword_be) || len != 4) {
+ if ((t != hive_t_dword && t != hive_t_dword_be) || len < 4) {
free (data);
errno = EINVAL;
return -1;
@@ -1650,7 +1650,7 @@ hivex_value_qword (hive_h *h, hive_value_h value)
if (data == NULL)
return -1;
- if (t != hive_t_qword || len != 8) {
+ if (t != hive_t_qword || len < 8) {
free (data);
errno = EINVAL;
return -1;
--
1.8.3.1
2011 Apr 13
1
[PATCH hivex] maint: split long lines
...->value_dword (h, opaque, node, values[i], t, len, key, i32) == -1)
+ vtor->value_dword (h, opaque, node, values[i],
+ t, len, key, i32) == -1)
goto error;
break;
}
@@ -1647,7 +1678,8 @@ hivex__visit_node (hive_h *h, hive_node_h node,
case hive_t_qword: {
int64_t i64 = hivex_value_qword (h, values[i]);
if (vtor->value_qword &&
- vtor->value_qword (h, opaque, node, values[i], t, len, key, i64) == -1)
+ vtor->value_qword (h, opaque, node, values[i],
+ t, len, key, i64) == -1)...
2013 Jul 25
19
[PATCH hivex 00/19] Fix read/write handling of li-records.
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.