Folks,
is it normal behavior for systems having woody-proposed-updates among
apt sources NOT to have a mysql update for the recently announced mysql
server vuln. ?
Proposed updates has mysql version 3.23.51-1woody5,
the security advisory (DSA 381-1) says 3.23.49-8.5
Now what ?
Is 3.23.51 not
David Stanaway wrote:
I am wandering if there is a way (which I am sure there is) to
automatically restart the mud after it crashes.
Try the openvt package maybe..
Or daemontools ?
(Beware, it's DJB :)
.SiCk of IT.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Stojan Rancic wrote:
Hello Marc,
AFAIK, the PHPMyAdmin version from potato
gives full access to the databases, allowing users to see data they
aren't supposed to see. Am I mistaken here?
You can (and should) only give the users access to their own database
( in the db table of
Stojan Rancic wrote:
Hello Marc,
AFAIK, the PHPMyAdmin version from potato
gives full access to the databases, allowing users to see data they
aren't supposed to see. Am I mistaken here?
You can (and should) only give the users access to their own database
( in the db table of mysql
Eirik Dentz wrote:
I have a virtual host configured under Apache 1.3.14 with SUEXEC support
enabled. My CGI/Perl scripts run as the USER/GROUP specified in the Virtual
Host directive in my httpd.conf file as they should, but for some reason my
PHP4 scripts don't. Rather they are running
5 matches
Mail list logo