1. 28 Nov, 2004 1 commit
  2. 15 Oct, 2003 1 commit
    • Mike Hibler's avatar
      Uniform syslog'ing. Change everything I could find to use a syslog facility · cc6d6fa7
      Mike Hibler authored
      as defined in the defs-* file (e.g. "TBLOGFACIL=local2").  The default is
      "local5" which is what we are setup to use so you shouldn't need to mess
      with your defs- file!
      
      perl scripts just get this value configured in when configure is run.
      C programs get the value in two ways.  For programs that are intimate with
      the testbed infrastructure, and include "config.h", they just get it from
      that file.  For programs that we sometimes use outside the Emulab build
      environment (e.g., frisbee, capture) and that don't include config.h,
      the value is set via a "-DLOG_TESTBED=..." in the GNUmakefile build line.
      If the value isn't set, it defaults to what it used to be (usually LOG_USER).
      
      Still to do: healthd, hmcd (whose build doesn't seem to be completely
      integrated) and plabdaemon.in (since its icky python :-)
      cc6d6fa7
  3. 10 Sep, 2002 1 commit
  4. 10 Jul, 2002 1 commit
  5. 04 Jul, 2002 1 commit
  6. 05 Apr, 2002 1 commit
    • Chad Barb's avatar
      Added SSL to capture (enabled with -DWITHSSL) · 2e536ba3
      Chad Barb authored
      To tip (or tiptunnel on a normal acl,) capture behaves the same.
      However, if a client connects and presents "USESSL" as the first six characters of their
      connection key, both sides initiate SSL negotiation.
      The server then attempts to get the key again. The second one is used for the check.
      
      SSL initialization is done on the first attempt by a client to connect via SSL.
      Capture assumes $(prefix)/etc/capture/cert.pem contains its certificate unless
      the '-c <certfile>' option is used.. if the certificate is not found or invalid, that
      connection fails, but normal connections will still succeed (and it will try to find the file
      again, next time an SSL connection is attempted.)
      
      On the client side, tiptunnel only uses ssl if there is a "ssl-server-cert:"
      property in the acl file. This is the SHA hash of the certificate that the capture server is
      expected to have (in hex.) If the certificate presented by the server does not hash to the
      same value, the connection is dropped.
      2e536ba3
  7. 11 Feb, 2002 1 commit
  8. 09 Jan, 2002 2 commits
  9. 16 Aug, 2001 1 commit
  10. 13 Aug, 2001 1 commit
  11. 09 Aug, 2001 1 commit
  12. 24 Jul, 2001 1 commit
    • Leigh B. Stoller's avatar
      Checkpoint new version of capture/tip that is sockets based instead · 34499cb6
      Leigh B. Stoller authored
      of pty/tty based (since they have several annoying problems
      associated). Note that permission is granted via the use of an "acl"
      file; /dev/tip/machine.acl, which must be set to the group of the
      project the node is in, so the user can read out the process id number
      and the random bits that are used by capture to grant permission to
      use (tip sends the random bits across first thing). This handshake is
      due to change to a request/challenge scheme as described by Dave in
      email to the testbed list.
      34499cb6
  13. 26 Jun, 2001 2 commits
  14. 05 Jan, 2001 1 commit
  15. 03 Jan, 2001 1 commit
  16. 02 Jan, 2001 2 commits
  17. 30 Dec, 2000 1 commit
  18. 10 Oct, 2000 1 commit
    • David G Andersen's avatar
      Initial import of the "capture" source into the testbed repository. · fec832e8
      David G Andersen authored
      Note that this has a hardcoded value for NBPG, a define that's only
      present in the digiboard headers.  In the interest of minimal source
      code changes (heh, heh, heh) I left it alone. :p
      
      Works on *bsd, and now Linux.  Manpage included at no charge,
      though if someone wants to figure out why the manpage only
      works under BSD ("Because Dave is an idiot" is not an acceptable
      answer, true as it may be), that'd be cool.
      fec832e8