From owner-freebsd-security Sun Sep 13 14:20:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04141 for freebsd-security-outgoing; Sun, 13 Sep 1998 14:20:20 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from alecto.physics.uiuc.edu (alecto.physics.uiuc.edu [130.126.8.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04135 for ; Sun, 13 Sep 1998 14:20:17 -0700 (PDT) (envelope-from igor@alecto.physics.uiuc.edu) Received: (from igor@localhost) by alecto.physics.uiuc.edu (8.9.0/8.9.0) id QAA15620; Sun, 13 Sep 1998 16:19:55 -0500 (CDT) Date: Sun, 13 Sep 1998 16:19:55 -0500 (CDT) From: Igor Roshchin Message-Id: <199809132119.QAA15620@alecto.physics.uiuc.edu> To: security@FreeBSD.ORG Subject: X-security Cc: cschuber@uumail.gov.bc.ca Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > That is why doing an xhost + or even and xhost hostname even to hosts > that you think you trust is so dangerous. It is easy for someone to > inject some "keystrokes" into an Xterm to get a root shell on a host > that one is logged into. > > > Regards, Phone: (250)387-8437 > Cy Schubert Fax: (250)387-5766 > Open Systems Group Internet: cschuber@uumail.gov.bc.ca > ITSD Cy.Schubert@gems8.gov.bc.ca > Government of BC > May be I am wrong, but xterm (when correctly configured, e.g.: no emulation enabled) will not allow to do that. am I blindly wrong ? The much higher danger in having xhost set to allow outside, or even inside connections - possibility of "steeling" your keystrokes. AFAIK, XFree86 does allow to disable access to your DISPLAY even from the localhost by other users (E.g. on SGIs one can always run any program with DISPLAY set local to localhost:0, and you can not disable that). Regards, IgoR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message