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: mvp at joeware.net (joe)
Subject: Hey, ya! =))

Actually that is a pretty common practice for folks in large companies that
have mail systems that open zip files and will quarantine the whole email if
the zip has files with extensions that the mail "gods" have deemed
unfriendly such as .vbs, .pl, etc. Virus or not. Think MailWatch. 

It is a simple quick way of telling the automated systems to stay out of the
zip... It isn't to secure the zip from people.

Of course renaming the zips is another possibility too but I don't see it as
a stretch that companies start reading the first couple bytes and ascertain
a file is a zip irregardless of the extension and treat it as such. 

 

-----Original Message-----
From: full-disclosure-admin@...ts.netsys.com
[mailto:full-disclosure-admin@...ts.netsys.com] On Behalf Of madsaxon
Sent: Tuesday, March 09, 2004 11:58 AM
To: full-disclosure@...ts.netsys.com
Subject: Re: [Full-Disclosure] Hey, ya! =))


I can't really think of any legitimate reason to pwd-zip an attachment and
then include the pwd in plain text in the body.  I think it's safe to assume
that any such message is malware and discard it as far up the chain as
possible.

m5x



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ