🚀 go-pugleaf

In article <1991May21.210447.9022@ux1.cso.uiuc.edu> phil@ux1.cso.uiuc.edu (Phil Howard KA9WGN) writes:

   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.

Let me quote from rfc1114...

   Current plans call for RSADSI to act in concert with subscriber
   organizations as a "certifying authority" in a fashion described
   later in this RFC.  RSADSI will offer a service in which it will sign
   a certificate which has been generated by a user and vouched for
   either by an organization or by a Notary Public.  This service will
   carry a $25 biennial fee which includes an associated license to use
   the RSA algorithm in conjunction with privacy protection of
   electronic mail.  Users who do not come under the purview of the RSA

So, yes, YOU generate your secret key, use the public part to generate
a certificate, and let RSADSI sign it.  Whether or not the license
will allow you to use unregistered keys also is not clear to me (I
would guess yes), though I am not sure why you would want to.

- Harald Hanche-Olsen <hanche@imf.unit.no>
  Division of Mathematical Sciences
  The Norwegian Institute of Technology
  N-7034 Trondheim, NORWAY