Full Disclosure mailing list archives
RE: Interscan - path disclosure - WAS:SpamAssasin - path disclosure
From: "Joshua Vince" <joshv () bcgsys com>
Date: Sun, 24 Aug 2003 21:41:34 -0400
What would you consider the "proper tool for the job"? -----Original Message----- From: morning_wood [mailto:se_cur_ity () hotmail com] Sent: Sunday, August 24, 2003 9:17 PM To: ViLLaN; full-disclosure () lists 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 () protonic com> To: full-disclosure () lists 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..
Current thread:
- RE: Interscan - path disclosure - WAS:SpamAssasin - path disclosure Joshua Vince (Aug 24)
- <Possible follow-ups>
- RE: Interscan - path disclosure - WAS:SpamAssasin - path disclosure suicyc0 (Aug 24)