full-disclosure - Interscan - path disclosure - WAS:SpamAssasin

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

From: se_cur_ity at hotmail.com (morning_wood)
Subject: Interscan - path disclosure - WAS:SpamAssasin - path disclosure

Messageahhh, 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 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 
  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/323c407a/attachment.html