1. 31 Aug, 2015 1 commit
  2. 30 May, 2014 1 commit
  3. 13 May, 2014 1 commit
  4. 28 Feb, 2013 1 commit
  5. 14 Jan, 2013 1 commit
  6. 10 Oct, 2012 1 commit
  7. 24 Sep, 2012 1 commit
    • Eric Eide's avatar
      Replace license symbols with {{{ }}}-enclosed license blocks. · 6df609a9
      Eric Eide authored
      This commit is intended to makes the license status of Emulab and
      ProtoGENI source files more clear.  It replaces license symbols like
      "EMULAB-COPYRIGHT" and "GENIPUBLIC-COPYRIGHT" with {{{ }}}-delimited
      blocks that contain actual license statements.
      
      This change was driven by the fact that today, most people acquire and
      track Emulab and ProtoGENI sources via git.
      
      Before the Emulab source code was kept in git, the Flux Research Group
      at the University of Utah would roll distributions by making tar
      files.  As part of that process, the Flux Group would replace the
      license symbols in the source files with actual license statements.
      
      When the Flux Group moved to git, people outside of the group started
      to see the source files with the "unexpanded" symbols.  This meant
      that people acquired source files without actual license statements in
      them.  All the relevant files had Utah *copyright* statements in them,
      but without the expanded *license* statements, the licensing status of
      the source files was unclear.
      
      This commit is intended to clear up that confusion.
      
      Most Utah-copyrighted files in the Emulab source tree are distributed
      under the terms of the Affero GNU General Public License, version 3
      (AGPLv3).
      
      Most Utah-copyrighted files related to ProtoGENI are distributed under
      the terms of the GENI Public License, which is a BSD-like open-source
      license.
      
      Some Utah-copyrighted files in the Emulab source tree are distributed
      under the terms of the GNU Lesser General Public License, version 2.1
      (LGPL).
      6df609a9
  8. 05 Apr, 2012 1 commit
  9. 04 Apr, 2012 1 commit
  10. 27 Mar, 2012 1 commit
  11. 15 Mar, 2012 1 commit
  12. 28 Feb, 2012 1 commit
  13. 17 Feb, 2012 1 commit
    • Leigh B Stoller's avatar
      Reorganize the protogeni installation code. · 99c1507e
      Leigh B Stoller authored
      * Split all of the certificate stuff out of initsite into initcerts so
        that it can be run independently, and when updating the IP/domain of
        a site.
      
      * Redo initsite in terms of libinstall. Fully automated now, no user
        intervention needed.
      
      * Regarding above statement, the new site no longer has to email the
        new CA certificate to us; a new web page is exported from the
        clearing house website that allows a new CA to be "provisionally"
        accepted; the new CA will be allowed to register their new protogeni
        certificates, but otherwise will have no access to anything else
        until someone at the ClearingHouse moves them from the unapproved to
        the approved column. 
      
      * New script called "cacontrol" that should be used from now on to
        manage the CA certificates. Also called from the web interface to
        provisionally install a new CA certificate into an "unapproved"
        bundle that is not distributed to other protogeni sites. Otherwise,
        cacontrol should be used as follows:
      
      	boss$ perl cacontrol -h
      	Usage: cacontrol [-a] [-n] [-d] <certfile>
      	       cacontrol [-n] [-d] -c <commonname>
      	       cacontrol [-n] [-d] -r <commonname>
      	Options
      	  -n     - Impotent mode; do not do anything for real
      	  -d     - Turn on debugging.
      	  -a     - Add certificate to approved list instead.
      	  -c     - Move certificate (commonname) to approved list.
      	  -r     - Remove certificate with given commonname.
      
        In the first form, add a new CA certificate to the unapproved list
        (this is the entrypoint used by the web page mentioned above). If
        you add the -a option, it goes right into the approved bundle
        (approved means it goes into the xmlsec directory and is exported to
        other sites).
      
        The second form is used to move a CA from the unapproved column to
        the approved colum.
      
        The third form is used to delete a CA certificate.
      
        NO MORE HAND EDITING OF THE FILES!
      99c1507e
  14. 13 Feb, 2012 1 commit
  15. 07 Nov, 2011 1 commit
  16. 06 Oct, 2011 1 commit
  17. 05 Oct, 2011 1 commit
  18. 03 Oct, 2011 1 commit
  19. 13 Apr, 2011 1 commit
  20. 01 Oct, 2010 1 commit
  21. 17 Jun, 2010 1 commit
  22. 28 May, 2010 1 commit
  23. 10 May, 2010 2 commits
  24. 21 Apr, 2010 1 commit
  25. 16 Feb, 2010 1 commit
  26. 01 Dec, 2009 3 commits
  27. 02 Nov, 2009 2 commits
  28. 30 Oct, 2009 3 commits
  29. 16 Oct, 2009 2 commits
  30. 30 Sep, 2009 1 commit
  31. 15 Jul, 2009 1 commit
  32. 13 Jul, 2009 2 commits