Re: [Sip] Review of draft-kupwade-sip-iba-00

Dean Willis <dean.willis@softarmor.com> Thu, 28 February 2008 18:33 UTC

Return-Path: <sip-bounces@ietf.org>
X-Original-To: ietfarch-sip-archive@core3.amsl.com
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BFCB3A6EE8; Thu, 28 Feb 2008 10:33:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.973
X-Spam-Level:
X-Spam-Status: No, score=-0.973 tagged_above=-999 required=5 tests=[AWL=-0.536, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uIPk-aHtTFaG; Thu, 28 Feb 2008 10:33:47 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC5DA28C0E1; Thu, 28 Feb 2008 10:33:46 -0800 (PST)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A66BD28C2CB for <sip@core3.amsl.com>; Thu, 28 Feb 2008 10:33:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O+qxwZoLygkk for <sip@core3.amsl.com>; Thu, 28 Feb 2008 10:33:44 -0800 (PST)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id CB26C3A6E69 for <sip@ietf.org>; Thu, 28 Feb 2008 10:33:38 -0800 (PST)
Received: from [206.176.144.210] (206-176-144-210.waymark.net [206.176.144.210]) (authenticated bits=0) by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id m1SIXQ5A016108 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 28 Feb 2008 12:33:28 -0600
Message-ID: <47C6FE6D.1040504@softarmor.com>
Date: Thu, 28 Feb 2008 12:33:17 -0600
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Icedove 1.5.0.14pre (X11/20080208)
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
References: <20080227003651.265505081A@romeo.rtfm.com> <E6C2E8958BA59A4FB960963D475F7AC30BC778D633@mail.acmepacket.com>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC30BC778D633@mail.acmepacket.com>
X-Enigmail-Version: 0.94.2.0
Cc: "sip@ietf.org" <sip@ietf.org>, "draft-kupwade-sip-iba@tools.ietf.org" <draft-kupwade-sip-iba@tools.ietf.org>
Subject: Re: [Sip] Review of draft-kupwade-sip-iba-00
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hadriel Kaplan wrote:
> Cool. So if I understand this right (and I probably don't), ignoring
> rfc4474 identity and IBS for a moment and instead thinking about SRTP
> and IBE: I could use IBE to encrypt the security-descriptions
> attribute value using the intended target's SIP URI as a key, and
> only someone owning that URI (and sharing the same KG) or the KG
> itself could decrypt it to learn the sec-desc cleartext to use?

Actually, there are partial-key models where the KG couldn't decrypt it
either.

There are modes of operation that allow the full private key to be a
product of a secret (retained by the user) and the output of the PKG.
Hence you need to know both parts to decrypt or sign a message.

> -hadriel p.s. the KG would actually be a problem for IBE, wouldn't
> it?  I mean the KG can always decrypt it. (at which point they would
> be the Key Generator Backdoor - aka, the KGB ;)

Yep. Early IB systems worked as you describe. But they don't HAVE to
work that way.

--
Dean


_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip