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

hashcat.c: change osx to OSX use shared_dir #409

Merged
merged 1 commit into from
Jul 4, 2016
Merged

hashcat.c: change osx to OSX use shared_dir #409

merged 1 commit into from
Jul 4, 2016

Conversation

jdek
Copy link
Contributor

@jdek jdek commented Jul 1, 2016

This fixes #408.

Note: I originally created the issue because I thought I didn't have enough time to look into a fix, but turns out I needed a fix enough to make time.

@jsteube
Copy link
Member

jsteube commented Jul 4, 2016

Two things to mention here:

  • I never expected this install system to be run on OSX. There could be problems
  • The macro APPLE is kind of official? Reason is we're currently using DARWIN on the most spots. What the correct/better form?

@jsteube jsteube merged commit 362cb05 into hashcat:master Jul 4, 2016
@magnumripper
Copy link
Contributor

magnumripper commented Jul 4, 2016

On my machine (latest OSX) both the native and Homebrew's gcc define __APPLE__ by default, but not __DARWIN__

$ gcc -dM -E -x c /dev/null | egrep "(APPLE|DARWIN)"
#define __APPLE_CC__ 1
#define __APPLE__ 1
$ /usr/bin/gcc -dM -E -x c /dev/null | egrep "(APPLE|DARWIN)"
#define __APPLE_CC__ 6000
#define __APPLE__ 1

@jsteube
Copy link
Member

jsteube commented Jul 4, 2016

Excellent. I think we should switch to that. /cc @unix-ninja

@unix-ninja
Copy link
Contributor

Sure. If we wanted to remove the custom declaration then I am fine with using APPLE

@unix-ninja
Copy link
Contributor

That was supposed to be

__APPLE__

jsteube added a commit that referenced this pull request Jul 8, 2016
@XeniaGabriela
Copy link

XeniaGabriela commented Aug 11, 2016

Dear hashcat team,

I just downloaded the latest version and installed it in an Ubuntu 14.04 virtual machine on Windows7 by

  1. unzipping it to ~/.hashcat with p7zip
  2. copying hashcat64.bin to /usr/bin/
  3. making a symblic link hashcat to hashcat64.bin

'hashcat --help' works fine ...
But I am getting the ERROR '/usr/bin/hashcat.hctune: No such file or directory' when I run the program.

Did I do something wrong with the installation?

Regards,

Xenia

@jdek jdek deleted the patch-2 branch August 11, 2016 17:25
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 this pull request may close these issues.

hashcat looking in binary folder for resources
5 participants