🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: sci.crypt
Article #6744

Re: rpem: current status

#6744
From: Phil Howard KA9WGN
Date: Tue, 21 May 1991 21:04
43 lines
3128 bytes
smb@ulysses.att.com (Steven Bellovin) writes:

>The code is real; I have seen a copy of it.  I've been told that the
>production version really will be distributed, and quite soon.  My
>information is from the authors themselves.  You're welcome to call
>this a rumor if you wish -- and certainly, the software had been
>promised long ago; another delay would not be a surprise.

Suppose this software comes bundled into a system that happens to be
unusable in certain circumstances, it "unfriendly" to a certain class
of users, or in some other way comes wrapped in an unsuitable implementation.

What my concern will be is that we won't be granted the freedom to "fix"
the implementation.

I rarely see, in both free or commercial software, implementations that
are truly suitable for all cases.  Free software usually comes with source
(fixed platforms like Mac and PC clones tend to have lots of non-source)
and thus individuals can fix things, or add improvements (but I call that
"fixing" anyway) themselves.  But what about distributing the fixes?

>As far as I know -- and I know much less about this than I do about
>the patent process -- the agreement with Public Key Partners about
>the use of RSA for PEM does not require that one use any particular
>software.  It would seem, then, that use of your software on the
>Internet would be permissible *if* users paid their license fees
>to obtain the certificates.  I would not be suprised if the agreement
>extended only to RFC-compliant implementations, but that isn't a
>major stumbling block, as far as I can see.

I guess we will have to wait and see what PKP is really wanting to do
about this.

However, if the end user licensing process involves them assigning the
actual keys, I certainly won't go for it, free or commercial.  If it
constitutes simply a registry of public keys (you give them your public
key) then that seems reasonable as long as there are no restrictions on
using other unregistered keys.
-- 
 /***************************************************************************\
/ Phil Howard -- KA9WGN -- phil@ux1.cso.uiuc.edu   |  Guns don't aim guns at  \
\ Lietuva laisva -- Brivu Latviju -- Eesti vabaks  |  people; CRIMINALS do!!  /
 \***************************************************************************/
Technical Details
Message-ID: <1991May21.210447.9022@ux1.cso.uiuc.edu>
Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!wuarchive!uwm.edu!ux1.cso.uiuc.edu!phil
References: <1991May20.145058.10669@msuinfo.cl.msu.edu> <14846@ulysses.att.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1025b4,8052260a1eaa980b
X-Google-Attributes: gid1025b4,public
X-Google-Thread: 1038e3,8052260a1eaa980b
X-Google-Attributes: gid1038e3,public
X-Google-Thread: fb57f,8052260a1eaa980b
X-Google-Attributes: gidfb57f,public
X-Google-ArrivalTime: 1991-05-22 02:16:50 PST
Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!wuarchive!uwm.edu!ux1.cso.uiuc.edu!phil
From: phil@ux1.cso.uiuc.edu (Phil Howard KA9WGN)
Newsgroups: sci.crypt,gnu.misc.discuss,misc.legal
Subject: Re: rpem: current status
Keywords: rpem RSA patent
Message-ID: <1991May21.210447.9022@ux1.cso.uiuc.edu>
Date: 21 May 91 21:04:47 GMT
References: <1991May20.145058.10669@msuinfo.cl.msu.edu> <14846@ulysses.att.com>
Organization: University of Illinois at Urbana
Lines: 43