The symbolic link issue mentioned below in Cygwin is still broken, if you
configure with:
"--enable-ln-s ", which Use ln -s vs symlink.c wrappers (Cygwin only)
So, I tested my configure without this, and all executables are working now.
I'm almost done with my testing and I'm about the release a new version for
Windows x64 on the custom build site.
-Robert B. Harris from VA
-----Original Message-----
From: ***@netscape.net [mailto:***@netscape.net]
Sent: Friday, August 25, 2017 11:24 PM
To: john-***@lists.openwall.com
Subject: RE: [john-users] Custom Windows build 1.8.0.9 - What happened to
zip2john?
So seeing how this problem was just discovered, I'd like to hear that
someone has either worked on the code to fix it, or they believe it is no
longer a problem with the code.
Then I'll compile a new bleeding for Windows, test this to confirm or deny
the problem's current status. Once the new version is confirmed fixed, I'll
put on the custom build site.
--Robert B. Harris
-----Original Message-----
From: Glen B [mailto:***@msn.com]
Sent: Thursday, August 24, 2017 10:22 PM
To: john-***@lists.openwall.com
Subject: Re: [john-users] Custom Windows build 1.8.0.9 - What happened to
zip2john?
Hey Robert,
I can confirm what you've found, the earlier build did have the proper
executables. I hope I can test a build from you soon if you won't mind!
Glen
Post by r***@netscape.netHey, I'm Robert and the one who contributes almost all of the builds
on the custom build site.
I think there was something definitely wrong with the bleeding version
in March 2017, and possibly now, when building with cygwin.
See below for more details.
I tested all of the symbolic link files in the Windows build from
March 2017 that I did and I can confirm there seems to be a problem with
them.
Post by r***@netscape.netbase64conv
gpg2john
hccap2john
keepass2john
putty2john
racf2john
rar2john
unafs
undrop
unique
unshadow
I then checked the previous version I made
"John-the-Ripper-v1.8.0-jumbo-1-Win-64".
In this version there are no files that are symbolic links. These all
run fine.
base64conv.exe
calc_stat.exe
cprepair.exe
dmg2john.exe
genmkvpwd.exe
gpg2john.exe
hccap2john.exe
john.exe
keepass2john.exe
keychain2john.exe
keyring2john.exe
keystore2john.exe
kwallet2john.exe
luks2john.exe
mkvcalcproba.exe
pfx2john.exe
putty2john.exe
pwsafe2john.exe
racf2john.exe
rar2john.exe
raw2dyna.exe
ssh2john.exe
tgtsnarf.exe
truecrypt_volume2john.exe
uaf2john.exe
unafs.exe
undrop.exe
unique.exe
unshadow.exe
wpapcap2john.exe
zip2john.exe
-- Robert B. Harris from VA
-----Original Message-----
Sent: Friday, August 18, 2017 3:55 PM
Subject: Re: [john-users] Custom Windows build 1.8.0.9 - What happened
to zip2john?
Post by Glen BI really liked the earlier versions of JtR that were self-contained and
didn't require downloading anything else to be honest.
This build wasn't meant to require anything extra either. According
to what you said, it's just a bug.
Post by Glen BIf this is just a symlink though, what is it symlink-ing to? The john
binary? If so, couldn't I just run john directly?
Yes. You could run "john" directly if you copy or rename it so that
it'd be called "zip2john".
Alexander
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus