configure fix-ups and security on -P

[Mark Poepping]

possible fix for memory leak
Carter,
Do you have the configure.in macro foo?  We don't put the libpcap in
the 'usual suspect' directories in our software management scheme
and are used to being able to tell configure where to look..  We can
probably patch, or perhaps bulk-replace..  Also there's no install
target [yet]..  Do you want this stuff fixed at some point?  We could
do this.

What about security (beyond tcpd) on the argus port?  We were thinking
perhaps just add SASL support to argus, this way both client and server
get it compiled in via shared code, just as now..  Should be okay to add
conditional compilation, with flexible authentication options that come
with SASL, so you'd get TLS with it too..

Thoughts?
mark.

  -----Original Message-----
  From: owner-argus at lists.andrew.cmu.edu
[mailto:owner-argus at lists.andrew.cmu.edu]On Behalf Of Carter Bullard
  Sent: Friday, September 29, 2000 11:14 PM
  To: Argus (E-mail)
  Subject: possible fix for memory leak


  Gentle People,
     I found a big bad memory problem.  One that would
  explain both the memory leak and Russell's loss of
  flows from the new Argus.

  I was using a fixed length queue to manage all the
  flows, and I suspect that you guys were exceeding
  that number.  Not what I was expecting, and so I didn't
  put in any smarts to handle it.

  This problem should be done.  (I just wonder if
  it will really fix anything :o)

  I put the new tarfile up late Fri as
  ftp://qosient.com/dev/argus/argus-2.0/argus-2.0.0k.tar.gz

  Just try to bomb with this one ;O)

  Carter

  Carter Bullard
  QoSient, LLC
  300 E. 56th Street, Suite 17A
  New York, New York  10022

  carter at qosient.com
  Phone +1 212 813-9426
  Fax   +1 212 813-9426

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20000930/f03c2e94/attachment.html>