$Id: README,v 1.8 2000/06/30 22:59:02 molter Exp $ README FOR ANETD ================ o INSTALLATION: see the file INSTALL o USER GUIDE: see the file anetd-user-guide.ps.gz o CHANGES AND KNOWN BUGS: see the file RELEASE_NOTES o USE UNDER THE ABONE: see http://www.isi.edu/abone/ o see http://www.csl.sri.com/activate/ for more informations on the ACTIVATE project and on Anetd WHAT IS ANETD ------------- Anetd is a generic "service deployer", that can be used used to manage both legacy networking software and more experimental software derived from active networking research. It can run stand-alone or as an ABONE node, in either cases without special privileges. For active networks, Anetd has both a system management function and a Unix-based node OS function. Its system management function allows an EE developer to securely install and test an EE on a remote node, without having a login account on that node. Anetd forks EEs as Unix sub-processes. There may be multiple Anetd processes executing under different Unix accounts, to isolate their EEs. Anetd's node OS function is to listen on the well-known ANEP UDP port(s), demultiplex incoming active packets on ANEP Type Id, and pass the packets to the appropriate EE. Anetd supports two kinds of EEs (other language environments can be supported in the future): 1. Java classes, run under a JVM 2. native executable code (normally written in C), run directly under the host operating system CRYPTO ------ Anetd uses RSAREF. Please read RSA_LICENSE before using Anetd. SOURCE AVAILABILITY AND HOW TO CONTRIBUTE NEW CODE/PATCHES ---------------------------------------------------------- Starting from version 1.5, the source code of Anetd is available under the terms of the "Community License", detailed in the file LICENSE. We will be glad to incorporate new code/bug fixes, according to the license. Please submit your code to abocc@isi.edu. HOW TO SUBMIT BUG REPORTS ------------------------- We want to hear bug reports, so we can improve Anetd. Please send bug reports to abocc@isi.edu. Before doing that, try to make your bug reproducible and include the output of anetd -v. COPYRIGHT NOTICES ----------------- Anetd includes software with the following copyrights: *** Copyright (c) 1995-1999 Kungliga Tekniska Högskolan (Royal Institute of Technology, Stockholm, Sweden). All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the Institute nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE INSTITUTE AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE INSTITUTE OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. *** Java Security Manager for Anetd USC Information Sciences Institute Marina del Rey, California Copyright (c) 2000 by the University of Southern California All rights reserved. Permission to use, copy, modify, and distribute this software and its documentation in source and binary forms for any purpose and without fee is hereby granted, provided that both the above copyright notice and this permission notice appear in all copies. and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed in part by the University of Southern California, Information Sciences Institute. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. THE UNIVERSITY OF SOUTHERN CALIFORNIA makes no representations about the suitability of this software for any purpose. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Other copyrights might apply to parts of this software and are so noted when applicable. *** Copyright (c) 1998 Todd C. Miller All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.