[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Libcdio-devel] buffer overflow/memory corruption in udf_readdir()

From: Pete Batard
Subject: Re: [Libcdio-devel] buffer overflow/memory corruption in udf_readdir()
Date: Tue, 17 Jan 2012 14:33:13 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0

On 2012.01.17 13:51, Thomas Schmitt wrote:
But if you are investing time into the UDF topic,

Well, that will depend on whether I need it or not. If I can extract UDF files OK with the current libcdio, even if it requires an ugly workaround, I probably won't look that deep into it (time constraints).

As said, my target on the first hand is production, not reading.
libisofs reads ECMA-119+RockRidge and Joliet. So why not UDF ?
At least we could share knowledge.

I'd have to considerably ramp up my knowledge on those, as it is currently nil...

What i am lacking yet is a comprehensice overview how to get from
UDF anchor to directory tree, file entries, and file content. There
seem to be several stages of volumes and partitions involved.
(I wanted to explore libcdio/src/lib/udf/udf_fs.c when i got distracted
  by endeavors which promised more fun.)

Have you had a look at what 7-zip source does (7z/CPP/7zip/Archive/Udf/)? It's a C++ Windows COM component, therefore heavily Windows oriented, but the license is LGPL v2.1 or later and you may find some information there.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]