summaryrefslogtreecommitdiff
path: root/pipermail/pycrypto/2011q1/000375.html
diff options
context:
space:
mode:
Diffstat (limited to 'pipermail/pycrypto/2011q1/000375.html')
-rw-r--r--pipermail/pycrypto/2011q1/000375.html124
1 files changed, 124 insertions, 0 deletions
diff --git a/pipermail/pycrypto/2011q1/000375.html b/pipermail/pycrypto/2011q1/000375.html
new file mode 100644
index 0000000..d9ab8c9
--- /dev/null
+++ b/pipermail/pycrypto/2011q1/000375.html
@@ -0,0 +1,124 @@
+<!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=4D229728.2000109%40gmx.li">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="000374.html">
+ <LINK REL="Next" HREF="000377.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[pycrypto] 'tis done: Python3 with PyCrypto</H1>
+ <B>don at amberfisharts.com</B>
+ <A HREF="mailto:pycrypto%40lists.dlitz.net?Subject=%5Bpycrypto%5D%20%27tis%20done%3A%20Python3%20with%20PyCrypto&In-Reply-To=4D229728.2000109%40gmx.li"
+ TITLE="[pycrypto] 'tis done: Python3 with PyCrypto">don at amberfisharts.com
+ </A><BR>
+ <I>Tue Jan 4 13:16:15 CST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="000374.html">[pycrypto] 'tis done: Python3 with PyCrypto
+</A></li>
+ <LI>Next message: <A HREF="000377.html">[pycrypto] 'tis done: Python3 with PyCrypto
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#375">[ date ]</a>
+ <a href="thread.html#375">[ thread ]</a>
+ <a href="subject.html#375">[ subject ]</a>
+ <a href="author.html#375">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE> Hey Thorsten,
+
+ I have a small patch you might want to include in your branch before it
+ merges.
+ It does three things:
+ * fix a typo in your new docs
+ * fixes a bug in the randrange unittests
+ * adds some more tests for randrange and shuffle
+
+ Furthermore it seems that you didn't commit the test_AllOrNothing.py
+ file.
+
+ Let me thank you once more for your determined and -it seems-
+ successful push for py3k support.
+
+ Cheers,
+ Lorenz
+
+
+ On Mon, 03 Jan 2011 22:42:32 -0500, Thorsten Behrens &lt;<A HREF="http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto">sbehrens at gmx.li</A>&gt;
+ wrote:
+&gt;<i> I've done what I will on the py3k branch. It's been tested on 2.1,
+</I>&gt;<i> 2.2,
+</I>&gt;<i> 2.7, 3.1 and 3.2.
+</I>&gt;<i>
+</I>&gt;<i> AllOrNothing unit tests are now in and show AllOrNothing failing
+</I>&gt;<i> occasionally. This has always been the case. The unit test just
+</I>&gt;<i> forces
+</I>&gt;<i> the failure. Since I highly suspect that no-one actually uses
+</I>&gt;<i> AllOrNothing.py - or these errors would have been detected before now
+</I>&gt;<i> -
+</I>&gt;<i> I am not going to tackle that particular piece further. Others are
+</I>&gt;<i> more
+</I>&gt;<i> than welcome to, of course!
+</I>&gt;<i>
+</I>&gt;<i> I have updated the documentation that ships with pycrypto, adding
+</I>&gt;<i> comments on the (in)security of the algorithms included, such as
+</I>&gt;<i> MD2/4/5, SHA1, ARC2, ARC4. Please do have a look. These changes bear
+</I>&gt;<i> verification by others. I may well have asserted that which is not
+</I>&gt;<i> true,
+</I>&gt;<i> or distorted a fact here and there.
+</I>&gt;<i>
+</I>&gt;<i> I've issued a pull request. I'm happy to make further changes if
+</I>&gt;<i> there
+</I>&gt;<i> should be something I overlooked and that the unit tests did not
+</I>&gt;<i> expose.
+</I>&gt;<i> But barring that, I consider the porting effort complete. All further
+</I>&gt;<i> work - such as dealing with the errors in AllOrNothing.py and
+</I>&gt;<i> random.sample() (the latter is an issue in Python 2.1 only), dealing
+</I>&gt;<i> with security concerns in Elgamal.py, deciding the fate of qNEW - I'd
+</I>&gt;<i> like to keep to trunk. I've made quite enough changes already on this
+</I>&gt;<i> private branch.
+</I>&gt;<i>
+</I>&gt;<i> Yours
+</I>&gt;<i> Thorsten
+</I>&gt;<i>
+</I>&gt;<i> _______________________________________________
+</I>&gt;<i> pycrypto mailing list
+</I>&gt;<i> <A HREF="http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto">pycrypto at lists.dlitz.net</A>
+</I>&gt;<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 --------------
+A non-text attachment was scrubbed...
+Name: py3k_branch.patch
+Type: text/x-diff
+Size: 2248 bytes
+Desc: not available
+Url : <A HREF="http://lists.dlitz.net/pipermail/pycrypto/attachments/20110104/d4594010/attachment.patch">http://lists.dlitz.net/pipermail/pycrypto/attachments/20110104/d4594010/attachment.patch</A>
+</PRE>
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="000374.html">[pycrypto] 'tis done: Python3 with PyCrypto
+</A></li>
+ <LI>Next message: <A HREF="000377.html">[pycrypto] 'tis done: Python3 with PyCrypto
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#375">[ date ]</a>
+ <a href="thread.html#375">[ thread ]</a>
+ <a href="subject.html#375">[ subject ]</a>
+ <a href="author.html#375">[ 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>