[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <eb9b69c4198c8381be6aa75816aaad4f@smtp.hushmail.com>
Date: Fri, 03 Oct 2014 23:59:23 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: John the Ripper v1.8.0.2-bleeding-jumbo-2014-09-28
for windows is available on the custom-builds wiki page
OK, that's not too bad. But unfortunately bleeding was less stable than
usual during the last days. That commit has the following "severe"
issues that I know of as of this writing:
- The new mask mode had a scaling issue and several edge-case bugs that
are fixed now. It's definitely usable for the casual user anyway.
- Resuming with an implicit internal encoding will fail. This only
happens if you uncommented Unicode/codepage stuff in john.conf. It is a
recoverable problem but very irritating.
If you have "warm caches" for re-building a version with latest commit
as of now, it would not hurt. But it's not that important if you ask me
- and who knows, we may always find the "worst bug ever" tomorrow
("tomorrow" being a constant) ;-)
magnum
On 2014-10-03 23:05, Robert Harris wrote:
> Magnum,
>
> I went to https://github.com/magnumripper/JohnTheRipper. Then I downloaded the zip file. Do it have the commit hash?
>
> I see in the comments of the actual zip file that is says: 57c2c
>
> -----Original Message-----
> From: magnum [mailto:john.magnum@...hmail.com]
> Sent: Friday, October 03, 2014 6:45 AM
> To: john-users@...ts.openwall.com
> Subject: Re: [john-users] John the Ripper v1.8.0.2-bleeding-jumbo-2014-09-28 for windows is available on the custom-builds wiki page
>
> On 2014-10-03 02:15, Robert Harris wrote:
>> Magnum,
>>
>> Where exactly can I find the commit hash in the github.com/magnumripper/JohnTheRipper file I downloaded?
>>
>> I'll reply with that info.
>
> That depends on how exactly you downloaded it. If you used https://github.com/magnumripper/JohnTheRipper/tarball/bleeding-jumbo to download a tarball, the abbreviated commit hash is the last 7 characters of the resulting filename. As of this writing, the name ends up as "magnumripper-JohnTheRipper-1.8.0-6154-ga886990.tar.gz" and the commit hash is thus a886990.
>
> https://github.com/magnumripper/JohnTheRipper/commits/bleeding-jumbo
> lists the same commit hash in the right column.
>
> magnum
>
>
> ---
> This email is free from viruses and malware because avast! Antivirus protection is active.
> http://www.avast.com
>
>
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
