-
Alternatively, .CURE might be moved to a place that's generally more sensible in a server setting. On a *IX system, this might be something like /var/lib/CURE. Uploads would go there as well, so they still would be outside Tomcat's directory tree.
2008-04-21 09:39:57 UTC in CURE
-
An anonymous user can take keys "hung" to a room. If that key has sufficient privilege, any person in the world can deposit files in a CURE room and make them accessible to anyone else in the world. This way, a CURE installation can easily be abused as a host for illegal or otherwise dubious material.
Suggested short-term solution: explicitly forbid Anonymous to take or receive any key...
2008-04-15 11:30:08 UTC in CURE
-
Currently CURE can only be set up through a JavaScript-enabled browser installed locally on the server CURE is supposed to run on. This requirement makes remote administration of a CURE server annoying, if not even impossible.
Server-centered OS distros (e.g. SLES 10) usually do not come with a full-fledged browser, requiring users to install one by hand. But even if one is installed, one...
2008-02-10 12:49:28 UTC in CURE
-
Workaround: on systems like these, give the 'tomcat' user an actual home dir, e.g. (as root):
mkdir /usr/share/tomcat-common
chown tomcat.tomcat /usr/share/tomcat-common
usermod --home /usr/share/tomcat-common tomcat
(It's called 'tomcat-common' because Gentoo e.g. allows its users to install Tomcat 5 and Tomcat 6 in parallel.)
2008-02-08 16:50:01 UTC in CURE
-
CURE saves its configuration (along with uploaded files) in '$HOME/.CURE', where $HOME is the home directory of the user running Tomcat.
This, however, seems to be a bad idea on systems where the user running Tomcat does NOT have a home dir. E.g., on Gentoo Linux systems, the 'tomcat' user by default has their home dir set to '/dev/null'.
Incidentally, what was wrong with putting...
2008-02-08 16:40:30 UTC in CURE
-
Under certain circumstances, CURE crashes leaving the following message in catalina.out:
X connection to localhost:10.0 host broken (explicit kill or server shutdown)
To reproduce do the following:
* remotely log in to your server
* start up Tomcat
* open a browser and configure CURE
* close the browser
* log out again
As it seems, the connection to the X server is closed at...
2008-02-08 14:18:27 UTC in CURE
-
Of course, I should have mentioned that I'm talking about CURE's title page...
2007-08-03 16:29:42 UTC in CURE
-
Somewhere between June 1st and the release of CURE 1.0.0, the "register" link ("Passwort anfordern" in German) has vanished.
Compare this screenshot (CURE-1.0.0): with this one (CVS snapshot 2007-06-01): .
2007-08-03 13:35:30 UTC in CURE
-
We definitely could have used an installation guide over here. OTOH, we've gathered some experience installing CURE on various Linux distros, so we should be able to contribute.
Maybe, if you'd just assign some kind of wiki (why not e.g. on the "old" CURE server in Hagen?), we could probably create some exhaustive doc cooperatively (yes, I meant to write that ;-).
2007-07-14 14:29:19 UTC in CURE
