Opened 13 months ago
Last modified 13 months ago
#68482 assigned defect
hashcat @6.2.5_0: does not create profile dir, '.local/share/hashcat/... No such file or directory'
Reported by: | JDLH (Jim DeLaHunt) | Owned by: | gaming-hacker (G Alexander) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | Cc: | ||
Port: | hashcat |
Description
Hashcat appears to use a session directory, ~/.local/share/hashcat/
, to store information on particular sessions when it runs. It issues an error message when the directory is not available. It appears not to create the directory. MacPorts appears not to create this directory either.
To reproduce:
- Make sure there is no session directory:
% rmdir ~/.local/share/hashcat/
- Install hashcat:
% sudo port install hashcat
- Run hashcat, asking for its built-in documentation:
% hashcat --help
Observed behaviour:
% hashcat --help | pbcopy /Users/myuser/.local/share/hashcat/sessions/usage.pid: No such file or directory /Users/myuser/.local/share/hashcat: No such file or directory % ls -ld ~/.local ~/.local/share ~/.local/share/hashcat ls: /Users/myuser/.local/share/hashcat: No such file or directory drwx------ 3 myuser staff 96 6 May 2022 /Users/myuser/.local drwx------ 7 myuser staff 224 17 Sep 01:31 /Users/myuser/.local/share
Expected behaviour: hashcat runs without an error message.
Discussion: I am not sure if hashcat creates its session directory itself when run on Windows or Linux. I do not see information about manually creating a profile directory in the Hashcat project's installation FAQ. Nor do I see information about hashcat creating the directory itself.
A successful workaround for me was to create the directory myself: % mkdir -p "~/.local/share/hashcat/"
. Having done that, the error messages no longer appeared, and I had the expected behaviour.
MacPorts ports won't create anything in your home directory. If you expect hashcat to do so, file a bug report / enhancement request with its developer.