full-disclosure - Re: Filtering sobig with postfix

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: Bojan.Zdrnja at LSS.hr (Bojan Zdrnja)
Subject: Re: Filtering sobig with postfix


> -----Original Message-----
> From: full-disclosure-admin@...ts.netsys.com 
> [mailto:full-disclosure-admin@...ts.netsys.com] On Behalf Of 
> martin f krafft
> Sent: Wednesday, 20 August 2003 10:43 p.m.
> To: full-disclosure@...ts.netsys.com
> Subject: [Full-Disclosure] Re: Filtering sobig with postfix
> 
> 
> also sprach vogt@...senet.com <vogt@...senet.com> 
> [2003.08.20.1017 +0200]:
> > in main.cf, enable "body_checks = (filename)". In that (filename)
> > file, write a regular expression matching sobig, e.g. something
> > like
> > 
> > /see attached file for details/	REJECT
> 
> this incurs a factor 2-4 performance drop, and it could also elicit
> false positives. you should definitely do more than just REJECT
> (i.e. write out a message: s/REJECT/554 Suspected virus/).

Yep, as the OP is using postfix, he could use the header_checks directive,
which can identify MIME headers, so he can easily stop this worm.
Just check for Content-Disposition header and block everything with .pif in
filename.

Regards,

Bojan Zdrnja