- cypherpunks-legacy - lists.cpunks.org

Last chance for lower rates
by Amy Thayer 25 Mar '06

25 Mar '06

1 0

Hey sweetie, hope you're well
by Reyna Miller 25 Mar '06

25 Mar '06

1 0

Pre-approved Application #072957388 Fri, 24 Mar 2006 22:02:22 -0600
by Dean Kaufman 24 Mar '06

24 Mar '06

1 0

Re: FREE HoddiaLife!
by Ora Gorman 24 Mar '06

24 Mar '06

own hard fate. Just as they were beginning to eat, someone dragged from my reverie of watching the passive screen to the Yet instead of being used to foster love, self realization and

1 0

Ratess will skyrocket soon
by Cornelia Lockwood 24 Mar '06

24 Mar '06

1 0

Pre-approved Application #jkwpL006852150
by Etta Murillo 24 Mar '06

24 Mar '06

1 0

Pre-approved Application #UEASJ08718
by Nolan Oneal 24 Mar '06

24 Mar '06

1 0

for the bored: test an iso (esp those with via padlock hw)
by coderman 24 Mar '06

24 Mar '06

if you'd like to help me test some crypto pieces the following ISO includes a test mode which gathers stats and hardware info. feel free to trim whatever from this report and send me the remainder. additional modes support a network-less key management mode and a network enabled instance and cd/dvd writing clone mode. i'm curious about the following mainly: - does it boot? - is network hardware (no wireless) detected in 'net' target? - does entropy mgmt on VIA hardware work? (c5test/c5keys/c5net) - does the clonecd/clonedvd work with your hardware? (clone) - are the key mgmt tools provided sufficient/working? (gpg, openssl, ssh) feedback appreciated. please note the test mode may take a loooong time (30 mins not uncommon). also note you may be left with a single seeder on a slow DSL line, which might take a while as well. src for mtrngd and modified hw_random in src/ on the iso. these bits need some work... thanks http://home.peertech.org:65534/test.iso.torrent gpg --print-md sha256 test.iso test.iso: C7096E4F 76F6AE52 F3E61058 0C269EC3 9C2A1478 B11DDDC5 0664F9F 864DDB44 you can run this without any disks for the security conscious. the full project is intended for release at defcon this year. hope to see you there. (not as a presentation, we just like to geek out. and i'll try to be sober this year but no promises!)

2 3

[perry@piermont.com: Greek officials were tapped using law enforcement back door]
by Eugen Leitl 24 Mar '06

24 Mar '06

----- Forwarded message from "Perry E. Metzger" <perry(a)piermont.com> -----

1 0

entropy status / benchmarks [was test an iso]
by coderman 24 Mar '06

24 Mar '06

On 3/16/06, coderman <coderman(a)gmail.com> wrote: > ... > - does entropy mgmt on VIA hardware work? (c5test/c5keys/c5net) for those with VIA/Intel/AMD hw entropy device support and a running mtrngd you can get current status via '/etc/rc.d/rcS.mtrngd status'. logs are in /var/log/mtrngd/. i'd be interesting in knowing run times for large amounts of entropy gathered and mixed to /dev/random (gigabytes if it remains stable for that long). particularly for the Intel and AMD hw devices which i do not currently have at my disposal for testing. status output is similar to the following; sizes are in Bytes, times/stats are in microseconds (not milli): [Fri Mar 24 08:46:14-459926] Current MTRNGD Status: bad fips blocks ......: 13080 monobit failures ___: 3359 poker run failures _: 542707 bit run failures __: 1104377 long run failures __: 9687 cont run failures __: 35 good fips blocks .....: 41614750 hwrng read bytes .....: 104069575000 entropy add bytes ....: 104036872320 random writeable cnt .: 541858710 hw entropy read stats ....: min: 2479 avg: 3359 max: 22788 total: 139833561751 rng fips check stats .....: min: 904 avg: 919 max: 6464 total: 38267989605 random recv starve stats .: min: 3416 avg: 4305 max: 24018 total: 179159453561 you can stress /dev/random via 'bench-rng /dev/random 1024 1000000' or simply 'cat /dev/random > /dev/null'. uptime would be helpful. note that i accidentally left "forgiving fips check" set in the rcS.mtrngd script; this can be turned off for a better real world test. the forgiving option does not fail blocks with poker or bit runs. monobit, long, and continuous runs are always critical and the block is discarded. the FIPS check block size is 1500 bytes. see http://csrc.nist.gov/fips/fips1401.htm for more info. by default entropy density is at 80% so take that into consideration when calculating available /dev/random throughput. ex: entropy add bytes ....: 104036872320 x 0.80 == 83,229,497,856 Bytes of actual entropy added to /dev/random pool.

1 0