On Wed, Jun 18, 2014 at 5:18 PM, D. J. Bernstein d...@cr.yp.to wrote:
...
would be unable to shortcut the loop if the
arguments were merely declared as pointers to volatile storage
The compiler would be required to access the storage but would still be
allowed to skip the intermediate
On Mon, Jun 9, 2014 at 7:35 PM, ianG i...@iang.org wrote:
Original Message
Subject: [Tcpcrypt] WG Review: TCP Increased Security (tcpinc)
Date: Thu, 05 Jun 2014 14:31:12 -0700
From: The IESG iesg-secret...@ietf.org
To: IETF-Announce ietf-annou...@ietf.org
CC: tcpinc WG
On Thu, Jun 19, 2014 at 4:18 PM, Dan McDonald dan...@kebe.com wrote:
ZFS crypto, closed-source thanks to Oracle, was supposed to address this
problem. Its design was to apply crypto in the ZIO path, like it does for
checksums. I've not used Oracle Solaris, but apparently ZFS crypto is in
On Thu, Jun 19, 2014 at 6:05 PM, Dan McDonald dan...@kebe.com wrote:
In the OpenZFS world, you deploy each OS's FDE underneath ZFS.
For now, yes. That's what you're stuck with.
That's actually not a problem.
That blog is 3.5 years old. I think things have likely improved since then.
Only
With common algorithms, how much would a LOT of storage help? I know this
one organization that seems to be building an omnious observation storage
facility, even though omnious observation has very mixed effectiveness
(read: not really worth it), and I'm wondering; is the NSA planning on
using it
