Bugs item #427967, was updated on 2001-05-28 07:21 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=427967&group_id=22866 Category: None Group: v2.2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Unix File permissions, run.sh Initial Comment: Linux IBM JDK 1.3 1) In JBoss-2.2.1_Tomcat-3.2.1.zip the directory file permissions are all rwxrwxrwx which is insecure as any user can add or delete files. I used cd into the root JBoss installation directory followed by chmod -R g-w,0-w * chown -R root.root * to remove group and other write permissions followed by chown -R root.jboss jboss/conf chmod -R g+w jboss/conf chown -R root.jboss jboss/conf chmod -R g+w jboss/conf chown -R root.jboss jboss/db chmod -R g+w jboss/db chown -R root.jboss jboss/deploy chmod -R g+w jboss/deploy chown -R root.jboss jboss/log chmod -R g+w jboss/log chown -R root.jboss jboss/tmp chmod -R g+w jboss/tmp chown -R root.jboss tomcat/conf chmod -R g+w tomcat/conf chown -R root.jboss tomcat/logs chmod -R g+w tomcat/logs to allow user jboss write access to directories that requires it for logs and deployment so JBoss runs as user jboss, but other files require root to change. 2) Directory jboss/db/jbossmg did not have it's execute permission set, so this was changed from drw-rw-r-- root jboss to drwxrwxr-x root jboss 3) The last line of jboss/bin/run.sh is java -server $JAXP...... which is an unrecognised option. I changed this to java $JAXP...... to get it to work. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=427967&group_id=22866 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
