head	1.2;
access;
symbols
	RELEASE_8_3_0:1.2
	RELEASE_9_0_0:1.2
	RELEASE_7_4_0:1.2
	RELEASE_8_2_0:1.2
	RELEASE_6_EOL:1.2
	RELEASE_8_1_0:1.2
	RELEASE_7_3_0:1.2
	RELEASE_8_0_0:1.2
	RELEASE_7_2_0:1.2
	RELEASE_7_1_0:1.2
	RELEASE_6_4_0:1.2
	RELEASE_5_EOL:1.2
	RELEASE_7_0_0:1.2
	RELEASE_6_3_0:1.2
	PRE_XORG_7:1.2
	RELEASE_4_EOL:1.2
	RELEASE_6_2_0:1.1.1.1
	RELEASE_6_1_0:1.1.1.1
	RELEASE_5_5_0:1.1.1.1
	RELEASE_6_0_0:1.1.1.1
	RELEASE_5_4_0:1.1.1.1
	RELEASE_4_11_0:1.1.1.1
	RELEASE_5_3_0:1.1.1.1
	RELEASE_4_10_0:1.1.1.1
	RELEASE_5_2_1:1.1.1.1
	RELEASE_5_2_0:1.1.1.1
	RELEASE_4_9_0:1.1.1.1
	RELEASE_5_1_0:1.1.1.1
	RELEASE_4_8_0:1.1.1.1
	RELEASE_5_0_0:1.1.1.1
	RELEASE_4_7_0:1.1.1.1
	RELEASE_4_6_2:1.1.1.1
	RELEASE_4_6_1:1.1.1.1
	RELEASE_4_6_0:1.1.1.1
	RELEASE_5_0_DP1:1.1.1.1
	RELEASE_4_5_0:1.1.1.1
	RELEASE_4_4_0:1.1.1.1
	RELEASE_4_3_0:1.1.1.1
	RELEASE_4_2_0:1.1.1.1
	RELEASE_4_1_1:1.1.1.1
	RELEASE_4_1_0:1.1.1.1
	RELEASE_3_5_0:1.1.1.1
	RELEASE_4_0_0:1.1.1.1
	RELEASE_3_4_0:1.1.1.1
	draft:1.1.1.1
	SE:1.1.1;
locks; strict;
comment	@# @;


1.2
date	2006.11.05.07.58.38;	author lawrance;	state Exp;
branches;
next	1.1;

1.1
date	99.09.18.09.05.28;	author se;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	99.09.18.09.05.28;	author se;	state Exp;
branches;
next	;


desc
@@


1.2
log
@Update master site and WWW.

PR:		ports/104256
Submitted by:	Josh Paetzel <josh@@tcbug.org>
@
text
@KeyNote is a simple and flexible trust-management system designed to
work well for a variety of large- and small- scale Internet-based
applications.  It provides a single, unified language for both local
policies and credentials.  KeyNote policies and credentials, called
`assertions,' contain predicates that describe the trusted actions
permitted by the holders of specific public keys.  KeyNote assertions
are essentially small, highly-structured programs.  A signed
assertion, which can be sent over an untrusted network, is also
called a `credential assertion.'  Credential assertions, which also
serve the role of certificates, have the same syntax as policy
assertions but are also signed by the principal delegating the trust.

This is an example implementation of the KeyNote Trust-Management System
as specified in IETF draft <draft-blaze-ietf-trustmgt-keynote-02.txt>.

WWW: http://www1.cs.columbia.edu/~angelos/keynote.html
@


1.1
log
@Initial revision
@
text
@d16 1
a16 1
WWW: http://www.cis.upenn.edu/~angelos/keynote.html
@


1.1.1.1
log
@New port of the keynote trust-management system (currently an IETF draft).
@
text
@@
