1 |
On 02/21/2014 05:48 PM, Alexander Tiurin wrote: |
2 |
> hi! |
3 |
> |
4 |
> emerge return errors during build of any atoms in linux32 chroot only. |
5 |
> |
6 |
> (null)*(null) (null)ACCESS DENIED(null): open_wr: /dev/tty |
7 |
> (null)*(null) (null)ACCESS DENIED(null): open_wr: /dev/null |
8 |
> |
9 |
> The full log http://pastebin.com/4An1ajY0 |
10 |
> |
11 |
> stat /dev/{null,tty} |
12 |
> File: '/dev/null' |
13 |
> Size: 0 Blocks: 0 IO Block: 4096 character |
14 |
> special file |
15 |
> Device: 5h/5d Inode: 1028 Links: 1 Device type: 1,3 |
16 |
> Access: (0666/crw-rw-rw-) Uid: ( 0/ root) Gid: ( 0/ root) |
17 |
> |
18 |
> File: '/dev/tty' |
19 |
> Size: 0 Blocks: 0 IO Block: 4096 character |
20 |
> special file |
21 |
> Device: 5h/5d Inode: 1035 Links: 1 Device type: 5,0 |
22 |
> Access: (0666/crw-rw-rw-) Uid: ( 0/ root) Gid: ( 5/ tty) |
23 |
> |
24 |
> Kernel 3.11.7-hardened-r1 |
25 |
> Kernel config |
26 |
> zcat /proc/config.gz | grep -i -e grkern -e pax |
27 |
> http://pastebin.com/ka63Jf98 |
28 |
> |
29 |
> emerge --info |
30 |
> http://pastebin.com/WJ7BRXCA |
31 |
> |
32 |
> |
33 |
> In x86_64 chroot all works fine. Also, with hardened-sources-3.2.52-r3 |
34 |
> linux32 chroot works fine too. |
35 |
> Please suggest any solution. |
36 |
> |
37 |
|
38 |
|
39 |
There's not enough context to really nail it, but start by trying this: |
40 |
|
41 |
for i in /proc/sys/kernel/grsecurity/chroot_* ; do |
42 |
echo 0 > $i |
43 |
done |
44 |
|
45 |
Also, can you give my your `df -a` so I can see what is mounted in the |
46 |
chroot. Run that from *outside* the chroot. |
47 |
|
48 |
|
49 |
-- |
50 |
Anthony G. Basile, Ph. D. |
51 |
Chair of Information Technology |
52 |
D'Youville College |
53 |
Buffalo, NY 14201 |
54 |
(716) 829-8197 |