Gentoo Archives: gentoo-hardened

From: Barry Dunn <lists@×××××××××××.uk>
To: gentoo-hardened@l.g.o
Subject: Re: [gentoo-hardened] Can't start eterm and xterm as normal user using X under SELinux and hardened gcc
Date: Fri, 24 Sep 2004 18:00:47
Message-Id: 20040924185342.6eeeaaf3@gen.aqui
In Reply to: [gentoo-hardened] Can't start eterm and xterm as normal user using X under SELinux and hardened gcc by Victor Banatean
1 On Fri, 24 Sep 2004 16:51:11 +0200
2 Victor Banatean <Pie_Oh_Pah@×××.net> wrote:
3
4 > Hi everyone,
5 >
6 > I have a problem using eterm and xterm when starting X as a normal
7 > user, as soon as I switch to root no problem at all.
8 >
9 > This is the error message for eterm and xterm:
10 > Eterm: Error: Can't open pseudo-tty -- No such file or directory
11 > Eterm: Error: Unable to run sub-command
12 >
13 > xterm: Error 32, errno 2: No such file or directory
14 > Reason: get_pty: not enough ptys
15 >
16 > I looked things up at the Gentoo-forums.
17 >
18 > My system:
19 >
20 > SELinux with hardened gcc-3.3.4-r1
21 > kernel-2.6.7-hardened-r8
22 > pentium4
23 > xorg--x11-6.7.0-r2
24 > eterm-0.9.2-r6
25 > xterm-191
26 >
27 > That is what I tried/looked up so far:
28 >
29 > 1. Change /etc/fstab
30 > => none /dev/pts devpts defaults 0 0
31 >
32 > 2. change to normal user and type export DISPLAY=:0
33 > and than type startx
34 >
35 > 3. compile /dev fs into kernel, following the options I used:
36 > => /dev file system support (obsulete)
37 > => Automatically mount at boot
38 > => debug devfs
39 >
40 > 4. Change /etc/security/selinux/src/policy/users
41 > => user victor roles {sysadm_r staff_r}
42 >
43 > 5. This is my /etc/devfsd.conf
44 > .....................................................................
45 > ..................................
46 >
47 > .....................................................................
48 > ..................................
49 >
50 > # Uncomment the following if you want to set the group to "tty" for
51 > the# pseudo-tty devices. This is necessary so that mesg(1) can later
52 > be used to
53 > # enable/disable talk requests and wall(1) messages.
54 > REGISTER ^pty/s.* PERMISSIONS -1.tty 0600
55 > REGISTER ^pts/.* PERMISSIONS -1.tty 0600
56 >
57 > 6. Also compiled into the kernel:
58 > => [*] Legacy (BSD) PTY support
59 > => (111) Maximum number of legacy PTY in use
60 >
61 > => [*] /proc file system support
62 > => [ ] /dev file system support (OBSOLETE)
63 > => [*] /dev/pts Extended Attributes
64 > => [*] /dev/pts Security Labels
65 > => [*] Virtual memory file system support (former shm fs)
66 > => [ ] HugeTLB file system support
67 >
68 > Number 1,2,4 nothing changed, if I tried number 3 the system
69 > crashed next after reboot.
70 >
71 > At the moment I got badly stuck.
72 > It would be great if someone could help me or give me a hint
73 > where to look next.
74 >
75 > Thanks in advance.
76 > Victor
77 >
78 > --
79 > gentoo-hardened@g.o mailing list
80 >
81
82 Are you using udev-030? I had the same problem recently and
83 emerging udev-032 fixed it. In both cases I had tty udev perms
84 set to root:tty:0660, but I assumed the error was caused by a tty entry
85 in 50-udev.rules, which in 032 was changed from
86 KERNEL="tty[p-za-e][0-9a-f]*", NAME="tty/s%n", SYMLINK="%k"
87 to
88 KERNEL="tty[p-za-e][0-9a-f]*", NAME="pty/s%n", SYMLINK="%k"
89
90 Hope that helps,
91
92 Barry
93
94 --
95 gentoo-hardened@g.o mailing list

Replies