Re: [TLS] HTTPS client-certificate-authentication in browsers

Anders Rundgren <anders.rundgren@telia.com> Mon, 25 July 2011 16:11 UTC

Return-Path: <anders.rundgren@telia.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B038111E8115 for <tls@ietfa.amsl.com>; Mon, 25 Jul 2011 09:11:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.577
X-Spam-Level:
X-Spam-Status: No, score=-3.577 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vwVQW0M6pU4H for <tls@ietfa.amsl.com>; Mon, 25 Jul 2011 09:11:53 -0700 (PDT)
Received: from smtp-out11.han.skanova.net (smtp-out11.han.skanova.net [195.67.226.200]) by ietfa.amsl.com (Postfix) with ESMTP id 7939421F8C8F for <tls@ietf.org>; Mon, 25 Jul 2011 07:43:27 -0700 (PDT)
Received: from [192.168.0.202] (81.232.44.37) by smtp-out11.han.skanova.net (8.5.133) (authenticated as u36408181) id 4D6512CA034B776B; Mon, 25 Jul 2011 16:43:26 +0200
Message-ID: <4E2D8104.3080309@telia.com>
Date: Mon, 25 Jul 2011 16:43:16 +0200
From: Anders Rundgren <anders.rundgren@telia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Henry Story <henry.story@bblfish.net>
References: <4E2D5C63.3000408@telia.com> <FCFA8791-E16A-45F4-B23D-B6A4A4F88AF9@bblfish.net> <4E2D688E.5030509@telia.com> <E2962F5B-AD7C-4AF7-9548-9686CE14FF38@bblfish.net> <4E2D71DB.6020604@telia.com> <C660273C-BDF3-4543-B1FC-82B3B6F39F0C@bblfish.net>
In-Reply-To: <C660273C-BDF3-4543-B1FC-82B3B6F39F0C@bblfish.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: tls@ietf.org
Subject: Re: [TLS] HTTPS client-certificate-authentication in browsers
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 16:11:54 -0000

On 2011-07-25 16:18, Henry Story wrote:
<snip>
>>>> TLS' session context is incompatible with web sessions.
>>
>>> Why?  A TLS Session can work very well with web sessions. You can 
>>> just make your TLS session be a web session.
>>
>> AFAIK HttpSession.invalidate in Tomcat/JBoss has no effect whatsoever
>> on a TLS session.
> 
> They are two different things. I think you  cannot logout the client from
> the server, though recently you pointed to some javascript that could allow that.

I did but I also used a scheme where I had a login site on one port
and the rest on another port.  I found this working more by accident.

It may be security-broken and browser-incompatible etc.

> This may be something the server vendors need to work on. The question first has
> to be asked: is this a necessary limitation, or is it just not implemented well?

This may be above my knowledge but I think it is impossible to do this on
the server only.  Why?  Otherwise it had already been done.

<snip>
Anders