-
Bug
-
Resolution: Fixed
-
P3
-
1.4.1_02
-
05
-
generic
-
solaris_8
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2069311 | 5.0 | Fred Oliver | P3 | Closed | Fixed | beta |
| JDK-2069310 | 1.4.2_02 | Fred Oliver | P3 | Closed | Fixed | 02 |
customer using 1.4.1_02
usr/sbin/chroot /chroot /usr/j2se/bin/java -version
Output is:
Need Solaris 2.6 (SunOS 5.6) or later.
Abort
I was able to reproduce this in house and running truss I find that
/proc/<pid> is looked for but not found. It is at that point that
the error message about needing 2.6 or later is encountered.
This scenario works fine for 1.3.1 where you can see the /proc entry in the truss and it is also not being found, but it still proceeds.
Needing/exposing /proc in the chroot environment is a security risk.
Why would 1.4.1 now require this where 1.3.1 did not?
usr/sbin/chroot /chroot /usr/j2se/bin/java -version
Output is:
Need Solaris 2.6 (SunOS 5.6) or later.
Abort
I was able to reproduce this in house and running truss I find that
/proc/<pid> is looked for but not found. It is at that point that
the error message about needing 2.6 or later is encountered.
This scenario works fine for 1.3.1 where you can see the /proc entry in the truss and it is also not being found, but it still proceeds.
Needing/exposing /proc in the chroot environment is a security risk.
Why would 1.4.1 now require this where 1.3.1 did not?
- backported by
-
JDK-2069310 missing /proc/<pid> dir in chroot env. causes 1.4.1 java to fail
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-