[124] in Open-Software-Foundation-News
OSF RFC 68.1
daemon@ATHENA.MIT.EDU (Walt Tuvell)
Fri Feb 17 17:29:02 1995
Resent-From: Bill Cattey <wdc@MIT.EDU>
Resent-To: osf-news-mtg@menelaus.LOCAL
From: Walt Tuvell <walt@osf.org>
Date: Fri, 17 Feb 95 13:02:45 -0500
To: sig-dce@osf.org, sig-security@osf.org, sig-dce-security@osf.org
*** OSF-RFC ANNOUNCEMENT ***
The following OSF-RFC has just been published:
=====================================================================
68.1 A. Anderson, J. Wray, "Public-Key Login for DCE 1.2 --
Functional Specification", February 1995.
Bytes: roff=123167, txt=126832, ps=438248; pages: txt=56,
ps=38.
Obsoletes: 68.0.
This document specifies the functionality required to integrate
public-key mechanisms into DCE login and DCE Registry operations,
including the associated protocols, API's, and user interfaces. This
specification obsoletes OSF RFC 68.0. The changes that have been
made since RFC 68.0 are massive, and it would be impractical to list
them all here. The present revision should be considered the first
(nearly) complete release of this document.
The goal of this effort is to allow users to choose to use public-key
cryptography instead of symmetric-key cryptography to prove their
identity to the system. The immediate benefit of such a change is
that, in the event of a KDC compromise public-key users will suffer
less exposure than normal users. For public-key users who do not
have smart-cards for secure storage of their private-keys, the
registry will also provide a storage service.
=====================================================================
/* Instructions for FTP access: "ftp grabbag.osf.org" (130.105.100.2),
user="dce-rfc", password="dce-rfc", "cd dce-rfc", usual ftp commands.
Instructions for Internet email access: "mail dce-rfc-archive@osf.org",
subject line null, body has two lines that look like this:
path <your-return-email-address>
send rfc <rfc-name>
where <rfc-name> has one of two forms:
rfc<M>.<m>.[roff|txt|ps]
rfc-index.[roff|txt|ps] <-- See this for list of all RFC's.
For full information about these and all other aspects of OSF-RFC's, see
the Introductory RFC 0.0 (rfc0.0.txt, which is considered REQUIRED
READING for all users of this series). Authors of OSF-RFC's must also
consult the Template and Style Guide RFC 0.1 (rfc0.1.roff).
HISTORICAL NOTE: OSF-RFC numbers < 62 are also known as "DCE-RFC's". */
- Walt Tuvell (OSF), OSF-RFC Editor, walt@osf.org, +1-617-621-8764
