summaryrefslogtreecommitdiff
path: root/pipermail/pycrypto/2008q3/000001.html
blob: aadc2bb598ba149e497341040f3fbdb46209a482 (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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [pycrypto] What to do about RandomPool
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:pycrypto%40lists.dlitz.net?Subject=%5Bpycrypto%5D%20What%20to%20do%20about%20RandomPool&In-Reply-To=20080722002526.GA14858%40rivest.dlitz.net">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="000000.html">
   <LINK REL="Next"  HREF="000002.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[pycrypto] What to do about RandomPool</H1>
    <B>Paul Hoffman</B> 
    <A HREF="mailto:pycrypto%40lists.dlitz.net?Subject=%5Bpycrypto%5D%20What%20to%20do%20about%20RandomPool&In-Reply-To=20080722002526.GA14858%40rivest.dlitz.net"
       TITLE="[pycrypto] What to do about RandomPool">paul.hoffman at gmail.com
       </A><BR>
    <I>Tue Jul 22 09:08:17 CST 2008</I>
    <P><UL>
        <LI>Previous message: <A HREF="000000.html">[pycrypto] What to do about RandomPool
</A></li>
        <LI>Next message: <A HREF="000002.html">[pycrypto] What to do about RandomPool
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1">[ date ]</a>
              <a href="thread.html#1">[ thread ]</a>
              <a href="subject.html#1">[ subject ]</a>
              <a href="author.html#1">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Mon, Jul 21, 2008 at 5:25 PM, Dwayne C. Litzenberger &lt;<A HREF="http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto">dlitz at dlitz.net</A>&gt; wrote:
&gt;<i> I'm not sure that PyCrypto is the right place to implement a good RNG,
</I>&gt;<i> anyway.
</I>
...much less a bad one. :-)

&gt;<i> Would there be any objection to replacing RandomPool with a simple wrapper
</I>&gt;<i> around os.urandom? A quick benchmark shows that reading from /dev/urandom on
</I>&gt;<i> Linux is about 10-50x faster than using RandomPool.
</I>
No objection here.
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="000000.html">[pycrypto] What to do about RandomPool
</A></li>
	<LI>Next message: <A HREF="000002.html">[pycrypto] What to do about RandomPool
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1">[ date ]</a>
              <a href="thread.html#1">[ thread ]</a>
              <a href="subject.html#1">[ subject ]</a>
              <a href="author.html#1">[ 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>