Re: Regarding Security Problem - Murali (India)

Hello. MySQL doesn't support Windows 98, and it's (Windows 98 certainly) design isn't enough secure. There're no file system which has support for file permissions. Upgrade to the fresher Windows (2k, XP, 2003) will allow you to solve this issue by protecting 'mysql' database from replacemen

Regarding Security Problem - Murali (India)

First I have to Thank you for creating such a wonderful backend. Problem Statment : My Operating System is Windows 98. I have set password for my MySql database. Its working fine. Following are the databases that i am using in My Data Folder Employee Sales Marketing

Re: security problem

Hello. On Wed 2002-10-02 at 09:49:30 -0400, [EMAIL PROTECTED] wrote: > Hi! I found a security bug on mysqlgui-win32-static-1.7.5-2. When I > install it on my desktop (win2k), I setup a password for the > database. What does "setup a password for the database" mean? Passwords are not per-database

security problem

Hi! I found a security bug on mysqlgui-win32-static-1.7.5-2. When I install it on my desktop (win2k), I setup a password for the database. However, if I install the mysqlgui on any machine in the local network, I could access the database on my desktop (from any machine on the local network) witho

Re: Security problem

Daniel's, Friday, August 30, 2002, 3:11:17 AM, you wrote: DsL> *This message was transferred with a trial version of CommuniGate(tm) Pro* DsL> I installed Mac OS X 10.2 this last weekend and since then I've been DsL> having some problems with the security on the MySQL files. I thought DsL> tha

Security problem

*This message was transferred with a trial version of CommuniGate(tm) Pro* I installed Mac OS X 10.2 this last weekend and since then I've been having some problems with the security on the MySQL files. I thought that I had everything fixed, but now when my web users try and update or insert a

Replication security problem

Hi I implemented replication in my databases, and I can see a security problem. When you configure the slave you must write the replication user password in the my.cnf file. If somebody access this file will see the password and the user name, so if he can and want he will get access to the

Re: Security problem in Access database

Jack writes: > 1. What should i do if i want to limit the user which can only edit the > record belongs to him/her. i mean user can only update to his own record but > not the others!! This sort of security is best handled at the application level. If you don't want your users to access the dat

Security problem in Access database

Dear all I'm planning to make a webpage which will let the user to enter the leave request record into one of the database's table. Actually the user can add, update the record with this table. Here is the question i want to ask: 1. What should i do if i want to limit the user which can only edit

databases with underscores security problem

(underscore) in it >Submitter-Id: [EMAIL PROTECTED] >Originator:F. Kooman >Organization: >MySQL support: none >Synopsis: mysql database creation security problem >Severity: serious >Priority: medium >Category: mysql >Class: sw-bug >

Re: Security problem with 3.23.38

Hi! > "Sinisa" == Sinisa Milivojevic <[EMAIL PROTECTED]> writes: Sinisa> Robert Cross writes: >> >> I've got a wierd problem with 3.23.38, built from source, running on RedHat >> v6.2 (Intel). Put simply the wildcard character for user access doesn't >> work. From my reading of the docs an

Re: Security problem with 3.23.38

Robert Cross writes: > > > I wrote: > >Try first granting USAGE on *.* to both users with 'identified by ...' > >and then try granting database rights. > > Thanks Sinisa, that works perfectly. I've now got a wonderful small and > fast database > that I can let the users into! > > Bob Cross. Y

Re: Security problem with 3.23.38

I wrote: >> I've got a wierd problem with 3.23.38, built from source, running on RedHat >> v6.2 (Intel). Put simply the wildcard character for user access doesn't >> work. From my reading of the docs any of the following: >> grant all on mtdb.* to user1 identified by "bozo1"; >> grant

Re: Security problem with 3.23.38

Robert Cross writes: > > I've got a wierd problem with 3.23.38, built from source, running on RedHat > v6.2 (Intel). Put simply the wildcard character for user access doesn't > work. From my reading of the docs any of the following: > > grant all on mtdb.* to user1 identified by "bozo1"; >

Security problem with 3.23.38

I've got a wierd problem with 3.23.38, built from source, running on RedHat v6.2 (Intel). Put simply the wildcard character for user access doesn't work. From my reading of the docs any of the following: grant all on mtdb.* to user1 identified by "bozo1"; grant all on mtdb.* to user2@"