john: Does not build in Sparc
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
john (Debian) |
Fix Released
|
Unknown
|
|||
john (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Automatically imported from Debian bug report #220928
http://
In Debian Bug tracker #220928, Christian Kurz (shorty) wrote : Re: Bug#220928: john: Does not build in Sparc | #1 |
In Debian Bug tracker #220928, Paul Slootman (paul-debian) wrote : | #2 |
On Sun 16 Nov 2003, Christian Kurz wrote:
> [...]
> > Benchmarking: Standard DES [24/32 128K]... make[3]: *** [sparc.h] Error 1
>
> > So it seems to break in the 'bench' program (in some of the '||exit 1')
> > statements there. There might be two ways to fix this:
It segfaults when setting the SIGALRM signal handler at line 100 of
bench.c. This indicates to me that some sort of memory corruption has
gone on before that.
> investigate the build who has some knowledge about sparc. Since the
> build logs show that 1.6.17 and earlier versions did build fine on
> sparc. So I suppose it's some change in the build daemon or on sparc
> that is responsible for this break.
With memory corruption, it could be all sorts of things that trigger it.
Assumedly the overwriting of some buffer happens all the time, but only
now does it touch an area that's critical. This could be due to other
libc, other compiler, other kernel...
I'd recommend running on some sort of malloc debugger such as electric
fence or so. Doing this on i386 should also be effective.
Paul Slootman
In Debian Bug tracker #220928, Christian Kurz (shorty) wrote : | #3 |
[Cc'ing Javier, the co-maintainer.]
On [18/12/03 17:35], Paul Slootman wrote:
> On Sun 16 Nov 2003, Christian Kurz wrote:
> > [...]
> > > Benchmarking: Standard DES [24/32 128K]... make[3]: *** [sparc.h] Error 1
> > > So it seems to break in the 'bench' program (in some of the '||exit 1')
> > > statements there. There might be two ways to fix this:
> It segfaults when setting the SIGALRM signal handler at line 100 of
> bench.c. This indicates to me that some sort of memory corruption has
> gone on before that.
Oh, that's not nice for me to read, considering the important task that
john does.
> > investigate the build who has some knowledge about sparc. Since the
> > build logs show that 1.6.17 and earlier versions did build fine on
> > sparc. So I suppose it's some change in the build daemon or on sparc
> > that is responsible for this break.
> With memory corruption, it could be all sorts of things that trigger it.
> Assumedly the overwriting of some buffer happens all the time, but only
> now does it touch an area that's critical. This could be due to other
> libc, other compiler, other kernel...
> I'd recommend running on some sort of malloc debugger such as electric
> fence or so. Doing this on i386 should also be effective.
Okay, we'll try it and see if that helps. I'll maybe try valgrind later.
Christian
--
Debian Developer (http://
1024D/B7CEC7E8 44BD 1F9E A997 3BE2 A44F 96A4 1C98 EEF3 B7CE C7E8
In Debian Bug tracker #220928, Javier Fernández-Sanguino (jfs) wrote : Any success testing malloc errors? | #4 |
Hi there,
Any success running john with valgrind/eeyes in order to find out where the
sparc issue might reside? I would hate to drop sparc from the supported
archs, but if we don't do it in the next upload probably the latest
revision (which includes quite a number of bug fixes) will not make it into
sarge in time for release...
Regards
Javier
In Debian Bug tracker #220928, Justin Pryzby (justinpryzby-users) wrote : MALLOC_CHECK_ | #5 |
malloc(3) also recommends `export MALLOC_CHECK_=1`, which is very simple
and easy.
Justin
In Debian Bug tracker #220928, Javier Fernández-Sanguino (jfs) wrote : Further information related to testing (in sparc) | #6 |
I have been testing this issue further in a unstable chroot (at vore). This
bug reproduces in gcc-2.95, gcc-3.2 and gcc-3.3 in unstable. Running it
through a debugger:
-------
GNU gdb 6.1-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
(...)
This GDB was configured as "sparc-
(gdb) run 1
Starting program: /home/jfs/
Benchmarking: Standard DES [24/32 128K]...
Program received signal SIGSEGV, Segmentation fault.
0x7005cf98 in __errno_location () from /lib/libc.so.6
(gdb) bt
#0 0x7005cf98 in __errno_location () from /lib/libc.so.6
#1 0x70072dc0 in __libc_sigaction () from /lib/libc.so.6
#2 0x70072ff4 in sigaction () from /lib/libc.so.6
#3 0x70072ce0 in ssignal () from /lib/libc.so.6
#4 0x0001aba0 in benchmark_format (format=0x2e040, salts=256,
results=
#5 0x0001af9c in main (argc=1, argv=0x32400) at best.c:53
-------
Bench.c (line 100) just does
If the signal call is removed it will not segfault (but will not run
properly either):
Benchmarking: Standard DES [24/32 128K]... Alarm clock
Christian hast said (in IRC) that it seems that the devel branch will not
compile properly on Sparc. I have succesfully tested a built on Solaris
over Sparc, so there seems to be an issue with the linux-specific code. I'm
not sure where the default resides (maybe libc6?). I would suggest that
this bug was reassigned to libc6 and that sparc support for john was
dropped (but this bug left open) until the issue is fixed.
Regards
Javier
In Debian Bug tracker #220928, Guilherme de S. Pastore (fatalerror) wrote : Damn, forgot it | #7 |
package john
tag 220928 pending
thanks
Upstream provided a patch. Our problems with Sparc should now be over. It will
be incorporated to the CVS@Alioth tonight (as soon as I get home).
--
Guilherme de S. Pastore
<email address hidden>
In Debian Bug tracker #220928, Guilherme de S. Pastore (fatalerror) wrote : Ugh... | #8 |
package john
tag 220928 -pending
tag 252506 pending
thanks
--
Guilherme de S. Pastore (fatalerror)
<email address hidden>
In Debian Bug tracker #220928, Javier Fernández-Sanguino (jfs) wrote : Tagging | #9 |
tags 252206 pending
tags 252506 pending
tags 251227 pending
tags 253194 pending
tags 220928 pending
thanks
All these bugs are pending an upload since the code fixing them has already
been commited to CVS...
Javier
In Debian Bug tracker #220928, Javier Fernández-Sanguino (jfs) wrote : Fixed in upload of john 1.6.36-2 to experimental | #10 |
tag 117213 + fixed-in-
tag 213164 + fixed-in-
tag 220928 + fixed-in-
tag 251095 + fixed-in-
tag 251172 + fixed-in-
tag 79831 + fixed-in-
quit
This message was generated automatically in response to an
upload to the experimental distribution. The .changes file follows.
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.7
Date: Tue, 8 Jun 2004 19:30:18 +0200
Source: john
Binary: john
Architecture: source i386
Version: 1.6.36-2
Distribution: experimental
Urgency: low
Maintainer: Guilherme de S. Pastore <email address hidden>
Changed-By: Javier Fernandez-Sanguino Pen~a <email address hidden>
Description:
john - An active password cracking tool
Closes: 79831 79831 117213 213164 220928 251095 251172
Changes:
john (1.6.36-2) experimental; urgency=low
.
* Moved -DJOHN_SYSTEM_WIDE from CPPFLAGS to CFLAGS were it should have
been in the first place. This makes john usable for both system-wide
use and per-user use. User files are located in ~/.john
even though users will need to copy the john.conf provided
file to that directory (Closes: #79831, #117213, #79831)
* Introduced --config and --private options in John's code to be able
to define specific configuration files and location of John's record
and log files per run, this fixes some of the requests filed in #110139.
It is currently a hack, however.
* Introduced a testbuild system (based on ifupdown's) which enables
the build system to test wether the compiled 'john-any' binary
can properly crack some simple passwords. This might be useful to
detect errors in autobuilders.
* Sparc support is done throught the 'generic' target since Solar
Designer says its the way to go and, in any case, the assembly code
which makes the binary not work might be removed in the future. This
should make the build work on Sparc again. Note that, for the moment
support for other architectures will be provided only in the
'experimental' package (Closes: #220928)
* Added a mechanism to detect if the passwords files have changed
(a new user has been added, a password has been modified, etc...) when
restoring the cron job so that John will use the latest password files.
The current implementation is rather "fine-grained" so it will start
again even if a user's name, uid, or gid is changed. Further
reimplemen
username or password has been modified.
(Closes: #251172)
* Major rewrite of the cronjob which will now work as follows:
* 'start' will run john in background instead of waiting for it to finish
* 'stop' will stop john and will call mailer if needed
Other changes include:
-Stale files are now removed under some circunstances (so /var/run/john
does not fill up with cronpasswd files)
- John is started/stopped using start-stop-daemon which makes it
write the pid file properly (unlike previously). Also,
the start-stop-daemon usage makes it possible to run john as a
non-root user (if everything i...
In Debian Bug tracker #220928, Guilherme de S. Pastore (fatalerror) wrote : Bug fixed, no need for help | #11 |
package john
tag 220928 -help
severity 220928 serious
quit
Debian Bug Importer (debzilla) wrote : | #12 |
Automatically imported from Debian bug report #220928
http://
Debian Bug Importer (debzilla) wrote : | #13 |
Message-ID: <email address hidden>
Date: Sat, 15 Nov 2003 19:18:38 +0100
From: Javier =?iso-8859-
To: <email address hidden>
Subject: john: Does not build in Sparc
Package: john
Version: 1.6-19
Tags: help confirmed
John does not build in the buildd environments for Sparc since release
1.6-19. It seems this is a problem in the build, and not in the package,
since the bugs which prevented it from building [1] have been fixed in
1.6-22 and it still will not build [2].
The build ends with:
gcc -c -Wall -O2 -fomit-
gcc -c -Wall -O2 -fomit-
path.c: In function `path_done':
path.c:49: warning: dereferencing type-punned pointer will break
strict-aliasing rules
gcc -c -Wall -O2 -fomit-
gcc -c -Wall -O2 -fomit-
gcc -s DES_bs.o DES_bs_b.o DES_fmt.o DES_std.o sparc.o MD5_fmt.o MD5_std.o
BF_fmt.o BF_std.o bench.o best.o common.o config.o formats.o memory.o
misc.o params.o path.o signals.o tty.o -o bench
make[5]: Leaving directory `/build/
make[4]: Leaving directory `/build/
Benchmarking: Standard DES [24/32 128K]... make[3]: *** [sparc.h] Error 1
So it seems to break in the 'bench' program (in some of the '||exit 1')
statements there. There might be two ways to fix this:
- try to upgrade the SPARC part to the -devel branch and see if that fixes
it
- drop sparc from the supported architectures (a drastic move).
Regards
Javi
[1] (missing sparc.h)
http://
[2]
http://
Debian Bug Importer (debzilla) wrote : | #14 |
Message-ID: <email address hidden>
Date: Sun, 16 Nov 2003 21:54:26 +0100
From: Christian Kurz <email address hidden>
To: Javier =?iso-8859-
<email address hidden>
Subject: Re: Bug#220928: john: Does not build in Sparc
--xXmbgvnjoT4axfJE
Content-Type: text/plain; charset=iso-8859-1
Content-
Content-
On [15/11/03 19:18], Javier Fern=E1ndez-
> Package: john
> Version: 1.6-19
> Tags: help confirmed
> John does not build in the buildd environments for Sparc since release=20
> 1.6-19. It seems this is a problem in the build, and not in the package,=
=20
> since the bugs which prevented it from building [1] have been fixed in=20
> 1.6-22 and it still will not build [2].
> The build ends with:
[...]
> Benchmarking: Standard DES [24/32 128K]... make[3]: *** [sparc.h] Error 1
> So it seems to break in the 'bench' program (in some of the '||exit 1')=
=20
> statements there. There might be two ways to fix this:
> - try to upgrade the SPARC part to the -devel branch and see if that fixe=
s=20
> it
> - drop sparc from the supported architectures (a drastic move).
I wouldn't veto against the first method since this would make maintaing
the package more difficult. Instead we might consider using the devel
branche and combining it with the documentation from the stable release,
but that still is not easy. (But at least upstream uses that for OWL.)
The latter would also be possible, but I would prefer if somebody would
investigate the build who has some knowledge about sparc. Since the
build logs show that 1.6.17 and earlier versions did build fine on
sparc. So I suppose it's some change in the build daemon or on sparc
that is responsible for this break.
Christian
--=20
Debian Developer (http://
1024D/B7CEC7E8 44BD 1F9E A997 3BE2 A44F 96A4 1C98 EEF3 B7CE C7E8
--xXmbgvnjoT4axfJE
Content-Type: application/
Content-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.4-cvs (GNU/Linux)
iEYEARECAAYFAj+
cGIAnjqvfUywy7O
=WGal
-----END PGP SIGNATURE-----
--xXmbgvnjoT4ax
Debian Bug Importer (debzilla) wrote : | #15 |
Message-ID: <email address hidden>
Date: Thu, 18 Dec 2003 17:35:12 +0100
From: Paul Slootman <email address hidden>
To: Cc: <email address hidden>
Subject: Re: Bug#220928: john: Does not build in Sparc
On Sun 16 Nov 2003, Christian Kurz wrote:
> [...]
> > Benchmarking: Standard DES [24/32 128K]... make[3]: *** [sparc.h] Error 1
>
> > So it seems to break in the 'bench' program (in some of the '||exit 1')
> > statements there. There might be two ways to fix this:
It segfaults when setting the SIGALRM signal handler at line 100 of
bench.c. This indicates to me that some sort of memory corruption has
gone on before that.
> investigate the build who has some knowledge about sparc. Since the
> build logs show that 1.6.17 and earlier versions did build fine on
> sparc. So I suppose it's some change in the build daemon or on sparc
> that is responsible for this break.
With memory corruption, it could be all sorts of things that trigger it.
Assumedly the overwriting of some buffer happens all the time, but only
now does it touch an area that's critical. This could be due to other
libc, other compiler, other kernel...
I'd recommend running on some sort of malloc debugger such as electric
fence or so. Doing this on i386 should also be effective.
Paul Slootman
Debian Bug Importer (debzilla) wrote : | #16 |
Message-ID: <email address hidden>
Date: Sun, 25 Jan 2004 12:26:25 +0100
From: Christian Kurz <email address hidden>
To: Paul Slootman <email address hidden>, <email address hidden>
Cc: Javier =?iso-8859-
Subject: Re: Bug#220928: john: Does not build in Sparc
--D9sZ58tf58331Q5M
Content-Type: text/plain; charset=us-ascii
Content-
Content-
[Cc'ing Javier, the co-maintainer.]
On [18/12/03 17:35], Paul Slootman wrote:
> On Sun 16 Nov 2003, Christian Kurz wrote:
> > [...]
> > > Benchmarking: Standard DES [24/32 128K]... make[3]: *** [sparc.h] Err=
or 1
> > > So it seems to break in the 'bench' program (in some of the '||exit 1=
')=20
> > > statements there. There might be two ways to fix this:
> It segfaults when setting the SIGALRM signal handler at line 100 of
> bench.c. This indicates to me that some sort of memory corruption has
> gone on before that.
Oh, that's not nice for me to read, considering the important task that
john does.
> > investigate the build who has some knowledge about sparc. Since the
> > build logs show that 1.6.17 and earlier versions did build fine on
> > sparc. So I suppose it's some change in the build daemon or on sparc
> > that is responsible for this break.
> With memory corruption, it could be all sorts of things that trigger it.
> Assumedly the overwriting of some buffer happens all the time, but only
> now does it touch an area that's critical. This could be due to other
> libc, other compiler, other kernel...
> I'd recommend running on some sort of malloc debugger such as electric
> fence or so. Doing this on i386 should also be effective.
Okay, we'll try it and see if that helps. I'll maybe try valgrind later.
Christian
--=20
Debian Developer (http://
1024D/B7CEC7E8 44BD 1F9E A997 3BE2 A44F 96A4 1C98 EEF3 B7CE C7E8
--D9sZ58tf58331Q5M
Content-Type: application/
Content-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.4-cvs (GNU/Linux)
iEYEARECAAYFAkA
Dv8AnjyPrwtQiHX
=rIeu
-----END PGP SIGNATURE-----
--D9sZ58tf58331
Debian Bug Importer (debzilla) wrote : | #17 |
Message-ID: <email address hidden>
Date: Tue, 30 Mar 2004 10:03:33 +0200
From: Javier =?iso-8859-
To: <email address hidden>
Subject: Any success testing malloc errors?
--8t9RHnE3ZwKMSgU+
Content-Type: text/plain; charset=iso-8859-15
Content-
Content-
Hi there,
Any success running john with valgrind/eeyes in order to find out where the=
=20
sparc issue might reside? I would hate to drop sparc from the supported=20
archs, but if we don't do it in the next upload probably the latest=20
revision (which includes quite a number of bug fixes) will not make it into=
=20
sarge in time for release...
Regards
Javier
--8t9RHnE3ZwKMSgU+
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAaSnVi4s
xCaMb2rlR7jI46A
=ngGi
-----END PGP SIGNATURE-----
--8t9RHnE3ZwKMS
Debian Bug Importer (debzilla) wrote : | #18 |
Message-ID: <20040412002637
Date: Sun, 11 Apr 2004 20:26:37 -0400
From: Justin Pryzby <email address hidden>
To: <email address hidden>
Subject: MALLOC_CHECK_
--sm4nu43k4a2Rpi4c
Content-Type: text/plain; charset=us-ascii
Content-
malloc(3) also recommends `export MALLOC_CHECK_=1`, which is very simple
and easy.
Justin
--sm4nu43k4a2Rpi4c
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAeeI8h7y
aHGbg/4E7wrBs9l
=8dyY
-----END PGP SIGNATURE-----
--sm4nu43k4a2Rp
Debian Bug Importer (debzilla) wrote : | #19 |
Message-ID: <email address hidden>
Date: Thu, 20 May 2004 22:00:43 +0200
From: Javier =?iso-8859-
To: <email address hidden>
Subject: Further information related to testing (in sparc)
--HlL+5n6rz5pIUxbD
Content-Type: text/plain; charset=iso-8859-15
Content-
Content-
I have been testing this issue further in a unstable chroot (at vore). This=
=20
bug reproduces in gcc-2.95, gcc-3.2 and gcc-3.3 in unstable. Running it=20
through a debugger:
-------
GNU gdb 6.1-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
(...)
This GDB was configured as "sparc-
"/lib/libthread
(gdb) run 1
Starting program: /home/jfs/
Benchmarking: Standard DES [24/32 128K]...
Program received signal SIGSEGV, Segmentation fault.
0x7005cf98 in __errno_location () from /lib/libc.so.6
(gdb) bt
#0 0x7005cf98 in __errno_location () from /lib/libc.so.6
#1 0x70072dc0 in __libc_sigaction () from /lib/libc.so.6
#2 0x70072ff4 in sigaction () from /lib/libc.so.6
#3 0x70072ce0 in ssignal () from /lib/libc.so.6
#4 0x0001aba0 in benchmark_format (format=3D0x2e040, salts=3D256,
results=
#5 0x0001af9c in main (argc=3D1, argv=3D0x32400) at best.c:53
-------
Bench.c (line 100) just does
If the signal call is removed it will not segfault (but will not run=20
properly either):
Benchmarking: Standard DES [24/32 128K]... Alarm clock
Christian hast said (in IRC) that it seems that the devel branch will not=
=20
compile properly on Sparc. I have succesfully tested a built on Solaris=20
over Sparc, so there seems to be an issue with the linux-specific code. I'm=
=20
not sure where the default resides (maybe libc6?). I would suggest that=20
this bug was reassigned to libc6 and that sparc support for john was=20
dropped (but this bug left open) until the issue is fixed.
Regards
Javier
--HlL+5n6rz5pIUxbD
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFArQ5ri4s
ERgrjqDT9ED2rXe
=IuDm
-----END PGP SIGNATURE-----
--HlL+5n6rz5pIU
Debian Bug Importer (debzilla) wrote : | #20 |
Message-ID: <email address hidden>
Date: Wed, 2 Jun 2004 15:23:25 -0300
From: "Guilherme de S. Pastore" <email address hidden>
To: <email address hidden>
Subject: Damn, forgot it
package john
tag 220928 pending
thanks
Upstream provided a patch. Our problems with Sparc should now be over. It=
will
be incorporated to the CVS@Alioth tonight (as soon as I get home).
--=20
Guilherme de S. Pastore
<email address hidden>
Debian Bug Importer (debzilla) wrote : | #21 |
Message-Id: <20040603231101
Date: Thu, 3 Jun 2004 23:11:01 -0300
From: "Guilherme de S. Pastore" <email address hidden>
To: <email address hidden>
Subject: Ugh...
package john
tag 220928 -pending
tag 252506 pending
thanks
--
Guilherme de S. Pastore (fatalerror)
<email address hidden>
Debian Bug Importer (debzilla) wrote : | #22 |
Message-ID: <email address hidden>
Date: Fri, 18 Jun 2004 00:21:47 +0200
From: Javier =?iso-8859-
To: <email address hidden>
Subject: Tagging
--l76fUT7nc3MelDdI
Content-Type: text/plain; charset=iso-8859-15
Content-
Content-
tags 252206 pending
tags 252506 pending
tags 251227 pending
tags 253194 pending
tags 220928 pending
thanks
All these bugs are pending an upload since the code fixing them has already=
=20
been commited to CVS...
Javier
--l76fUT7nc3MelDdI
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA0hl7i4s
TgMcIXAqWQxv2t7
=QQDc
-----END PGP SIGNATURE-----
--l76fUT7nc3Mel
Debian Bug Importer (debzilla) wrote : | #23 |
Message-Id: <email address hidden>
Date: Sun, 20 Jun 2004 11:17:02 -0400
From: Javier Fernandez-Sanguino Pen~a <email address hidden>
To: <email address hidden>
Cc: Javier Fernandez-Sanguino Pen~a <email address hidden>,
<email address hidden> (Guilherme de S. Pastore)
Subject: Fixed in upload of john 1.6.36-2 to experimental
tag 117213 + fixed-in-
tag 213164 + fixed-in-
tag 220928 + fixed-in-
tag 251095 + fixed-in-
tag 251172 + fixed-in-
tag 79831 + fixed-in-
quit
This message was generated automatically in response to an
upload to the experimental distribution. The .changes file follows.
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.7
Date: Tue, 8 Jun 2004 19:30:18 +0200
Source: john
Binary: john
Architecture: source i386
Version: 1.6.36-2
Distribution: experimental
Urgency: low
Maintainer: Guilherme de S. Pastore <email address hidden>
Changed-By: Javier Fernandez-Sanguino Pen~a <email address hidden>
Description:
john - An active password cracking tool
Closes: 79831 79831 117213 213164 220928 251095 251172
Changes:
john (1.6.36-2) experimental; urgency=low
.
* Moved -DJOHN_SYSTEM_WIDE from CPPFLAGS to CFLAGS were it should have
been in the first place. This makes john usable for both system-wide
use and per-user use. User files are located in ~/.john
even though users will need to copy the john.conf provided
file to that directory (Closes: #79831, #117213, #79831)
* Introduced --config and --private options in John's code to be able
to define specific configuration files and location of John's record
and log files per run, this fixes some of the requests filed in #110139.
It is currently a hack, however.
* Introduced a testbuild system (based on ifupdown's) which enables
the build system to test wether the compiled 'john-any' binary
can properly crack some simple passwords. This might be useful to
detect errors in autobuilders.
* Sparc support is done throught the 'generic' target since Solar
Designer says its the way to go and, in any case, the assembly code
which makes the binary not work might be removed in the future. This
should make the build work on Sparc again. Note that, for the moment
support for other architectures will be provided only in the
'experimental' package (Closes: #220928)
* Added a mechanism to detect if the passwords files have changed
(a new user has been added, a password has been modified, etc...) when
restoring the cron job so that John will use the latest password files.
The current implementation is rather "fine-grained" so it will start
again even if a user's name, uid, or gid is changed. Further
reimplemen
username or password has been modified.
(Closes: #251172)
* Major rewrite of the cronjob which will now work as follows:
* 'start' will run john in background instead of waiting for it to finish
* 'stop' will stop john and will call mailer if needed
Other changes include:
-Stale files are now rem...
Debian Bug Importer (debzilla) wrote : | #24 |
Message-ID: <email address hidden>
Date: Mon, 21 Jun 2004 17:25:26 -0300
From: "Guilherme de S. Pastore" <email address hidden>
To: <email address hidden>
Subject: Bug fixed, no need for help
package john
tag 220928 -help
severity 220928 serious
quit
Matt Zimmerman (mdz) wrote : | #26 |
This bug is sparc-specific
In Debian Bug tracker #220928, Guilherme de S. Pastore (fatalerror) wrote : Bug#220928: fixed in john 1.6-28 | #27 |
Source: john
Source-Version: 1.6-28
We believe that the bug you reported is fixed in the latest version of
john, which is due to be installed in the Debian FTP archive:
john_1.6-28.diff.gz
to pool/main/
john_1.6-28.dsc
to pool/main/
john_1.
to pool/main/
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Guilherme de S. Pastore <email address hidden> (supplier of updated john package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Thu, 27 May 2004 18:14:28 -0300
Source: john
Binary: john
Architecture: source i386
Version: 1.6-28
Distribution: unstable
Urgency: medium
Maintainer: Guilherme de S. Pastore <email address hidden>
Changed-By: Guilherme de S. Pastore <email address hidden>
Description:
john - An active password cracking tool
Closes: 138689 141741 213164 220928 224883 228750 229597 251095 251172 251227 252206 252506 253194
Changes:
john (1.6-28) unstable; urgency=medium
.
* Ported debian/rules to use CDBS
- Removed debian/conffiles, debhelper handles this
- Uses debian/dirs and others instead of polluting debian/rules
- Made cleanups and removed things that remained there from older
releases, such as unnecessary directories
* Bumped Standards-Version to 3.6.1.1
* Moved manpages to section 8 (Closes: #252206)
- Fixed problems (Closes: #252506)
* Re-added sparc support with generic target (Closes: #220928)
* Added real alternative to suggestion on wordlist
* Removed lintian/linda overrides, don't need them anymore
* Moved configuration files to /etc/john/ (Closes: #141741, #229597)
* Only check for configuration file in config if it's an upgrade
(Closes: #251227, #253194)
* Added patch from Goswin von Brederlow to avoid segfaults when
casting signed char to unsigned int on amd64 (Closes: #251095)
* Added clarification to the manpage about having to run john with
-show from the same directory where the password was cracked, so
that it works (Closes: #228750)
[ Javier Fernandez-Sanguino ]
* Build on all architectures Debian supports, using the 'generic'
target for the ones not supported by john (Closes: #138689, #224883)
* Major rewrite of the cronjob which will now work as follows:
- Mailer uses the latest password file to avoid mailing users warning
about passwords if they have changed it (Closes: #251172)
- This new cronjob will now restore interrupted sessions correctly
(and uses the new john.rec files) (Closes: #213164)
Files:
a40b501e335c57
44c2f1b5b6a900
Debian Bug Importer (debzilla) wrote : | #28 |
Message-Id: <email address hidden>
Date: Mon, 12 Jul 2004 17:47:14 -0400
From: <email address hidden> (Guilherme de S. Pastore)
To: <email address hidden>
Subject: Bug#220928: fixed in john 1.6-28
Source: john
Source-Version: 1.6-28
We believe that the bug you reported is fixed in the latest version of
john, which is due to be installed in the Debian FTP archive:
john_1.6-28.diff.gz
to pool/main/
john_1.6-28.dsc
to pool/main/
john_1.
to pool/main/
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Guilherme de S. Pastore <email address hidden> (supplier of updated john package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Thu, 27 May 2004 18:14:28 -0300
Source: john
Binary: john
Architecture: source i386
Version: 1.6-28
Distribution: unstable
Urgency: medium
Maintainer: Guilherme de S. Pastore <email address hidden>
Changed-By: Guilherme de S. Pastore <email address hidden>
Description:
john - An active password cracking tool
Closes: 138689 141741 213164 220928 224883 228750 229597 251095 251172 251227 252206 252506 253194
Changes:
john (1.6-28) unstable; urgency=medium
.
* Ported debian/rules to use CDBS
- Removed debian/conffiles, debhelper handles this
- Uses debian/dirs and others instead of polluting debian/rules
- Made cleanups and removed things that remained there from older
releases, such as unnecessary directories
* Bumped Standards-Version to 3.6.1.1
* Moved manpages to section 8 (Closes: #252206)
- Fixed problems (Closes: #252506)
* Re-added sparc support with generic target (Closes: #220928)
* Added real alternative to suggestion on wordlist
* Removed lintian/linda overrides, don't need them anymore
* Moved configuration files to /etc/john/ (Closes: #141741, #229597)
* Only check for configuration file in config if it's an upgrade
(Closes: #251227, #253194)
* Added patch from Goswin von Brederlow to avoid segfaults when
casting signed char to unsigned int on amd64 (Closes: #251095)
* Added clarification to the manpage about having to run john with
-show from the same directory where the password was cracked, so
that it works (Closes: #228750)
[ Javier Fernandez-Sanguino ]
* Build on all architectures Debian supports, using the 'generic'
target for the ones not supported by john (Closes: #138689, #224883)
* Major rewrite of the cronjob which will now work as follows:
- Mailer uses the latest password file to avoid mailing users warning
about passwords if they have changed it (Closes: #251172)
- This new cronjob will ...
Daniel Robitaille (robitaille) wrote : | #29 |
Fixed in Debian with this upload:
john (1.6-28) unstable; urgency=medium
* Re-added sparc support with generic target (Closes: #220928)
-- Guilherme de S. Pastore <email address hidden> Thu, 27 May 2004 18:14:28 -0300
Changed in john: | |
status: | Unconfirmed → Fix Released |
Changed in john: | |
status: | Unknown → Fix Released |
On [15/11/03 19:18], Javier Fernández-Sanguino Peña wrote:
> Package: john
> Version: 1.6-19
> Tags: help confirmed
> John does not build in the buildd environments for Sparc since release
> 1.6-19. It seems this is a problem in the build, and not in the package,
> since the bugs which prevented it from building [1] have been fixed in
> 1.6-22 and it still will not build [2].
> The build ends with:
[...]
> Benchmarking: Standard DES [24/32 128K]... make[3]: *** [sparc.h] Error 1
> So it seems to break in the 'bench' program (in some of the '||exit 1')
> statements there. There might be two ways to fix this:
> - try to upgrade the SPARC part to the -devel branch and see if that fixes
> it
> - drop sparc from the supported architectures (a drastic move).
I wouldn't veto against the first method since this would make maintaing
the package more difficult. Instead we might consider using the devel
branche and combining it with the documentation from the stable release,
but that still is not easy. (But at least upstream uses that for OWL.)
The latter would also be possible, but I would prefer if somebody would
investigate the build who has some knowledge about sparc. Since the
build logs show that 1.6.17 and earlier versions did build fine on
sparc. So I suppose it's some change in the build daemon or on sparc
that is responsible for this break.
Christian www.debian. org)
--
Debian Developer (http://
1024D/B7CEC7E8 44BD 1F9E A997 3BE2 A44F 96A4 1C98 EEF3 B7CE C7E8