Re: [Sip] pgp authentication

Dean Willis <dean.willis@softarmor.com> Wed, 27 July 2005 19:50 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxrvD-0003WK-HR; Wed, 27 Jul 2005 15:50:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxrvB-0003WC-7s for sip@megatron.ietf.org; Wed, 27 Jul 2005 15:50:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27874 for <sip@ietf.org>; Wed, 27 Jul 2005 15:50:26 -0400 (EDT)
Received: from nylon.softarmor.com ([66.135.38.164]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DxsQU-00012v-0T for sip@ietf.org; Wed, 27 Jul 2005 16:22:51 -0400
Received: from [64.101.149.214] (dhcp-64-101-149-214.cisco.com [64.101.149.214]) (authenticated bits=0) by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id j6RJsJXs001313 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Wed, 27 Jul 2005 14:54:21 -0500
In-Reply-To: <42E707BC.6070600@brondsema.net>
References: <42E13D86.30309@brondsema.net> <42E707BC.6070600@brondsema.net>
Mime-Version: 1.0 (Apple Message framework v622)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <5ac54e7042c1a8737df61654588ae8f7@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] pgp authentication
Date: Wed, 27 Jul 2005 14:50:33 -0500
To: Dave Brondsema <dave@brondsema.net>
X-Pgp-Agent: GPGMail 1.1 (Panther)
X-Gpgmail-State: signed
X-Mailer: Apple Mail (2.622)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit
Cc: sip@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


The short answer is that we removed it because it was unimplemented, 
incompletely specified, appeared to have no current constituency, and 
we didn't have time to deal with it in SIP.

There's a writeup on using PEM and PGP with Apache for authentication 
and encryption at:

http://hoohoo.ncsa.uiuc.edu/docs/PEMPGP.html

that might have pointers that would help.


I don't believe we actually have "a recommended way" to do 
www-authenticate for SIP using PGP.


- --
Dean

On Jul 26, 2005, at 11:04 PM, Dave Brondsema wrote:

> Is there a better place to ask this?
>
> Dave Brondsema wrote:
>>
>> Why was pgp authentication removed in rfc3261?  A note mentions "PGP
>> MIME" is more complete, but I can't find any other RFC with a
>> WWW-Authentication scheme for PGP.  What is the recommended way to
>> implement WWW-Authentication using PGP?
>>
>> Thanks!
>>
>
> --
> Dave Brondsema : dave@brondsema.net
> http://www.splike.com : programming
> http://www.brondsema.net : personal
>                <><
> _______________________________________________
> Sip mailing list  https://www1.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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFC5+WNSE0vSqCaet8RAhyfAJ9ukryYIgV2HBr1Q8zQ9MdxNQDMfgCgkhMh
93VFjZ/NZ/rBsYluz45VHpM=
=Pq/D
-----END PGP SIGNATURE-----


_______________________________________________
Sip mailing list  https://www1.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