summaryrefslogtreecommitdiff
path: root/pipermail/pycrypto/2010q4/000299.html
diff options
context:
space:
mode:
Diffstat (limited to 'pipermail/pycrypto/2010q4/000299.html')
-rw-r--r--pipermail/pycrypto/2010q4/000299.html78
1 files changed, 78 insertions, 0 deletions
diff --git a/pipermail/pycrypto/2010q4/000299.html b/pipermail/pycrypto/2010q4/000299.html
new file mode 100644
index 0000000..d619a86
--- /dev/null
+++ b/pipermail/pycrypto/2010q4/000299.html
@@ -0,0 +1,78 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [pycrypto] Blowfish breaks between versions 2.0.1 and 2.3
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:pycrypto%40lists.dlitz.net?Subject=%5Bpycrypto%5D%20Blowfish%20breaks%20between%20versions%202.0.1%20and%202.3&In-Reply-To=">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="000293.html">
+ <LINK REL="Next" HREF="000300.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[pycrypto] Blowfish breaks between versions 2.0.1 and 2.3</H1>
+ <B>Eric Chamberlain</B>
+ <A HREF="mailto:pycrypto%40lists.dlitz.net?Subject=%5Bpycrypto%5D%20Blowfish%20breaks%20between%20versions%202.0.1%20and%202.3&In-Reply-To="
+ TITLE="[pycrypto] Blowfish breaks between versions 2.0.1 and 2.3">eric at rf.com
+ </A><BR>
+ <I>Wed Dec 8 21:29:24 CST 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="000293.html">[pycrypto] PyCrypto TSU NOTIFICATION
+</A></li>
+ <LI>Next message: <A HREF="000300.html">[pycrypto] Rewrite bcrypt in PyCrypto so we can use it on Google App Engine
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#299">[ date ]</a>
+ <a href="thread.html#299">[ thread ]</a>
+ <a href="subject.html#299">[ subject ]</a>
+ <a href="author.html#299">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Hello,
+
+With version 2.0.1 our code works fine, but after upgrading to 2.3,
+
+ blowfish = Blowfish.new(SECRET_KEY)
+
+generates the following error:
+
+ ValueError: Maximum key size is 448 bits
+
+Our SECRET_KEYs are 74 ASCII characters long and we can't easily change them, given the amount of data encrypted with the keys.
+
+Is it possible to bring back the 2.0.1 behavior and allow keys of arbitrary length?
+
+--
+Eric Chamberlain
+
+
+
+
+</PRE>
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="000293.html">[pycrypto] PyCrypto TSU NOTIFICATION
+</A></li>
+ <LI>Next message: <A HREF="000300.html">[pycrypto] Rewrite bcrypt in PyCrypto so we can use it on Google App Engine
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#299">[ date ]</a>
+ <a href="thread.html#299">[ thread ]</a>
+ <a href="subject.html#299">[ subject ]</a>
+ <a href="author.html#299">[ 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>