[Full-Disclosure] RE: 7350reass - alleged *BSD remote kernel exploit
From: Dave M. Wilson (full-disclosure@botanicus.net)
Date: 10/22/02
- Next message: KF: "[Full-Disclosure] RE: 7350reass - alleged *BSD remote kernel exploit"
- Previous message: Janusz Niewiadomski: "[Full-Disclosure] RE: 7350reass - alleged *BSD remote kernel exploit"
- In reply to: Janusz Niewiadomski: "[Full-Disclosure] RE: 7350reass - alleged *BSD remote kernel exploit"
- Next in thread: KF: "[Full-Disclosure] RE: 7350reass - alleged *BSD remote kernel exploit"
- Reply: KF: "[Full-Disclosure] RE: 7350reass - alleged *BSD remote kernel exploit"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: full-disclosure@botanicus.net (Dave M. Wilson) Date: Tue, 22 Oct 2002 19:08:34 +0100
On Tue, Oct 22, 2002 at 07:32:42PM +0200, Janusz Niewiadomski wrote:
> Yet another, not interesting trojan horse which you probably don't
> want to run. One minute analysis is available at:
> http://isec.pl/funkysh/trash/ for those who interested.
Thanks for that. I had straced it half-heartidly inside a chroot to see
what would happen, and it SEGV'd. At least I now know it was worth
covering my back :).
I notice you have a 'plaintext' copy of the binary -- is there a no-fuss
method for decrypting burneye binaries? Thanks,
Dave.
- Next message: KF: "[Full-Disclosure] RE: 7350reass - alleged *BSD remote kernel exploit"
- Previous message: Janusz Niewiadomski: "[Full-Disclosure] RE: 7350reass - alleged *BSD remote kernel exploit"
- In reply to: Janusz Niewiadomski: "[Full-Disclosure] RE: 7350reass - alleged *BSD remote kernel exploit"
- Next in thread: KF: "[Full-Disclosure] RE: 7350reass - alleged *BSD remote kernel exploit"
- Reply: KF: "[Full-Disclosure] RE: 7350reass - alleged *BSD remote kernel exploit"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]