Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to glob E01 on Windows share? #146

Open
ghost opened this issue Feb 2, 2021 · 5 comments
Open

Unable to glob E01 on Windows share? #146

ghost opened this issue Feb 2, 2021 · 5 comments

Comments

@ghost
Copy link

ghost commented Feb 2, 2021

Attempts to open an E01 file fail when the target is on a network share. I think the problem may be in libewf_glob()

@joachimmetz joachimmetz self-assigned this Feb 2, 2021
@joachimmetz
Copy link
Member

@devmd5 can you provide more detail, otherwise I cannot help you

  • what is the error you are getting? or not working?
  • what version of libewf are you using? in what context?
  • how was libewf buillt?
  • what type of share are you talking about? CIFS? other?

@joachimmetz joachimmetz added the pending input reporter Issue is pending input from the reporter label Feb 2, 2021
@joachimmetz joachimmetz changed the title Open fails when target is on a network shared (Win32) Unable to open E01 from Windows share? Feb 2, 2021
@joachimmetz joachimmetz changed the title Unable to open E01 from Windows share? Unable to glob E01 on Windows share? Feb 2, 2021
@ghost
Copy link
Author

ghost commented Feb 2, 2021

The images are located on a Windows 10 share (SMB2 I think). When opened locally, the images open file.

e.g. \myhost\share\name.e01

However, when opened via the share path, the call to libewf_glob_wide() returns 1 indicating success but number of files is reported as 0. It looks like libewf_glob_wide() fails blows when the path has a \ prefix.

This error is in libewf-experimental-20201230. The library was built as a DLL following the standard instructions and otherwise seems to work ok.

@joachimmetz
Copy link
Member

joachimmetz commented Feb 2, 2021

can you provide an example of the path you are using there are multiple ways to define an UNC share path on Windows

@ghost
Copy link
Author

ghost commented Feb 2, 2021

\\servername\share\TestImage.e01
\\192.168.20.2\share\TestImage.e01

@joachimmetz
Copy link
Member

I would need to take a closer look. The glob just tries to iterate which segment files exists specific for the format. Maybe the exist checks fails for some reason.

@joachimmetz joachimmetz added needs a closer look and removed pending input reporter Issue is pending input from the reporter labels Feb 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant