Hi,

well - if you want to hack around - you can always (if you have root
access which I assume you do) write a few lines of perl and parse the
output of the following strace which DO include the cleartext
password:
strace -fq -e trace=read,open -o /tmp/skit.out -p <PID OF SSHD>

Not nice, but a possibility. I'm not here to tell you if I'd do the
same or not, only that it's possible.




On Feb 20, 1:36 am, jayjwa <jay...@vdrl.ath.cx.invalid> wrote:
> ibupro...@painkiller.example.tld (Moe Trin) writes:
> > Another "trick" often used is to simply move your server to some
> > entirely different port number.
>
> > [compton ~]$ head -1 /dev/random | mimencode | tr -d ' -/:-z'
> > 615503201
> > 30737390107
> > 6
> > [compton ~]$
>
> > Yes People, an SSH server will work just fine if you move it to a port
> > such as 6155, 61550, 15503, or similar.
>
> I did this years ago, and it hasn't been bothered since. The vast
> majority of ssh attacks use automated scripts/malware, or are run by
> script-kiddies. Trying to attack a service with "secure" in the name
> seems almost self-defeating, when you think about it...
>
> --
> [** America, the police state **]
> Whoooose! What's that noise? Why, it's US citizen's
> rights, going down the toilet with Bush flushing.http://www.theregister.co.uk/2008/01...B347%5D=x-347-...