summaryrefslogtreecommitdiff
path: root/pipermail/pycrypto/2008q4/000042.html
blob: b9ffb1f03aa9f34ee4e8c1ae26b02267b827e801 (plain)
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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [pycrypto] the sad state of pycrypto
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:pycrypto%40lists.dlitz.net?Subject=%5Bpycrypto%5D%20the%20sad%20state%20of%20pycrypto&In-Reply-To=1e267dfe0811090754n5f96cf22ud92ea02458600505%40mail.gmail.com">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="000051.html">
   <LINK REL="Next"  HREF="000043.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[pycrypto] the sad state of pycrypto</H1>
    <B>zooko</B> 
    <A HREF="mailto:pycrypto%40lists.dlitz.net?Subject=%5Bpycrypto%5D%20the%20sad%20state%20of%20pycrypto&In-Reply-To=1e267dfe0811090754n5f96cf22ud92ea02458600505%40mail.gmail.com"
       TITLE="[pycrypto] the sad state of pycrypto">zooko at zooko.com
       </A><BR>
    <I>Sun Nov  9 10:58:00 CST 2008</I>
    <P><UL>
        <LI>Previous message: <A HREF="000051.html">[pycrypto] the sad state of pycrypto
</A></li>
        <LI>Next message: <A HREF="000043.html">[pycrypto] the sad state of pycrypto
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#42">[ date ]</a>
              <a href="thread.html#42">[ thread ]</a>
              <a href="subject.html#42">[ subject ]</a>
              <a href="author.html#42">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Nov 9, 2008, at 8:54 AM, Paul Hoffman wrote:

&gt;<i> The idea of dropping support for &quot;weak&quot; algorithms is silly. No  
</I>&gt;<i> developer looks through the list of algorithms in a library and say  
</I>&gt;<i> &quot;I'll pick, um, er, that one&quot; without knowing what it is.
</I>
I happen to know a somewhat famous developer who once looked through  
the Crypto++ API and chose DES-XEX without (I think) realizing that  
it was DES-X and not Triple-DES.

But yeah, modelling the developers who use your library -- guessing  
how clueful and careful they will be -- is a black art and is  
probably doomed to failure.

Regards,

Zooko
</PRE>





<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="000051.html">[pycrypto] the sad state of pycrypto
</A></li>
	<LI>Next message: <A HREF="000043.html">[pycrypto] the sad state of pycrypto
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#42">[ date ]</a>
              <a href="thread.html#42">[ thread ]</a>
              <a href="subject.html#42">[ subject ]</a>
              <a href="author.html#42">[ 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>