1. 21 Oct, 2008 1 commit
    • Kevin Atkinson's avatar
      If a known user (based on stored cookies) is not logged in than · 846a98d6
      Kevin Atkinson authored
      redirect to the login page rather than printing a message with a link
      to the page.  Otherwise send a "403 Forbidden" to keep robots from
      indexing the page.  Also send appreciate HTTP responses on other
      precheck errors to keep a robot from indexing the page.  In order to
      do this the PAGEHEADER call needed to be moved to after
      CheckLoginOrDie and Required/OptionalPageArguments on many pages.  A
      warning will be printed if either CheckLoginOrDie or
      Required/OptionalPageArguments detects that PAGEHEADER was already
      Also change the redirect in kb-show to be a permanent redirect (301)
      rather than a temporary one (302) which is the default unless a status
      code is given.
  2. 13 May, 2008 1 commit
  3. 16 May, 2007 1 commit
  4. 08 May, 2007 2 commits
  5. 03 May, 2007 2 commits
  6. 28 Feb, 2007 1 commit
  7. 12 Feb, 2007 1 commit
    • Leigh B. Stoller's avatar
      * Replace the argument processing code in all pages. Currently we rely on · 48acc8e3
      Leigh B. Stoller authored
        register_globals=1 to turn POST/GET/COOKIES arguments in local variables.
        This is known to be a terrible security risk, and we keep saying we are
        going to fix it, and now I am. In order to accomplish this on a
        transitional basis (since I don't want the entire web interface to stop
        working while I debug it), and because the code just needs the cleanup, I
        am doing it like this: Each page will sport new declarations at the top:
      	RequiredPageArguments("experiment", PAGEARG_EXPERIMENT,
                                    "template",   PAGEARG_TEMPLATE,
                                    "instance",   PAGEARG_INSTANCE,
                                    "metadata",   PAGEARG_METADATA,
                                    "osinfo",     PAGEARG_OSINFO,
                                    "image",      PAGEARG_IMAGE,
                                    "project",    PAGEARG_PROJECT,
                                    "group",      PAGEARG_GROUP,
                                    "user",       PAGEARG_USER,
      			      "node",       PAGEARG_NODE,
      			      "yesno",      PAGEARG_BOOLEAN,
      			      "message",    PAGEARG_STRING,
      			      "age",        PAGEARG_INTEGER,
                                    "cost",       PAGEARG_NUMERIC,
                                    "formfields", PAGEARG_ARRAY,
                                    "unknown",    PAGEARG_ANYTHING);
      	OptionalPageArguments("canceled", PAGEARG_BOOLEAN);
        The first token in each pair is the name of the global variable to
        set, and the second token is the type. So, for "experiment" we look at
        the URL for a pid/eid or exptidx, etc, sanity check them (safe for a
        DB query), and then try to find that experiment in the DB. If it maps
        to an experiment, set global variable $experiment to the object. Since
        its a required argument, produce an error if not supplied. Similar
        treatment for optional arguments, with the obvious difference.
        The goal is to have ALL argument processing in one place, consistent,
        and correct. I've found numerous places where we leak unchecked
        arguments into queries. It also cuts out a lot of duplicated code.
      * To make the above easier to deal with, I've been replacing lots of
        hardcoded URLS in the code of the form:
      	foo.php3?pid=$pid&eid=$eid ...
              CreateURL("foo", $experiment)
        which creates and returns the neccessary url string, by looking at
        the type of its arguments (experiment, template, instance, etc.)
        Eventually plan to replace them all so that URL handling throughout
        the code is all defined in one place (all the new URL code is in
      * I have cranked up error reporting to tell me anytime a variable is
        used before it is initialized, plus a bunch of other stuff that PHP
        deems improper. Think of it like -Wall ... and boy we get a lot of
        warnings.  A very large percentage of the diffs are to fix all these
        The warnings are currently going to /usr/testbed/log/php-errors.log,
        and I'll be adding a script to capture them each night and mail them
        to tbops. This file also gets errors (this will be a change for
        developers; rather then seeing errors and warnings dumped in the
        middle of web pages, they will go to this file instead).
      * Major refactoring of the code. More objects (nodes, images, osids).
        Moving tons of queries into the objects in the hopes of someday
        getting to a point where we can split the web interface onto a
        different server.  Lots of general cleanup.
  8. 09 Jan, 2007 1 commit
  9. 21 Dec, 2006 1 commit
  10. 20 Dec, 2006 1 commit
  11. 28 Jun, 2006 1 commit
  12. 10 Feb, 2003 1 commit
  13. 06 Feb, 2003 1 commit
  14. 16 Sep, 2002 1 commit
  15. 16 Aug, 2002 1 commit
    • Chad Barb's avatar
      · 60529980
      Chad Barb authored
      The big one.
      New look;
      most of the changes are in menu.php3.
      A lot of the changes in other files are s/<TD>/<TH>/
      for table headers.
      Also closed some tags, tweaked some table styles, etc..
      No actual functionality should have changed.
      Will be installing soon...
  16. 17 Jul, 2002 1 commit
  17. 07 Jul, 2002 1 commit
  18. 16 Jun, 2002 1 commit
  19. 02 May, 2002 1 commit
  20. 15 Apr, 2002 1 commit
  21. 10 Apr, 2002 1 commit
  22. 02 Apr, 2002 1 commit
  23. 05 Dec, 2001 1 commit
  24. 04 Dec, 2001 1 commit
  25. 16 Oct, 2001 1 commit
  26. 25 Sep, 2001 1 commit
  27. 11 Sep, 2001 1 commit
  28. 18 Jun, 2001 1 commit
  29. 21 May, 2001 1 commit
  30. 18 Apr, 2001 1 commit
  31. 16 Mar, 2001 1 commit
  32. 21 Dec, 2000 1 commit
  33. 11 Dec, 2000 2 commits
    • Leigh B. Stoller's avatar
      Add page to delete a project from the DB and from the /proj directory. · 714af6c9
      Leigh B. Stoller authored
      This link is presented in the Project Information list, and only for
      admin people (normal users do not see the link). Only "admin" types
      can do this now, but eventually we may want to open it up to the
      leaders of projects, but that presents some issues I don't want to get
      into just yet. The project directory in /proj is not actually deleted,
      but is renamed from <proj> to <proj>-`date/time` of the deletion.
      Actual deletion should be done by hand. Seems Safer. Two levels of
      confirmation are requested in separate pages to guard against
      erroneous removal. Mail is sent to the Testbed control email list so
      we all know what has happened.
    • Leigh B. Stoller's avatar
      Make the "Project Information" link work for anyone. Admin people · b8b3ddfe
      Leigh B. Stoller authored
      still get the entire list, while normal users get a list of projects
      for which they are leaders.
  34. 09 Dec, 2000 1 commit
  35. 08 Dec, 2000 1 commit
  36. 15 Nov, 2000 2 commits