-----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 PROTECTED]>
Changed-By: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
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
reimplementations might be improved so they only restart if either a
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 is 'chowned' to him) and could make it
possible to avoid the --private option (by creating a user
whose $HOME dir is /var/lib/john)
- This new cronjob will now restore interrupted sessions correctly
(and uses the new john.rec files) (Closes: #213164)
- Use the --private option (--config is not used so that the
admin can overwrite the generic options by setting up a different
john.conf if necessary)
* Changed mailer so it uses the new --private option
* Remove /var/run/john and /etc/john on purge
[ Changes by Goswin von Brederlow]
* Remove segfaults in src/loader.c and src/rules.c (Closes: #251095)
* Broader generic definition based on architecture to avoid stating
each architecture separately
Files:
18886617cd79373ecc89732956829be7 778 admin optional john_1.6.36-2.dsc
3e7535dddf5a476e8667ef47ec87cdb3 481953 admin optional john_1.6.36-2.diff.gz
01431a834ece091392d5e5c6edead7ef 547350 admin optional john_1.6.36-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iQCVAwUBQNWmSvtEPvakNq0lAQE/cAP/VvshPo6Stq/Q1kFvv2CAtF56qtmOgwBf
GZx/Fy2PaEBgYZSsDEyiBhHUqtvZw25f5rV2Yc1TeaUcoemyuJi04IA/E2yCSMwp
8LCv/YiesWS88eGM5KRb4xstXnV9VqqKv7noYBqZIUGQSK9dL1rZbw8WJWYPhlqv
lxFO5ZQKZvo=
=kUhj
-----END PGP SIGNATURE-----
Accepted:
john_1.6.36-2.diff.gz
to pool/main/j/john/john_1.6.36-2.diff.gz
john_1.6.36-2.dsc
to pool/main/j/john/john_1.6.36-2.dsc
john_1.6.36-2_i386.deb
to pool/main/j/john/john_1.6.36-2_i386.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
