full-disclosure - No shell => secure?

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]

Message-ID: <200407092114.07648.npguy@websurfer.com.np>
From: npguy at websurfer.com.np (npguy)
Subject: No shell => secure?

On Friday 09 July 2004 08:19 am, hax wrote:
> 2)  That'd stop a lot of skript kiddies, I guess, but it'd be pretty
> trivial to just rework the shellcode to call some other command
> instead of /bin/sh.

if this is single target. attacker can guess your setting and keeping
executing any commands it could possible target to execute more attack
what about wget from shellcode.