<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.18.2">
</HEAD>
<BODY>
<BR>
<BR>
On Mon, 2008-08-11 at 13:33 -0600, Peter Braam wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
>> <BR>
>> You do need to sign it and encrypt it - for multiple purposes, to secure the<BR>
>> wire transaction and for storage on the server.<BR>
> <BR>
> Sorry I'm still a little confused. To be exactly clear, do you mean: In<BR>
> the future we'll use NASD-style protocol to secure the bulk data's wire<BR>
> transfer & storage on server; and for now we can simply leave the bulk<BR>
> data unprotected?<BR>
<BR>
No you need to be able to encrypt it.<BR>
<BR>
I'm just stating that if you the current solution (which gives privacy using<BR>
GSS between client and OSS iirc) is going to be changed, then please change<BR>
it in the correct way to accommodate re-using checksums and re-using the<BR>
encrypted data for storage. Doing either of these things twice is<BR>
pointless.<BR>
</BLOCKQUOTE>
The NASD protocols do not allow for the encryption of the communications and the stored information to be the same. The key management for communications is well understood, but the key management for the stored information as defined by NASD requires the encryption of the stored information to be performed at the target. <BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
Probably there should be options not to do so as part of the configuration.<BR>
<BR>
Peter<BR>
<BR>
<BR>
</BLOCKQUOTE>
</BODY>
</HTML>