libyal / libvhdi Goto Github PK

Thank you for the fantastic VHD library.

I have been experimenting with the new VHDX support. However, I found that libvhdi_file_read_buffer_at_offset() will sometimes return unexpected data. This data appears to be the original file header and is repeated at intervals throughout data.

I have uploaded an a small example VHDX file. This contains a minimal NTFS file system and is available here:

https://drive.google.com/file/d/1ARTrgObHAlfEtWIDC7yguuRpKRQMRTNV

When I open this file usingLibvhdi, I found that the signature "vhdxfile" is present at the following offsets: 0x2000000, 0x4000000, 0x6000000, 0x8000000 etc. This data is not present when the file is mounted using the built-in Windows VHDX feature.

How do we mount multiple VHDX differencing file in a single mount point ?
file1.vhdx , file2.avhdx, file3.avhdx

I am getting this error with UBUNTU 64-bit -- 3.13.0-49-lowlatency. Libtool is:
libtool (GNU libtool) 2.4.2

 configure.ac:22: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
  If this token and others are legitimate, please use m4_pattern_allow.
  See the Autoconf documentation.

configure.ac:31: error: possibly undefined macro: AC_PROG_LIBTOOL

autoreconf: /usr/bin/autoconf failed with exit status: 1

See subject and a similar issue here: libyal/libewf#117

Environment: macOS 10.14
Details:

$ ./vhditools/vhdimount ~/VirtualBox\ VMs/test/test.vhd a
vhdimount 20190105

volicon: missing 'iconpath' option
Unable to create fuse handle.

where is ./configure

Hi!

Can you add a .gitmodules support for this dependencies?

***** automake *****
***** PWD: /var/tmp/portage/dev-libs/libvhdi-20181227_alpha/work/libvhdi-20181227_alpha
***** automake --add-missing --copy --foreign --force-missing

configure.ac:35: warning: The 'AM_PROG_MKDIR_P' macro is deprecated, and its use is discouraged.
configure.ac:35: You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro instead,
configure.ac:35: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your Makefile.am files.
configure.ac:22: installing './compile'
configure.ac:11: installing './missing'
Makefile.am: installing './INSTALL'
configure.ac:189: error: required file 'libcerror/Makefile.in' not found
configure.ac:190: error: required file 'libcthreads/Makefile.in' not found
configure.ac:191: error: required file 'libcdata/Makefile.in' not found
configure.ac:192: error: required file 'libclocale/Makefile.in' not found
configure.ac:193: error: required file 'libcnotify/Makefile.in' not found
configure.ac:194: error: required file 'libcsplit/Makefile.in' not found
configure.ac:195: error: required file 'libuna/Makefile.in' not found
configure.ac:196: error: required file 'libcfile/Makefile.in' not found
configure.ac:197: error: required file 'libcpath/Makefile.in' not found
configure.ac:198: error: required file 'libbfio/Makefile.in' not found
configure.ac:199: error: required file 'libfcache/Makefile.in' not found
configure.ac:200: error: required file 'libfdata/Makefile.in' not found
configure.ac:201: error: required file 'libfguid/Makefile.in' not found
Makefile.am:3: error: required directory ./libcerror does not exist
Makefile.am:3: error: required directory ./libcthreads does not exist
Makefile.am:3: error: required directory ./libcdata does not exist
Makefile.am:3: error: required directory ./libclocale does not exist
Makefile.am:3: error: required directory ./libcnotify does not exist
Makefile.am:3: error: required directory ./libcsplit does not exist
Makefile.am:3: error: required directory ./libuna does not exist
Makefile.am:3: error: required directory ./libcfile does not exist
Makefile.am:3: error: required directory ./libcpath does not exist
Makefile.am:3: error: required directory ./libbfio does not exist
Makefile.am:3: error: required directory ./libfcache does not exist
Makefile.am:3: error: required directory ./libfdata does not exist
Makefile.am:3: error: required directory ./libfguid does not exist
libvhdi/Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'

it might be worth mentioning that the

field:
Disk sizeContains the size of the disk in bytes

is stored in big endian format. I would have expected it to be little endian given ms file formats.

The current implementation does not appear to provide a method to determine the sector size.

This could be called libvhdi_handle_get_bytes_per_sector()

For context: libyal/libvmdk#16

Hi Joachim Metz,

I've been preparing to package the new release of libvhdi for Debian,
I found a small obstacle ahead, there was a change in ABI, some interfaces were added and others were removed, as we can see in:
https://salsa.debian.org/fvcr/libvhdi/-/commit/31c90371c7d0d97b8f89e88824bcd73e0543d45e
I believe that the removal of some interfaces should cause a bump of SONAME.

What do you think about bumping SONAME to reflect the backwards compatibility breakage in the new releases?
As other software that depends on the removed interfaces/functions will have to be checked and rebuilt against it.

Regards,
Francisco.

Looking at the man page for libvhdi I only see read operations.
Is it possible to create and write to vhd disks with this library?

See https://brew.sh and https://docs.brew.sh/Formula-Cookbook

VHDX appears to be positioned as version 2 of the VHD format, though it is significantly different.

Consider adding VHDX support to libvhdi

• Create test files https://github.com/dfirlabs/vhdx-specimens
• Add VHDX format documentation
• Update source
• Test

Seeing that VHDX support is getting closer to completion #13 per #11 consider adding API function to return bytes per sector (logical sector size)

I am trying to build libvhdi from source. But the build is failing due to some cppflags missing in libcerror. This happens only after libyal/libcerror@2066b60 commit in libcerror.

.

Can you take a look into this issue?. or am I doing something wrong?

My commands to build from source:

./synclibs.sh
./autogen.sh
./configure
make