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

Martin Rex <martin.rex@sap.com> Wed, 03 January 2007 22:55 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H2F1A-0005gd-Jz; Wed, 03 Jan 2007 17:55:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H2F19-0005gX-87 for tls@ietf.org; Wed, 03 Jan 2007 17:55:31 -0500
Received: from smtpde01.sap-ag.de ([155.56.68.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2F17-0006Mc-ST for tls@ietf.org; Wed, 03 Jan 2007 17:55:31 -0500
Received: from sap-ag.de (smtpde01) by smtpde01.sap-ag.de (out) with ESMTP id XAA23475; Wed, 3 Jan 2007 23:55:18 +0100 (MEZ)
From: Martin Rex <martin.rex@sap.com>
Message-Id: <200701032255.XAA15968@uw1048.wdf.sap.corp>
Subject: Re: [TLS] Please discuss: draft-housley-evidence-extns-00
To: mark@redphonesecurity.com
Date: Wed, 03 Jan 2007 23:55:18 +0100
In-Reply-To: <002401c72f6f$5269f6e0$6801a8c0@rps.local> from "Mark Brown" at Jan 3, 7 01:42:37 pm
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-SAP: out
X-SAP: out
X-Spam-Score: 1.1 (+)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
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 Brown wrote:
> 
> Here's an example to motivate why someone might want an un-forgeable record.
> Say you're buying tickets to a popular concert/movie/etc. online (i.e.,
> limited inventory situation).  In this case you (buyer) might care even more
> about getting a ticket than its price.  So when you show up at the venue you
> want your electronic tickets / records of sale sustain a fair verification
> effort that they are not forgeries.  You do not want the venue manager to
> say, "Sorry, we don't have records of this transaction..."


Sorry, but this is complete bullshit.

Browsers traditionally use up to 4 independent connections to retrieve
parts of what composes a Web page as seen by the user, and that results
in several parallel independent TLS-protected communcation channels.

Similar things happens in the middleware of other applications.

The majority of online-shops uses a crazy amount of http gimicks to
beef up their web-pages, including CSS and javascript, and you don't
seem to have looked at the raw source code of any of that stuff lately,
or you would know that this stuff is close to incomprehensible at
the network level.  Implementing some visualization software to
make sense from the captures&signed fraction of a raw datastream
will require magnitudes more code&time than implementing digital
signatures in a clean an understandable way at the application level
and the signed data can be made comprehensible for mere mortals
in raw form or compatible and verifyable with standardized software
(i.e. PKCS#7 / CMS).


-Martin

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