Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: Compiling kterm
- To: tlug@example.com
- Subject: Re: Compiling kterm
- From: Shimpei Yamashita <shimpei@example.com>
- Date: Fri, 22 Jun 2001 03:13:17 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <993094568.3b316ba9000be@example.com>; from jmglov@example.com on Wed, Jun 20, 2001 at 11:36:08PM -0400
- References: <200106210255.LAA26836@example.com> <20010621121801.A6901@example.com> <993094568.3b316ba9000be@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <tciNJC.A.leD.GujM7@example.com>
- Resent-Sender: tlug-request@example.com
On Wed, Jun 20, 2001 at 11:36:08PM -0400, Josh Glover wrote: > Quoting Christopher SEKIYA <wileyc@example.com>: > > > Consider using rxvt instead. kterm is horribly > > broken. > > Anybody using rxvt should be aware of some security bug > (root exploit, if I remember correctly). I don't remember > the details, but if you head over to www.securityfocus.com > and search the BugTraq archives, you should find a dozen > posts or so on the vulnerability. It's a root exploit only if rxvt has root privileges, i.e. setuid root. I hope nobody was *that* stupid in this day and age. (It looks like some distributions did install rxvt as setgid utmp.) -- Shimpei Yamashita http://www.shimpei.org/
- References:
- Compiling kterm
- From: jwb@example.com (Jim Breen)
- Re: Compiling kterm
- From: Christopher SEKIYA <wileyc@example.com>
- Re: Compiling kterm
- From: Josh Glover <jmglov@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: Binary - ASCII difference ?
- Next by Date: RE: NIC problem
- Prev by thread: Re: Compiling kterm
- Next by thread: Re: Compiling kterm
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links