2) If you throw TCP processing in there, unless you are consistantly going to
have packets on the order of at least 1000 bytes, your crypto algorithm is
almost _irrelevant_.
This is my experience, too. And I would add and lots of packets.
The only crypto overhead that really mattered in a
[I realise this isn't crypto, but it's arguably security-relevant and arguably
interesting :-)].
James Hughes hugh...@mac.com writes:
TOEs that are implemented in a slow processor in a NIC card have been shown
many times to be ineffective compared to keeping TCP in the fastest CPU
(where it is
On Jul 24, 2009, at 1:30 PM, Peter Gutmann wrote:
[I realise this isn't crypto, but it's arguably security-relevant
and arguably
interesting :-)].
As long as we think this is interesting, (although I respectfully
disagree that there are any inherent security problems with TOE. Maybe
From http://www.wired.com/gadgetlab/2009/07/iphone-encryption/:
the supposedly enterprise-friendly encryption included with the iPhone 3GS
is so weak it can be cracked in two minutes with a few pieces of
readily available
freeware...“I don’t think any of us [developers] have ever seen
[cross-posted to tahoe-...@allmydata.org and cryptogra...@metzdowd.com]
Disclosure: Cleversafe is to some degree a competitor of my Tahoe-
LAFS project. On the other hand, I tend to feel positive towards
them because they open-source much of their work. Our Related
Projects page has
