Older lexi issue

[Carter Bullard]

Hey Neil,
   Lex takes the -P option on my Linux machine, no problem.
This is lex 2.5.4.  Because we are now merging the two
compilers together, we have to have this option in order
for the strategy to work.  Is there not a switch on your
lex that does the same thing as the -P option (specify
scanner prefix other than 'yy')?

   If not, we'll have to have two programs.  The argus
engine and the output mutliplexer will have to be
independent programs.  This causes potential security
gotchas, because we'll have to fork/exec something in 
the filesystem, which is a wonderful opportunity for
someone to swap programs.  That would give someone the
opportunity to put in their own embedded filters, thus
hiding tracks, or generating false trails.

   We can do it, but I'd rather not.

Carter

   

-----Original Message-----
From: Neil Long [mailto:neil.long at computing-services.oxford.ac.uk]
Sent: Monday, September 11, 2000 4:43 AM
To: carter at qosient.com
Subject: Re: argus-2.0.0c available


Hi

There is a problem with the 'fix' for configure to enable -Pargus in that
lex does not support the -P option, it is flex specific.

This kinda looks like flex is a pre-requisite??

Neil


> Here is a fix for ./configure that should work now.
>
> diff -r1.14 configure
> 1540,1541c1540,1541
> <     V_LEX="lex -Pargus_"
> <     V_YACC="yacc -p argus_"
> ---
> >     V_LEX="lex"
> >     V_YACC="yacc"
> 1542a1543
> >
> 1546a1548,1553
> >
> >     if test "$V_LEX" = lex -a -n "argus_" ; then
> >     V_LEX="$V_LEX -Pargus_"
> >     V_YACC="$V_YACC -p argus_"
> >     fi
> >
>