[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <002501d324ca$be729390$3b57bab0$@netscape.net>
Date: Sun, 3 Sep 2017 11:38:51 -0400
From: <rs904c@...scape.net>
To: <john-users@...ts.openwall.com>
Subject: RE: John the Ripper v1.8.0.9-jumbo-1-bleeding (Bleeding version on 2017-09-01), compiled for windows, on the custom-builds site
I'm not really sure how to do that. Can you point me to some directions on that?
-----Original Message-----
From: Frank Dittrich [mailto:frank.dittrich@...lbox.org]
Sent: Sunday, September 03, 2017 11:29 AM
To: john-users@...ts.openwall.com
Subject: Re: [john-users] John the Ripper v1.8.0.9-jumbo-1-bleeding (Bleeding version on 2017-09-01), compiled for windows, on the custom-builds site
Hi Robrt,
Am 03.09.2017 um 17:17 schrieb rs904c@...scape.net:
> Version: 1.8.0.9-jumbo-1-bleeding
Could you clone the git repository, and build from within your local repository?
Then, the version string would show something like
Version: 1.8.0.6-jumbo-1-3229-g9bb5e94
This means, the binary was built using git commit 9bb5e94, which is 3229 commits after release 1.8.0.6-jumbo-1.
The actual commit id would be really useful in case of bug reports.
BTW:
The "Version: 1.8.0.9-jumbo-1-bleeding" version string when built outside a git repository is somewhat misleading.
It looks "newer" than the "1.8.0.6-jumbo-1-3229-g9bb5e94", but it isn't.
Instead, this version string has been unchanged since 2016-07-08.
So, we never know if a user is running a more or less current binary or a binary which is more than one year old.
Regards
Frank
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
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.
