Yeah, the problem here is different.
The dependencies are just incorrect (neither Mesa, nor Pocl are officially
recommended by hashcat and there is no such dependency for the hashcat
project) and the user needs to understand what s/he needs to do to get
hashcat working (a guide like the one I post
Hi,
>Well, as said, the only correct way would be that the "hashcat" package
>directly depends on NVidia drivers, AMD drivers or Intel drivers.
>
>But as far as I understood this can't be enforced because otherwise the
>hashcat package can't be installed by default (and debian has the policy
-- Forwarded message --
From: Phil
Date: Tue, Mar 7, 2017 at 2:33 PM
Subject: Re: Bug#856932: hashcat dependency problem
To: Raphael Hertzog
Hello Raphael,
Thank you for your answer and the explanations.
Well, as said, the only correct way would be that the "hashcat&quo
[ ccing Petter for his input on isenkram at the end ]
Hello,
On Mon, 06 Mar 2017, Philipp wrote:
> Firstly, I just want to let you know that I already tried to contact some
> Kali/Debian developers privately (via mail, for instance the dev rhertzog
> which seems to be active and somehow related t
Package: hashcat
Version: 3.30-1
Severity: normal
Dear Maintainer,
Firstly, I just want to let you know that I already tried to contact some
Kali/Debian developers privately (via mail, for instance the dev rhertzog
which seems to be active and somehow related to this package) about this
"problem"
5 matches
Mail list logo