1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
# ChangeLog for app-crypt/johntheripper
# Copyright 2002-2004 Gentoo Technologies, Inc.; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/app-crypt/johntheripper/ChangeLog,v 1.11 2004/05/18 04:09:39 dragonheart Exp $
*johntheripper-1.6-r2 (18 May 2004)
18 May 2004; Daniel Black <dragonheart@gentoo.org>
+files/john-ntlm.skey.patch, +johntheripper-1.6-r2.ebuild
+metadata.xml:
fixes thanks to Ghislain Bourgeois ghislain48@hotmail.com in bug #49988.
All patches are patching the same area of code. mysql dropped due
conficts with other patches.
01 Oct 2003; Tavis Ormandy <taviso@gentoo.org> johntheripper-1.6.ebuild:
Stable on alpha
13 Feb 2003; Guy Martin <gmsoft@gentoo.org> johntheripper-1.6.ebuild :
Changed keyword ~hppa to hppa.
*johntheripper-1.6-r1 (13 Feb 2003)
13 Feb 2003; <zhen@gentoo.org> johntheripper-1.6-r1.ebuild files/digest-johntheripper-1.6-r1 :
new version that uses patches for ntlm, mysql, etc password cracking
13 Feb 2003; <zhen@gentoo.org> johntheripper-1.6-r1.ebuild files/digest-johntheripper-1.6-r1 :
new
*johntheripper-1.6 (22 May 2002)
28 Mar 2003; Pieter Van den Abeele <pvdabeel@gentoo.org> johntheripper-1.6.ebuild :
Moved to stable ppc
09 Feb 2003; Seemant Kulleen <seemant@gentoo.org> johntheripper-1.6.ebuild :
Changed to use epatch. Also, changed sed expression delimiters from / to
:, closing bug #15006 by Blu3 <david+gentoo.org@blue-labs.org>
06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
22 May 2002; Grant Goodyear <g2boojum@gentoo.org>
New package. I use the debian patch because it contains some
useful hacks to make john fit in an LFS filesystem (not to
mention man pages).
-- Explanation of ChangeLog format:
Every new version or revision of the package should be marked by a '*'
seperator line as above. Changes since the last revision have to be added to
the top of the file, underneath the initial copyright and cvs header
comments, in exactly the same format as this comment.
This means that you start with header line that has the following format,
indented two spaces:
DD MMM YYYY; your_name <your_email> changed_file1, changed_file2: Your
explanation should follow. It should be indented and wrapped at a line width
of 80 characters. The changed_files can be omitted if they are obvious; for
example, if you are only modifying the .ebuild file and committing a new rev
of a package. Any details about what exactly changed in the code should be
added as a message when the changes are committed to cvs, not in this file.
|
GitWeb
