Re: [Libcdio-devel] private udf information

[Rocky Bernstein]

On Sun, Oct 17, 2010 at 8:42 PM, Shaya Potter <address@hidden> wrote:

> in libcdio a bunch of information is kept private and not readily available
> to programs, what I'm concerned about is basically the start/length of a
> file.
>
>
This seems reasonable. In general the philosophy behind opaque structures
is that the information is very implementation specific and it is possible
the fields may change around from version to version. So compatibility would
be made worse than it is now  if programmers were to use those the exact
format of the structure. (And things are far from ideal now -- ask any
packager of libcdio.)

That said, I don't see anything in udf_dirent_s that should dictate it be
private.


> this is in the udf_dirent_t structure, but is hidden from programmers.
>
> I care about this as I am trying to write a barebones dvd decrypter that
> works on images files
>
> i.e. I have some DVDs in bad shape, so using 1) lsdvd to authenticate the
> disk, 2) ddrescue to recover a complete image, but it still has CSS
> embedded, so then need to remove the CSS, but I have to basically check if I
> need to rekey on each VOB file and need to know the start of it to rekey on
> the right block.  libcdio's udf support should provide it to me, but as it's
> hidden, it doesn't.
>
> any thoughts on providing an interface to this data?
>
> thanks
>
>