1. 27 Mar, 2012 1 commit
  2. 15 Mar, 2012 1 commit
  3. 28 Feb, 2012 1 commit
  4. 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
  5. 13 Feb, 2012 1 commit
  6. 07 Nov, 2011 1 commit
  7. 06 Oct, 2011 1 commit
  8. 05 Oct, 2011 1 commit
  9. 03 Oct, 2011 1 commit
  10. 13 Apr, 2011 1 commit
  11. 01 Oct, 2010 1 commit
  12. 17 Jun, 2010 1 commit
  13. 28 May, 2010 1 commit
  14. 10 May, 2010 2 commits
  15. 21 Apr, 2010 1 commit
  16. 16 Feb, 2010 1 commit
  17. 01 Dec, 2009 3 commits
  18. 02 Nov, 2009 2 commits
  19. 30 Oct, 2009 3 commits
  20. 16 Oct, 2009 2 commits
  21. 30 Sep, 2009 1 commit
  22. 15 Jul, 2009 1 commit
  23. 13 Jul, 2009 2 commits
  24. 10 Jul, 2009 1 commit
  25. 05 Jun, 2009 1 commit
  26. 04 Mar, 2009 1 commit
    • Leigh B. Stoller's avatar
      Change EMULAB-COPYRIGHT to GENIPUBLIC-COPYRIGHT, for future expansions · bb878eff
      Leigh B. Stoller authored
      to the Geni Public License at http://www.geni.net/docs/GENIPubLic.pdf,
      whose expansion at this time is:
      
      -----
      Permission is hereby granted, free of charge, to any person obtaining
      a copy of this software and/or hardware specification (the "Work") to
      deal in the Work without restriction, including without limitation the
      rights to use, copy, modify, merge, publish, distribute, sublicense,
      and/or sell copies of the Work, and to permit persons to whom the Work
      is furnished to do so, subject to the following conditions:
      
      The above copyright notice and this permission notice shall be
      included in all copies or substantial portions of the Work.
      
      THE WORK IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
      OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
      MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
      NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
      HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
      WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
      OUT OF OR IN CONNECTION WITH THE WORK OR THE USE OR OTHER DEALINGS
      IN THE WORK.
      bb878eff
  27. 10 Feb, 2009 1 commit
  28. 30 Jan, 2009 1 commit
  29. 27 Jan, 2009 1 commit
  30. 22 Jan, 2009 1 commit
  31. 21 Jan, 2009 2 commits