Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1b9e1de2d019f48c73c4808a92584b22@smtp.hushmail.com>
Date: Wed, 11 Sep 2013 11:23:00 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: JTR Bleeding Edge cannot compile in cygwin 32bit with krb5-18_fmt.c error

On 11 sep 2013, at 09:58, Alex <experi3nc3@...il.com> wrote:
> I've just downloaded the  latest git copy to Desktop and tried compiling it 
> with Win7 cygwin but this error came up:
> 
> krb5-18_fmt.c: In function ‘crypt_all’:
> krb5-18_fmt.c:217:21: error: ‘krb5_keyblock’ has no member named ‘length’
> krb5-18_fmt.c:218:30: error: ‘krb5_keyblock’ has no member named ‘contents’
> krb5-18_fmt.c:219:9: error: ‘krb5_keyblock’ has no member named ‘contents’
> krb5-18_fmt.c:220:9: error: ‘krb5_keyblock’ has no member named ‘contents’
> krb5-18_fmt.c:221:9: error: ‘krb5_keyblock’ has no member named ‘contents’
> Makefile:2243: recipe for target `krb5-18_fmt.o' failed
> make[1]: *** [krb5-18_fmt.o] Error 1
> make[1]: Leaving directory 
> `/cygdrive/c/Users/Administrator/Desktop/JohnTheRipper-unstable-jumbo/src'
> Makefile:1690: recipe for target `win32-cygwin-x86-sse2' failed
> make: *** [win32-cygwin-x86-sse2] Error 2
> 
> All I did was to change CHARSET_LENGTH in params.h

If you are indeed using bleeding-jumbo, then why change CHARSET_LENGTH? Is 24 not enough? Or did you check out the unstable-jumbo branch?

Anyway I'm not sure how to get krb5-18 working for you but in case you don't need it you can try disabling it. Comment out the two following lines in Makefile:

HAVE_KRB5 = `find 2>&1 /usr/include/ /usr/local/include/ -name "krb5.h" | grep -q "krb5.h" && echo -DHAVE_KRB5`
KRB5_LDFLAGS = `find 2>&1 /usr/include/ /usr/local/include/ -name "krb5.h" | grep -q "krb5.h" && echo -lk5crypto -lkrb5`

magnum

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.