ghidra
ghidra copied to clipboard
It is not possible to directly select the type of filesystem when opening it.
(This sort of crosses the line between bug and feature, though)
Describe the bug Filesystem providers whose factories do not implement GFileSystemProbeBytesOnly or GFileSystemProbeByteProvider are not considered when opening a filesystem via 'File > Open File System...'.
To Reproduce Steps to reproduce the behavior:
- Create an empty filesystem whose factory implements neither GFileSystemProbeBytesOnly nor GFileSystemProbeByteProvider and make it available to Ghidra.
- Open a filesystem via 'File > Open File System...'
- An error message says no filesystem provider for the file is available.
Expected behavior If the probing providers give up, there should be a way to pick a fallback filesystem.
Environment (please complete the following information):
- OS: macOS
- Java Version: 11.0.15
- Ghidra Version: 10.2-DEV at ca60845ee1551f33d8e02b03503d67a1742d9251
- Ghidra Origin: locally built.
Additional context In cases where a custom filesystem with no particular header or other identifying characteristics to write a probe for, there is no chance for the filesystem to be traversed even if a filesystem provider is available.
I've written a proto-PR to work around that issue - which I'm having now: https://github.com/agatti/ghidra/commit/7bf3a0e244eb6236a250fd29be42ed4f3a2c353f. I'm willing to clean it up and submit it as a full-fledged PR if it's OK with you folks, but maybe you may have other ideas...
seems reasonable, and the PR looks ok. I'll comment in the branch about a few things and we'll go from there.
I currently hit this for virtually all binaries and for the mean time you can archive your binary into a tarball, open it in Ghidra, and then import the binary file from with the tarball as a workaround.
hello everyone. i have the same problem. when i try to import a binary into ghidra, it say me ' no filesytem provide for this file'. i don't know how to solve it. please someone to help me