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

API Set Dump should obey custom config #10

Closed
captainGeech42 opened this issue Aug 19, 2019 · 3 comments · Fixed by #11
Closed

API Set Dump should obey custom config #10

captainGeech42 opened this issue Aug 19, 2019 · 3 comments · Fixed by #11

Comments

@captainGeech42
Copy link

I wanted to test binee and make sure it got the DLLs correctly, but I used a custom config ("win10_64" instead of 32). Unfortunately, it was hardcoded to use the default "win10_32" config. The code for this is here. I'm happy to put together a PR for this flag to obey a custom config that gets passed in with -c, but I'm curious if this is worthwhile or relevant. Thoughts?

Output:

root@04f06cefb9a9:~/go/src/binee# ./binee -A -c config/my_config.yaml
2019/08/19 20:34:21 file 'apisetschema.dll' not found
root@04f06cefb9a9:~/go/src/binee# cat config/my_config.yaml 
root: "os/win10_64/"
root@04f06cefb9a9:~/go/src/binee# ls os/win10_64/windows/system32/
advapi32.dll  apisetschema.dll	crypt32.dll  kernel32.dll  mswsock.dll	ntdll.dll  secur32.dll	shell32.dll  shlwapi.dll  user32.dll  ws2_32.dll
@jholowczak
Copy link
Collaborator

Good timing on this issue, I'm currently working on fixing that hard-coded path as we speak. This same issue is the cause of other issues relating to custom configs. PR coming shortly.

@jholowczak
Copy link
Collaborator

Also a small note, we don't have full support for 64 bit yet so I imagine you will run into issues getting some files to run.

@captainGeech42
Copy link
Author

Yeah I discovered the 64bit issue pretty quickly afterwards trying to get those libraries to work, so I switched to a set of 32bit DLLs. Is there a timeline for full 64bit support?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants