[<prev] [next>] [day] [month] [year] [list]
Message-ID: <127D9E8872144749A56C77E94025D145DF5AFA@akrn09.stw.com>
From: joshv at bcgsys.com (Joshua Vince)
Subject: Interscan - path disclosure - WAS:SpamAssasin - path disclosure
What would you consider the "proper tool for the job"?
-----Original Message-----
From: morning_wood [mailto:se_cur_ity@...mail.com]
Sent: Sunday, August 24, 2003 9:17 PM
To: ViLLaN; full-disclosure@...ts.netsys.com
Subject: [Full-Disclosure] Interscan - path disclosure - WAS:SpamAssasin
- path disclosure
ahhh, ok you are the first to specifically state " section of the header
showing the path ".
thank you for the clarity.
Trend Interscan Viruswall has a path disclosure issue
So these products are often used in conjuntion with each other?
Trend Interscan Viruswall and Spamassasin run on the same box and
combining thier output?
i think im going to turbocharge, supercharge and nitrous my lawnmowers
<http://www.briggsandstratton.com/> Briggs & Stratton.
im sure i will cut more grass more better by stacking products and
solutions together instead
of purchasing the proper tool for the job.
morning_wood
----- Original Message -----
From: ViLLaN <mailto:villain@...tonic.com>
To: full-disclosure@...ts.netsys.com
Sent: Sunday, August 24, 2003 5:41 PM
Subject: RE: [Full-Disclosure] SpamAssasin - path disclosure
No one is denying that Spamassasin is in use, they are saying that the
section of the header showing the path (what your original post was
about from what I understood), is Interscan, not Spamassasin..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20030824/fcc2ddb1/attachment.html
Powered by blists - more mailing lists