Liam MacKenzie wrote:
>permission to create tables in other databases, but the can
>still browse them and view the information.
>
I do not know MySQL but I'd be very surprised if this was not a database
creation/configuration issue. In postgres, unless given permission, I
cannot even connect t
Perhaps a better way of wording my question would have been to say this:
At the moment, I can make seperate users, the do not have
permission to create tables in other databases, but the can
still browse them and view the information.
Any the example I used for the named.conf was a bad one.
No, you're right..
Permissions for that file could probably be tighter,
but it's better not to rely on file system permissions only.
bvr.
>> And also...
>> How do I go about securing PHP functions. For example, at the moment Joe
>> can upload a PHP script that deletes /etc/named.conf. NOT
Liam MacKenzie wrote:
> And also...
> How do I go about securing PHP functions. For example, at the moment Joe
> can upload a PHP script that deletes /etc/named.conf. NOT GOOD!
>
Surely this is a general security issue? If an ordinary user is allowed
to delete /etc/named.conf (whether by PHP,
>Ok, I'm over it. Now...
>Does anyone know how to set up MySQL, or phpMyAdmin to restrict users to a
>single database? For instance, the user JoeBlow...
>Joe has a database called JB, I want him to have full access to it and
>nothing else. How would I go about doing this? I'd also like him
Ello all!
Whazzup?
Ok, I'm over it. Now...
Does anyone know how to set up MySQL, or phpMyAdmin to restrict users to a
single database? For instance, the user JoeBlow...
Joe has a database called JB, I want him to have full access to it and
nothing else. How would I go about doing this? I'd a
6 matches
Mail list logo