full-disclosure - Re: new openssh exploit in the wild! * isFAKE AS SH@!*

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: vosipov at tpg.com.au (V.O.)
Subject: Re: new openssh exploit in the wild! * isFAKE AS SH@!*

Yeah, I missed the fact that after "calculating" the offset it starts to
"exploit" in the same way as if it was given an offset as a parameter.
Anyway, I simply wanted to note that whoever posted it here was either
knowingly lying about its purpose or not having a clue about UNIX at all :)

W.


----- Original Message ----- 
From: "Adam Balogh" <adam@...tnet.net>
To: "Full Disclosure" <full-disclosure@...sys.com>
Sent: Friday, September 19, 2003 9:47 PM
Subject: Re: [Full-Disclosure] Re: new openssh exploit in the wild! * isFAKE
AS SH@!*


> Vitaly Osipov wrote:
> > which is obviously not true. Btw as far as I understand, the troyan code
is triggered when
> > the "exploit" is run with the offset specified, and not in a
"bruteforcing" mode.
> >
> > W.
>
> Me and my friend tried to run it on a lab-box thats not connected
> directly to internet and doesnt relay mails. It doesn't use that
> special offset as a trigger. We got so many "sys3" accounts in
> /etc/passwd as many times we ran it plus those outgoing-mails que'd.
>
> /Adam Balogh
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
>
>