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

.dmg builds and releases are actually Mach-O executables #26

Closed
kernel-sanders opened this issue Sep 26, 2018 · 2 comments
Closed

.dmg builds and releases are actually Mach-O executables #26

kernel-sanders opened this issue Sep 26, 2018 · 2 comments

Comments

@kernel-sanders
Copy link

Just a note to let you know that the "dmg" releases and builds from source for Darwin are actually Mach-O executables. Unless this was purposeful obfuscation for some reason, in which case... carry on.

$ file /.../merlinAgent-Darwin-x64-v0.6.0/merlinAgent-Darwin-x64.dmg
/.../merlinAgent-Darwin-x64-v0.6.0/merlinAgent-Darwin-x64.dmg: Mach-O 64-bit executable x86_64
@Ne0nd0g
Copy link
Owner

Ne0nd0g commented Sep 26, 2018

Thanks for the heads @kernel-sanders , it wasn't an attempt for purposeful obfuscation. My goal was to have a file extension on it so that I could easily sort it among other binary files. I'm not super familiar with MacOS and found that with a dmg extension I could meet my goal and the file would execute fine on the CLI. Is there a better extension I should use? Maybe just .bundle?

@kernel-sanders
Copy link
Author

I would suggest .bin or .macho just to prevent people (like me) from trying to extract the disk image and failing.

@Ne0nd0g Ne0nd0g closed this as completed in c06f699 Jan 1, 2019
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

No branches or pull requests

2 participants