From owner-freebsd-security Wed Dec 1 14: 0:56 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 E8A2014F94 for ; Wed, 1 Dec 1999 14:00:54 -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 QAA21687; Wed, 1 Dec 1999 16:00:17 -0600 (CST) (envelope-from thanatos@incantations.net) Date: Wed, 1 Dec 1999 16:00:17 -0600 (CST) From: Jason Hudgins To: Paul Hart Cc: freebsd-security@FreeBSD.ORG Subject: Re: logging a telnet session In-Reply-To: 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 > 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