Displaying 9 results from an estimated 9 matches for "qudsi".
Did you mean:
quasi
2014 Nov 11
4
[libhivex] Memory leak in hivex_node_delete_child?
[This email is either empty or too large to be displayed at this time]
2014 Oct 30
0
Re: [libhivex] Undefined behavior when accessing invalid (too small) registry hives
On Wed, Oct 29, 2014 at 09:26:30PM -0500, Mahmoud Al-Qudsi wrote:
> On Oct 29, 2014, at 3:39 PM, Richard W.M. Jones <rjones@redhat.com> wrote:
> >
> >> Or is it expected that certain sanity checks would be performed prior to
> >> passing along any files to libhivex? What would those checks be?
> >
> > No, hive...
2014 Oct 30
4
Re: [libhivex] Undefined behavior when accessing invalid (too small) registry hives
On Oct 29, 2014, at 3:39 PM, Richard W.M. Jones <rjones@redhat.com> wrote:
>
>> Or is it expected that certain sanity checks would be performed prior to
>> passing along any files to libhivex? What would those checks be?
>
> No, hivex should definitely have those checks.
>
> I'll have a proper look at this in the morning.
>
> Thanks,
>
> Rich.
2013 Feb 07
1
[libhivex] Patch implementing hivex_node_get_child_deep
...be added to my patch (please).
I apologize for not taking the time to ask whether or not such a new API
function would be welcome. As it was, I needed this code for my own
purposes, so I am sharing it here on the mailing list in case it proves to
be helpful to anyone else.
Thank you,
Mahmoud Al-Qudsi
NeoSmart Technologies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libguestfs/attachments/20130207/b6f783ce/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Implement...
2014 Oct 29
2
[libhivex] Undefined behavior when accessing invalid (too small) registry hives
...location(s) to place range-checking would be; is
there anything smarter than plastering checks at every read/write to the
registry file?
Or is it expected that certain sanity checks would be performed prior to
passing along any files to libhivex? What would those checks be?
Thank you,
Mahmoud Al-Qudsi
NeoSmart Technologies
2014 Oct 29
0
Re: [libhivex] Undefined behavior when accessing invalid (too small) registry hives
On Wed, Oct 29, 2014 at 10:43:59AM -0500, Mahmoud Al-Qudsi wrote:
> Hello all,
>
> I know that one of the original design goals of libhivex was to be
> resilient to corrupt, invalid, or malicious registry hives. I've
> encountered some undefined behavior in libhivex when attempting to open
> registry files that are too small. I'm...
2014 Nov 11
0
Re: [libhivex] Memory leak in hivex_node_delete_child?
Hi,
On Monday 10 November 2014 18:28:52 Mahmoud Al-Qudsi wrote:
> I’m not able to pin it myself from a brief look, but it seems that
> under certain conditions a call to hivex_node_delete_child can cause
> the allocations from _hivex_get_children to not be freed properly?
>
> I know that if the return value of _hivex_get_children is -1, n...
2014 Nov 11
0
Re: [libhivex] Memory leak in hivex_node_delete_child?
> On Nov 11, 2014, at 5:36 AM, Mahmoud Al-Qudsi <mqudsi@neosmart.net> wrote:
> I'll test it and be back.
And it works perfectly.
Thanks,
Mahmoud
2014 Nov 11
0
Re: [libhivex] Undefined behavior when accessing invalid (too small) registry hives
> On Nov 11, 2014, at 1:57 AM, Richard W.M. Jones <rjones@redhat.com> wrote:
>
> Yes I was also meaning to do that after reading lcamtuf's postings.
Yup. That's the one.
> I just started a run now .. Will let it run for a few days and report
> any issues on the list.
Thank you. Do you mind running it under valgrind to catch out-of-bound reads?
Mahmoud