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-next>] [day] [month] [year] [list]
Message-ID: <405F5C52.5040907@egotistical.reprehensible.net>
From: ge at egotistical.reprehensible.net (Gadi Evron)
Subject: viruses being sent to this list

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all, I kept quiet for a while as this is a not moderated mailing
list - but enough is enough.

Today's spoof, of an email supposedly coming from me with an infected
file was a cute trick by whatever kiddie, but doesn't really bother me.

What does bother me is the following:

Although this list is not moderated and thus suffers from an extremely
high noise-signal ratio, not to mention stupidity and flame wars, that
is all within acceptable parameters of being an unmoderated mailing list.

One who doesn't wish to be on it, can leave. One who doesn't wish to
read, can skip and/or delete email messages.

However, the mailing list has become, in a growing trend, a means by
which people transfer viruses, whether it is their intention or if they
got "0wned" is irrelevant, distributing malware is illegal, and should
be dealt with by the list owners.

It is also a growing concern among some of us that VX'ers now use this
list to propagate viruses, once they are out in the wild.

Viruses must not be spread, especially on a security mailing list and to
such a huge audience.

It is my opinion that it is the _duty_ of the list owners to do
something about this, as it is not only illegal, but it is irresponsible.

I'd have emailed the list owners privately, but as I am the latest
victim of the latest spreading mechanism for viruses - Full-Disclosure,
I demand and immediate public announcement on what is going to be done
about this problem.

Thank you,

	Gadi Evron.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)

iD8DBQFAX1xPqH6NtwbH1FARAt5qAJ9uhCsQnbhY14he9VJCX+0Dw5jjywCgirZQ
EF1aq5XqpNPKujNxf0DJvOo=
=Rk7E
-----END PGP SIGNATURE-----


Powered by blists - more mailing lists