full-disclosure - mydoom.c information

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: mducharme at cybergeneration.com (Maxime Ducharme)
Subject: mydoom.c information

Another way :

Create a script named "mydoom_listener",
chmod 700 mydoom_listener, and then start it
via ./mydoom_listener &


mydoom_listener contains 2 lines :
nc -l -p 3127 > doomjuice.dump$$
./mydoom_listener &

will create random file names.

Ciao

Maxime Ducharme Programmeur / Sp?cialiste en s?curit? r?seau

----- Original Message ----- 
From: <m.mohr@...oste.net>
To: "Frank Knobbe" <frank@...bbe.us>
Cc: <full-disclosure@...ts.netsys.com>
Sent: Monday, March 08, 2004 2:01 AM
Subject: RE: [Full-Disclosure] mydoom.c information


>
>
> On Sun, 7 Mar 2004, Frank Knobbe wrote:
>
> > On Sun, 2004-03-07 at 19:47, Chris Eagle wrote:
> > > > As I recall the -L option (persistent listener) only works on the
windows
> > > > port.
> > > >
> > >
> > > If you want it for Unix:
> >
> > How about?
> >
> > while true;do nc -l -p 1234;done
>
> The problem with that is that there is no incrementing counter.  The
> output never gets written to file, since nc sends data directly to stdout.
> Which is why I had an 'x' variable in my loop - it conveniently increments
> by one each iteration, thus generating a new filename.
>
> 3127.1
> 3127.2
> 3127.3
>
> etc
>
>
> -Mike
>
> >
> > Forrest? Trees?
> > -Frank
> >
> >
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
>