[e-cvs] cvs commit: e/domains/cap/capsecure-org bib.dtd hub.xml index.html

markm@eros.cs.jhu.edu markm@eros.cs.jhu.edu
Fri, 19 Oct 2001 04:54:30 -0400


markm       01/10/19 04:54:30

  Modified:    domains/cap/capsecure-org index.html
  Added:       domains/cap/capsecure-org bib.dtd hub.xml
  Log:
  first draft of new home for link hub

Revision  Changes    Path
1.3       +219 -72   e/domains/cap/capsecure-org/index.html

Index: index.html
===================================================================
RCS file: /cvs/e/domains/cap/capsecure-org/index.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- index.html	2000/12/24 22:58:47	1.2
+++ index.html	2001/10/19 08:54:30	1.3
@@ -1,72 +1,219 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <!--last modified on Saturday, October 03, 1998 04:19 PM --> 
-<HTML>
-<!-- #BeginTemplate "/Templates/template.dwt" --> 
-<HEAD>
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html;CHARSET=iso-8859-1">
-<!-- #BeginEditable "doctitle" --> 
-<TITLE>Welcome to CapSecure.org</TITLE>
-<!-- #EndEditable --> 
-<meta name="Author" content="Mark S. Miller">
-<link rel=author rev=made href="mailto:markm@caplet.com" title="Mark S. Miller">
-<META NAME="description" CONTENT="E: Cryptographic Capabilities for Distributed Smart Contracting">
-<META NAME="keywords" CONTENT="Capability Security, Capabilities, Cryptography, Distributed Objects, Distributed
-  Language, Distributed Capabilities, Lambda Calculus, Scripting Language, Distributed Language, Persistent
-  Language, Persistent Capabilities, Persistent Objects, Java Shell, Capability Shell, Scripting Java, Smart
-  Contracting, Agoric E-Commerce, Open Source ">
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFCC" LINK="#0000FF" VLINK="#800080">
-<P> 
-<TABLE BORDER="0" width="100%">
-  <TR VALIGN="TOP"> 
-    <TD WIDTH="10%">&nbsp;</TD>
-    <TD> 
-      <P> 
-      <TABLE BORDER="0" WIDTH="100%">
-        <TR> 
-          <TD ALIGN="LEFT"><a href="index.html"><img src="images/lgmarb3.gif" width="26" height="26" align="absmiddle" border="0"></a></TD>
-          <TD ALIGN="RIGHT"> 
-            <P ALIGN="RIGHT"><FONT SIZE="7"><!-- #BeginEditable "BigTitle" --><FONT SIZE="7"><b><font size="5">Welcome 
-              to the future home of<br>
-              <font size="7">CapSecure.org</font></font></b></FONT><!-- #EndEditable --></FONT> 
-          </TD>
-        </TR>
-      </TABLE>
-      <hr>
-      <!-- #BeginEditable "LongBody" --> Watch this space. In the meantime, see 
-      <a href="http://www.erights.org/"><img src="images/e-lambda.gif" width="32" height="32" align="middle" border="0"></a>.<!-- #EndEditable --></TD>
-    <TD WIDTH="10%">&nbsp;</TD>
-  </TR>
-  <TR VALIGN="TOP"> 
-    <TD WIDTH="10%">&nbsp;</TD>
-    <TD> 
-      <hr>
-      <div align="center"> 
-        <p><a href="index.html"><img src="images/lgmarb3.gif" width="26" height="26" align="bottom" border="0"></a> 
-          <i><b><font size="5">H</font>ome</b></i></p>
-        <table width="100%" border="0" cellspacing="0" cellpadding="4">
-          <tr> 
-            <td> 
-              <div align="left"><!-- #BeginEditable "for-for-sale" -->
-              <a href="http://www.caplet.com/domains.html">
-              <img
-              src="http://www.caplet.com/images/for-sale-small.gif"
-              width="129" height="62" border="0" align="right">
-              </a>
-              <!-- #EndEditable --><i><a href="mailto:webmaster@capsecure.org">webmaster@capsecure.org</a></i><br>
-                or <a href="http://www.blindpay.com/crit-me-now.cgi"><img src="images/cmn.gif" width="98" height="21" border="0"></a> 
-              </div>
-            </td>
-            <td> 
-              <div align="right"><a href="http://www.privacy.org/ipc/"><img src="images/key.gif" width="37" height="19" alt="Golden Key" border="0"></a>&nbsp;<a href="http://mirrors.yahoo.com/eff/blueribbon.html"><img src="images/ribbon.gif" width="18" height="30"
-alt="Blue Ribbon" border="0"></a></div>
-            </td>
-          </tr>
-        </table>
-      </div>
-    </TD>
-    <td width="10%" valign="bottom">&nbsp;</td>
-  </TR>
-</TABLE>
-</BODY>
-<!-- #EndTemplate -->
-</HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<html>
+  <head>
+    <meta name="generator" content="HTML Tidy, see www.w3.org">
+    <title>Capability Systems References</title>
+  </head>
+
+  <body bgcolor="#ffffff">
+    <h1>Random references to capability information</h1>
+
+    <h2>Introductory Texts</h2>
+
+    <ul>
+      
+  <li><a href="http://www.zilium.de/joerg/17C3-CapOs/">17C3-CapOs</a><br>
+      Slides for my "capability based systems" workshop at the <a
+      href=
+      "http://www.ccc.de/congress/">ChaosCommunicationCongress2000</a></li>
+
+      <li><a href=
+      "http://www.eros-os.org/essays/00Essays.html">http://www.eros-os.org/essays/00Essays.html</a><br>
+
+      Some introductory essays -- easy reading...</li>
+
+      <li><a href=
+      "http://www.crit.org/~ping/alert/meaning.html">http://www.crit.org/~ping/alert/meaning.html</a><br>
+
+      The Meaning of Capability-Based Security</li>
+
+      <li><a href=
+      "http://www.skyhunter.com/marcs/capabilityIntro/">http://www.skyhunter.com/marcs/capabilityIntro/</a><br>
+
+      Marcs introduction to capability based security</li>
+
+      <li><a href=
+      "http://cap-lore.com/CapTheory/">http://cap-lore.com/CapTheory/</a><br>
+
+      Normans thought snippets: a lot of interesting stuff
+      here...</li>
+
+      <li><a href=
+      "http://www.cs.berkeley.edu/~pingster/sec/project/">http://www.cs.berkeley.edu/~pingster/sec/project/</a><br>
+
+       Interaction Design for End-User Security: PRE-PUBLICATION
+      DRAFT: A paper describing some ideas about man machine
+      interaction with respect to capability based systems.</li>
+    </ul>
+
+    <h2>Specific OS implementations</h2>
+
+    <ul>
+      <li>
+        <a href=
+        "http://www.eros-os.org/">http://www.eros-os.org/</a><br>
+         Promising project: A pure capability OS implementation for
+        x86; developed unter GPL. 
+
+        <ul>
+          <li><a href=
+          "http://www.eros-os.org/mailman/listinfo/">http://www.eros-os.org/mailman/listinfo/</a><br>
+
+          Mailinglist -- reading some discussions can be very
+          enlighting</li>
+
+          <li><a href=
+          "http://www.eros-os.org/papers/shap-thesis.ps">http://www.eros-os.org/papers/shap-thesis.ps</a><br>
+
+          Paper describing the EROS architecture and the
+          confinement mechanism.</li>
+
+          <li><a href=
+          "http://eros.cs.jhu.edu/gatherings/EWG2000/EWG2000.html">http://eros.cs.jhu.edu/gatherings/EWG2000/EWG2000.html</a><br>
+
+          EROS Working Group Meeting 2000</li>
+
+          <li><a href=
+          "http://www.capidl.org">http://www.capidl.org</a><br>
+          CapIDL will be Capability-oriented Interface Definition
+          Language, initially for describing EROS invocations.</li>
+        </ul>
+      </li>
+
+      <li><a href=
+      "http://www.agorics.com/KeyKos/">http://www.agorics.com/KeyKos/</a><br>
+
+      KeyKOS is a persistent, pure capability operating system. It
+      was first developed by Tymshare on IBM 370. Later KeyLogic
+      continued KeyKOS and ported it to -XXX-.</li>
+
+      <li><a href=
+      "http://www.cis.upenn.edu/~KeyKOS/Gnosis/Gnosis.html">http://www.cis.upenn.edu/~KeyKOS/Gnosis/Gnosis.html</a><br>
+
+       GNOSIS is a capability based OS whose construction began
+      about 1975 at Tymshare. Development continued for several
+      years at KeyLogic under the name "KeyKOS".</li>
+
+      <li><a href=
+      "http://www.informatik.uni-ulm.de/rs/projekte/SPEEDOS/">http://www.informatik.uni-ulm.de/rs/projekte/SPEEDOS/</a><br>
+
+      Persistent pure capability OS</li>
+
+      <li><a href=
+      "http://www.cse.unsw.edu.au/~disy/Mungi/">http://www.cse.unsw.edu.au/~disy/Mungi/</a><br>
+
+      Single-address-space, orthogonally persistent,
+      capability-based OS</li>
+    </ul>
+
+    <h2>Capability based programming languages / object
+    platforms</h2>
+
+    <ul>
+      <li>
+        <a href=
+        "http://www.erights.org/">http://www.erights.org/</a><br>
+        ELang provides a secure distributed object platform and p2p
+        scripting language for writing Capability-Based Smart
+        Contracts. 
+
+        <ul>
+          <li><a href=
+          "http://www.skyhunter.com/marcs/eDeskIndex.html">http://www.skyhunter.com/marcs/eDeskIndex.html</a><br>
+
+          Demo implementation of a desktop system on top of E.</li>
+        </ul>
+      </li>
+
+      <li><a href=
+      "http://www.mozart-oz.org/">http://www.mozart-oz.org/</a><br>
+      The Mozart Programming System is an advanced development
+      platform for intelligent, distributed applications. Mozart is
+      based on the Oz language.</li>
+
+      <li><a href=
+      "http://www.agorics.com/joule.html">http://www.agorics.com/joule.html</a><br>
+
+      Joule embodies a new computational model for building
+      distributed systems.</li>
+    </ul>
+
+    <h2>More abstract stuff</h2>
+
+    <ul>
+      <li><a href=
+      "http://citeseer.nj.nec.com/">http://citeseer.nj.nec.com/</a><br>
+
+       Provides a heap of interesting papers and makes them easy
+      accessable. You could start at <a href=
+      "http://citeseer.nj.nec.com/cs?q=capability&amp;cs=1">http://citeseer.nj.nec.com/cs?q=capability&amp;cs=1</a>
+      and spend the next two years reading...</li>
+    </ul>
+
+    <h2>POSIX 1003.1e and other UNIX hardening hacks (mostly
+    ugly)</h2>
+
+    <ul>
+      <li><a href=
+      "http://www.guug.de/~winni/posix.1e/">http://www.guug.de/~winni/posix.1e/</a><br>
+
+      POSIX 1003.1e "draft": Capabilities and MAC for UNIX</li>
+
+      <li><a href=
+      "http://www.trustedbsd.org">http://www.trustedbsd.org</a><br>
+      Project implementing POSIX.1e and MAC on FreeBSD</li>
+
+      <li><a href=
+      "http://www.bsdcon.com/proceedings/spencer_minear/">http://www.bsdcon.com/proceedings/spencer_minear/</a><br>
+
+      About Type Enforcement and POSIX.1e</li>
+
+      <li><a href=
+      "http://www.nsa.gov/selinux/">http://www.nsa.gov/selinux/</a><br>
+
+      Security-Enhanced Linux developed by the NSA. Offers MAC and
+      TypeEnforcement for Linux</li>
+
+      <li><a href=
+      "http://www.kernel.org/pub/linux/libs/security/linux-privs/">http://www.kernel.org/pub/linux/libs/security/linux-privs/</a><br>
+
+      Linux-Privs Project: POSIX 3.1e on linux. Another resource:
+      <a href=
+      "http://www.linuxsecurity.com/resource_files/server_security/linux-privs/linux-privs.html">
+      http://www.linuxsecurity.com/resource_files/server_security/linux-privs/linux-privs.html</a></li>
+
+      <li><a href=
+      "http://oss.sgi.com/projects/ob1/">http://oss.sgi.com/projects/ob1/</a><br>
+
+      SGI released documentation about their Trusted IRIX (TRIX).
+      <a href=
+      "http://techpubs.sgi.com/library/tpl/cgi-bin/browse.cgi?coll=0650&amp;db=bks&amp;cmd=toc&amp;pth=/SGI_Admin/TCMW_AG">
+      http://techpubs.sgi.com/library/tpl/cgi-bin/browse.cgi?coll=0650&amp;db=bks&amp;cmd=toc&amp;pth=/SGI_Admin/TCMW_AG</a>.
+      Don't forget to seach for some man pages about TRIX...</li>
+
+      <li><a href=
+      "http://www.hpl.hp.com/research/papers/trustedlinux.html">http://www.hpl.hp.com/research/papers/trustedlinux.html</a><br>
+
+       This paper describes a compartment based security
+      architecture for linux developed by HP. As far as i know this
+      is the solution HP offers as "HP-LX".</li>
+
+      <li><a href=
+      "http://www.sun.com/trusted-solaris">http://www.sun.com/trusted-solaris</a><br>
+
+      SUN Trusted Solaris</li>
+
+      <li><a href=
+      "http://www.sco.com/government/security/cmw_whtp.html">http://www.sco.com/government/security/cmw_whtp.html</a><br>
+
+      SCO CMW+ 3.0 -- SCO trusted Unix</li>
+    </ul>
+    <hr noshade>
+
+    <div align="right">
+      $Date: 2001/10/19 08:54:30 $; <a href=
+      "mailto:joerg@zilium.de">Joerg Bornschein</a>
+    </div>
+  </body>
+</html>
+



1.1                  e/domains/cap/capsecure-org/bib.dtd

Index: bib.dtd
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!--DTD generated by XML Spy v3.5 NT (http://www.xmlspy.com)-->
<!ELEMENT desc (#PCDATA | link | linklist)*>
<!ELEMENT entry (desc)>
<!ATTLIST entry
	ref CDATA #REQUIRED
	lang CDATA #IMPLIED
>
<!ELEMENT html (script)>
<!ELEMENT link (#PCDATA)>
<!ATTLIST link
	ref CDATA #REQUIRED
>
<!ELEMENT linklist (entry+)>
<!ELEMENT page (rcsdate, para, html)>
<!ATTLIST page
	title CDATA #REQUIRED
>
<!ELEMENT para (subpara+)>
<!ATTLIST para
	title CDATA #REQUIRED
>
<!ELEMENT rcsdate (#PCDATA)>
<!ELEMENT script EMPTY>
<!ATTLIST script
	type CDATA #REQUIRED
	language CDATA #REQUIRED
	src CDATA #REQUIRED
>
<!ELEMENT subpara (linklist)>
<!ATTLIST subpara
	title CDATA #REQUIRED
>



1.1                  e/domains/cap/capsecure-org/hub.xml

Index: hub.xml
===================================================================
<!DOCTYPE page SYSTEM "C:\Documents and Settings\Administrator\Desktop\bib.dtd">
<page title="Capability Systems References">
    <rcsdate>$Date: 2001/10/19 08:54:30 $</rcsdate>
    <para title="Random references to capability information">
        <subpara title="Introductory Texts">
            <linklist>
                <entry ref="http://www.zilium.de/joerg/17C3-CapOs/" lang="de">
                    <desc>Slides for my "capability based systems" workshop at the 
        <link ref="http://www.ccc.de/congress/">ChaosCommunicationCongress2000</link>
                    </desc>
                </entry>
                <entry ref="http://www.eros-os.org/essays/00Essays.html">
                    <desc>Some introductory essays -- easy reading...</desc>
                </entry>
                <entry ref="http://www.crit.org/~ping/alert/meaning.html">
                    <desc>The Meaning of Capability-Based Security</desc>
                </entry>
                <entry ref="http://www.skyhunter.com/marcs/capabilityIntro/">
                    <desc>Marcs introduction to capability based security</desc>
                </entry>
                <entry ref="http://cap-lore.com/CapTheory/">
                    <desc>Normans thought snippets: a lot of interesting stuff here...</desc>
                </entry>
                <entry ref="http://www.cs.berkeley.edu/~pingster/sec/project/">
                    <desc> Interaction Design for End-User Security: 
       PRE-PUBLICATION DRAFT: A paper describing some ideas about man machine 
       interaction with respect to capability based systems.
      </desc>
                </entry>
            </linklist>
        </subpara>
        <subpara title="Specific OS implementations">
            <linklist>
                <entry ref="http://www.eros-os.org/">
                    <desc>
       Promising project: A pure capability OS implementation for x86;
       developed unter GPL.
       <linklist>
                            <entry ref="http://www.eros-os.org/mailman/listinfo/">
                                <desc>Mailinglist -- reading some discussions can be very enlighting</desc>
                            </entry>
                            <entry ref="http://www.eros-os.org/papers/shap-thesis.ps">
                                <desc>Paper describing the EROS architecture and the confinement mechanism.</desc>
                            </entry>
                            <entry ref="http://eros.cs.jhu.edu/gatherings/EWG2000/EWG2000.html">
                                <desc>EROS Working Group Meeting 2000</desc>
                            </entry>
                            <entry ref="http://www.capidl.org">
                                <desc>CapIDL will be Capability-oriented Interface Definition Language, 
		initially for describing EROS invocations.</desc>
                            </entry>
                        </linklist>
                    </desc>
                </entry>
                <entry ref="http://www.agorics.com/KeyKos/">
                    <desc>KeyKOS is a persistent, pure capability operating system. It
	was first developed by Tymshare on IBM 370. Later KeyLogic
	continued KeyKOS and ported it to -XXX-.</desc>
                </entry>
                <entry ref="http://www.cis.upenn.edu/~KeyKOS/Gnosis/Gnosis.html">
                    <desc> GNOSIS is a capability based OS whose construction began
	about 1975 at Tymshare. Development continued for several
	years at KeyLogic under the name "KeyKOS".
      </desc>
                </entry>
                <entry ref="http://www.informatik.uni-ulm.de/rs/projekte/SPEEDOS/">
                    <desc>Persistent pure capability OS</desc>
                </entry>
                <entry ref="http://www.cse.unsw.edu.au/~disy/Mungi/">
                    <desc>Single-address-space, orthogonally persistent, capability-based OS</desc>
                </entry>
            </linklist>
        </subpara>
        <subpara title="Capability based programming languages / object platforms">
            <linklist>
                <entry ref="http://www.erights.org/">
                    <desc>ELang provides a secure distributed object platform and p2p
	scripting language for writing Capability-Based Smart
	Contracts.
      <linklist>
                            <entry ref="http://www.skyhunter.com/marcs/eDeskIndex.html">
                                <desc>Demo implementation of a desktop system on top of E.</desc>
                            </entry>
                        </linklist>
                    </desc>
                </entry>
                <entry ref="http://www.mozart-oz.org/">
                    <desc>The Mozart Programming System is an advanced development platform for
	intelligent, distributed applications. Mozart is based on the Oz language.
    </desc>
                </entry>
                <entry ref="http://www.agorics.com/joule.html">
                    <desc>Joule embodies a new computational model for building
	distributed systems.
    </desc>
                </entry>
            </linklist>
        </subpara>
        <subpara title="More abstract stuff">
            <linklist>
                <entry ref="http://citeseer.nj.nec.com/">
                    <desc> Provides a heap of interesting papers and makes them easy
	accessable. You could start at 
	<link ref="http://citeseer.nj.nec.com/cs?q=capability&amp;cs=1"/>
	and spend the next two years reading...
    </desc>
                </entry>
            </linklist>
        </subpara>
        <subpara title="POSIX 1003.1e and other UNIX hardening hacks (mostly ugly)">
            <linklist>
                <entry ref="http://www.guug.de/~winni/posix.1e/">
                    <desc>POSIX 1003.1e "draft": Capabilities and MAC for UNIX</desc>
                </entry>
                <entry ref="http://www.trustedbsd.org">
                    <desc>Project implementing POSIX.1e and MAC on FreeBSD</desc>
                </entry>
                <entry ref="http://www.bsdcon.com/proceedings/spencer_minear/">
                    <desc>About Type Enforcement and POSIX.1e</desc>
                </entry>
                <entry ref="http://www.nsa.gov/selinux/">
                    <desc>Security-Enhanced Linux developed by the NSA. Offers MAC and TypeEnforcement 
	for Linux</desc>
                </entry>
                <entry ref="http://www.kernel.org/pub/linux/libs/security/linux-privs/">
                    <desc>Linux-Privs Project: POSIX 3.1e on linux. Another resource: 
	<link ref="http://www.linuxsecurity.com/resource_files/server_security/linux-privs/linux-privs.html"/>
                    </desc>
                </entry>
                <entry ref="http://oss.sgi.com/projects/ob1/">
                    <desc>SGI released documentation about their Trusted IRIX (TRIX).
	<link ref="http://techpubs.sgi.com/library/tpl/cgi-bin/browse.cgi?coll=0650&amp;db=bks&amp;cmd=toc&amp;pth=/SGI_Admin/TCMW_AG"/>. Don't forget to seach for some man pages about TRIX...
    </desc>
                </entry>
                <entry ref="http://www.hpl.hp.com/research/papers/trustedlinux.html">
                    <desc>
       This paper describes a compartment based security architecture for linux
       developed by HP.
       As far as i know this is the solution HP offers as &quot;HP-LX&quot;.
       
    </desc>
                </entry>
                <entry ref="http://www.sun.com/trusted-solaris">
                    <desc>SUN Trusted Solaris</desc>
                </entry>
                <entry ref="http://www.sco.com/government/security/cmw_whtp.html">
                    <desc>SCO CMW+ 3.0 -- SCO trusted Unix</desc>
                </entry>
            </linklist>
        </subpara>
    </para>