full-disclosure - 411 [ sneak previews ]

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: aliver at xexil.com (aliver@...il.com)
Subject: 411 [ sneak previews ] - #1

On Tue, 27 Aug 2002, Slack wh0re wrote:
> /*
> * Anatomy.c

Dude, no offense but this kind of thing could be spiced up a lot and has
been done quite a bit already. I can appreciate that you have some coding
skills, so don't take this as me dissing you. I'm sure 98% of the list
can't code hello.c, but I think you can do better. Here are some ideas to
help make it possibly better.

* Use a library like libnet to connect "raw" and add options to create
spoofed connections to hosts with weak ISN generation.

* Take a look at octopus.c (out there somewhere) and emulate the same
technique to (optionally?) do the same type of thing to all open ports and
have a brute force "my machine can afford to keep more ports open that
yours" type contest. You might even add a simple portscan routine to make
this more efficient.

* Use getopt() and make it more interactive. This always pleases the kidz.

* Add signal handling in case people want to fire off lots of these and
kill them gracefully later (ie.. graceful or not so graceful closing of
your connections might be interesting).

* Perhaps add some protocol specific (telnet?) attacks to your
bomb_string.

* Add UDP functionality.

If you are interested email in private. I've been working on some blackhat
flavored cryptographic tools lately, but if you want someone to bounce
ideas off I'd be happy to kick the can with ya'.

aliver