Re: [TLS] Please discuss: draft-housley-evidence-extns-00 - brokerage illustration

Martin Rex <martin.rex@sap.com> Fri, 12 January 2007 20:26 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H5SyZ-0006UT-12; Fri, 12 Jan 2007 15:26:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H5SyX-0006RV-Io for tls@ietf.org; Fri, 12 Jan 2007 15:26:09 -0500
Received: from smtpde02.sap-ag.de ([155.56.68.170]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H5SyV-0000ed-61 for tls@ietf.org; Fri, 12 Jan 2007 15:26:09 -0500
Received: from sap-ag.de (smtpde02) by smtpde02.sap-ag.de (out) with ESMTP id VAA01737; Fri, 12 Jan 2007 21:25:58 +0100 (MEZ)
From: Martin Rex <martin.rex@sap.com>
Message-Id: <200701122025.VAA23310@uw1048.wdf.sap.corp>
Subject: Re: [TLS] Please discuss: draft-housley-evidence-extns-00 - brokerage illustration
To: mark@redphonesecurity.com
Date: Fri, 12 Jan 2007 21:25:57 +0100
In-Reply-To: <003a01c73678$b9ee0df0$6801a8c0@rps.local> from "Mark Brown" at Jan 12, 7 12:37:34 pm
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-SAP: out
X-SAP: out
X-SAP: out
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: tls@ietf.org
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: martin.rex@sap.com
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Errors-To: tls-bounces@lists.ietf.org

Mark,

Mark Brown wrote:
> 
> Below is an illustration of how to use TLS Evidence for a brokerage
> transaction.

I appreciate your efforts, but I'm running out of time with this
debate.  I'm behind on my development schedule and need to go back
do the work I'm being paid for.


There will always be means to use a inappropriate technology
for an inadequate solution, I can see it every day when deployed technology
is frobbed^Wretrofitted for a purpose for which it wasn't designed.
However, it is a pretty bad idea to start off with a technology
that fits common scenarios in home/office/businesses so poorly
as TLS Evidence and has such a huge abusive potential.


I know that there is a huge economic motivation for government agencies
to be able to purchase equiment on the free market that suits their
needs rather than having to develop it on their own.  This is one of
the reasons how/why TPM sneaked into modern business computers for
the mass market.

There is some truth in what Peter says, the proposal is so well designed,
and many of the things people recognize as problems are there on a
purpose and integral part of the proposal, so the most severe problems
are beyond repair.  IMHO, if TLS Evidence is rubberstamped, it means that
the IETF has been subverted sucessfully.


If this technology enters the maintstream, then the agencies will
start harvesting the results.  They've been pretty firm in how
much they like and intend to expand surveillance, and they are
regularly breaking the laws in order to collect information
to which they're not entitled.

The most effective security measure is not protecting data with
strong crypto and high assurance, it is not creating -- or where
it needs to be created and processed -- not persisting it.


As far as risk management is concerned, TLS Evidence is probably
the largest can of worms I've ever seen.  Since I've started thinking
about this technology, I discover at least one major new problem every day
(acutally every night when I try to get asleep), and I have the feeling
that I've only seen the tip of the iceberg so far.


-Martin 

_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls