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
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [pycrypto] 'tis done: Python3 with PyCrypto
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:pycrypto%40lists.dlitz.net?Subject=%5Bpycrypto%5D%20%27tis%20done%3A%20Python3%20with%20PyCrypto&In-Reply-To=2e5e0f645584e65dc50d25cb3578820a%40amberfisharts.com">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000375.html">
<LINK REL="Next" HREF="000378.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[pycrypto] 'tis done: Python3 with PyCrypto</H1>
<B>Thorsten Behrens</B>
<A HREF="mailto:pycrypto%40lists.dlitz.net?Subject=%5Bpycrypto%5D%20%27tis%20done%3A%20Python3%20with%20PyCrypto&In-Reply-To=2e5e0f645584e65dc50d25cb3578820a%40amberfisharts.com"
TITLE="[pycrypto] 'tis done: Python3 with PyCrypto">sbehrens at gmx.li
</A><BR>
<I>Tue Jan 4 14:14:43 CST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="000375.html">[pycrypto] 'tis done: Python3 with PyCrypto
</A></li>
<LI>Next message: <A HREF="000378.html">[pycrypto] 'tis done: Python3 with PyCrypto
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#377">[ date ]</a>
<a href="thread.html#377">[ thread ]</a>
<a href="subject.html#377">[ subject ]</a>
<a href="author.html#377">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Thanks! I'll take a look. Also: Well oops. The test_AllOrNothing.py file
is now staged.
On 1/4/2011 2:16 PM, <A HREF="http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto">don at amberfisharts.com</A> wrote:
><i> Hey Thorsten,
</I>><i>
</I>><i> I have a small patch you might want to include in your branch before
</I>><i> it merges.
</I>><i> It does three things:
</I>><i> * fix a typo in your new docs
</I>><i> * fixes a bug in the randrange unittests
</I>><i> * adds some more tests for randrange and shuffle
</I>><i>
</I>><i> Furthermore it seems that you didn't commit the test_AllOrNothing.py
</I>><i> file.
</I>><i>
</I>><i> Let me thank you once more for your determined and -it seems-
</I>><i> successful push for py3k support.
</I>><i>
</I>><i> Cheers,
</I>><i> Lorenz
</I>><i>
</I>><i>
</I>><i> On Mon, 03 Jan 2011 22:42:32 -0500, Thorsten Behrens <<A HREF="http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto">sbehrens at gmx.li</A>>
</I>><i> wrote:
</I>>><i> I've done what I will on the py3k branch. It's been tested on 2.1, 2.2,
</I>>><i> 2.7, 3.1 and 3.2.
</I>>><i>
</I>>><i> AllOrNothing unit tests are now in and show AllOrNothing failing
</I>>><i> occasionally. This has always been the case. The unit test just forces
</I>>><i> the failure. Since I highly suspect that no-one actually uses
</I>>><i> AllOrNothing.py - or these errors would have been detected before now -
</I>>><i> I am not going to tackle that particular piece further. Others are more
</I>>><i> than welcome to, of course!
</I>>><i>
</I>>><i> I have updated the documentation that ships with pycrypto, adding
</I>>><i> comments on the (in)security of the algorithms included, such as
</I>>><i> MD2/4/5, SHA1, ARC2, ARC4. Please do have a look. These changes bear
</I>>><i> verification by others. I may well have asserted that which is not true,
</I>>><i> or distorted a fact here and there.
</I>>><i>
</I>>><i> I've issued a pull request. I'm happy to make further changes if there
</I>>><i> should be something I overlooked and that the unit tests did not expose.
</I>>><i> But barring that, I consider the porting effort complete. All further
</I>>><i> work - such as dealing with the errors in AllOrNothing.py and
</I>>><i> random.sample() (the latter is an issue in Python 2.1 only), dealing
</I>>><i> with security concerns in Elgamal.py, deciding the fate of qNEW - I'd
</I>>><i> like to keep to trunk. I've made quite enough changes already on this
</I>>><i> private branch.
</I>>><i>
</I>>><i> Yours
</I>>><i> Thorsten
</I>>><i>
</I>>><i> _______________________________________________
</I>>><i> pycrypto mailing list
</I>>><i> <A HREF="http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto">pycrypto at lists.dlitz.net</A>
</I>>><i> <A HREF="http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto">http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto</A>
</I>><i>
</I>><i>
</I>><i> _______________________________________________
</I>><i> pycrypto mailing list
</I>><i> <A HREF="http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto">pycrypto at lists.dlitz.net</A>
</I>><i> <A HREF="http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto">http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto</A>
</I>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <A HREF="http://lists.dlitz.net/pipermail/pycrypto/attachments/20110104/65751368/attachment-0001.htm">http://lists.dlitz.net/pipermail/pycrypto/attachments/20110104/65751368/attachment-0001.htm</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000375.html">[pycrypto] 'tis done: Python3 with PyCrypto
</A></li>
<LI>Next message: <A HREF="000378.html">[pycrypto] 'tis done: Python3 with PyCrypto
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#377">[ date ]</a>
<a href="thread.html#377">[ thread ]</a>
<a href="subject.html#377">[ subject ]</a>
<a href="author.html#377">[ author ]</a>
</LI>
</UL>
<hr>
<a href="http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto">More information about the pycrypto
mailing list</a><br>
</body></html>
|
