From owner-freebsd-security Wed Dec 1 14:18:57 1999 Delivered-To: freebsd-security@freebsd.org Received: from eddie.incantations.net (adsl-208-189-80-58.dsl.rcsntx.swbell.net [208.189.80.58]) by hub.freebsd.org (Postfix) with ESMTP id 5C65A14F94 for ; Wed, 1 Dec 1999 14:18:50 -0800 (PST) (envelope-from thanatos@incantations.net) Received: from eddie.incantations.net (thanatos@eddie.incantations.net [208.189.80.58]) by eddie.incantations.net (8.8.8/8.8.8) with ESMTP id QAA23297 for ; Wed, 1 Dec 1999 16:16:52 -0600 (CST) (envelope-from thanatos@incantations.net) Date: Wed, 1 Dec 1999 16:16:52 -0600 (CST) From: Jason Hudgins Cc: freebsd-security@freebsd.org Subject: Re: logging a telnet session In-Reply-To: <4.2.0.58.19991201140744.014d5dd0@mail1.dcomm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org That would require trojanizing my own sshd, my own netstat, and settup up a packet sniffer on an external machine, I still think that trojaning only ps would be easier. > Paul also suggested leaking the cleartext before encryption which is also > good. It would roughly double the local bandwidth used by him, but I can't > doubling telnet/ssh would be a big deal. a netstat may give this away, but > you could use udp to send the plaintext to the logging host. As for > writing this from scratch, you may be able to find something like this in a > rootkit. > > > At 04:00 PM 12/1/99 -0600, you wrote: > > > No. Remember, you're the one calling the shots. Go ahead and trojan your > > > own sshd to leak session keys so you can decrypt the sniffed sessions, or > > > even better, have it leak the cleartext before encrypting it. > > > >Well, I think it would be easier to just trojanize some binaries on > >the cracked box (like ps) and make the logging process invisible then to > >trojan sshd AND write a decryption client of sorts. > > > > > The original poster wanted to watch a telnet session anyway. > > > >Yeah, I was the original poster, I'm just talking theory now. =) > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-security" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message