Import to bypass security

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have discovered that to get around a secured Db, if you create a new Db
then import all objects from the secured Db you can then open the new one
without the password requirements and blocked permissions of the original
secured Db.

Have I missed something in the many instructions for securing your Db or is
this a known problem. Either way is there a solution to this problem?

TIA
Ian.
 
Ian said:
I have discovered that to get around a secured Db, if you create a
new Db then import all objects from the secured Db you can then open
the new one without the password requirements and blocked permissions
of the original secured Db.

Have I missed something in the many instructions for securing your Db
or is this a known problem. Either way is there a solution to this
problem?

TIA
Ian.
Click to expand...

You missed something. You would not be able to do that in a properly secured
file. You have to have certain permissions to import tables. Permissions that
the default user and group should not have.
 
Ian said:
I have discovered that to get around a secured Db, if you create a new Db
then import all objects from the secured Db you can then open the new one
without the password requirements and blocked permissions of the original
secured Db.

Have I missed something in the many instructions for securing your Db or is
this a known problem. Either way is there a solution to this problem?

TIA
Ian.
Click to expand...


Ian -
When you are logged on to your secure database as you - the developer.
Create a new database. This will make you the owner of the new database.
Import objects from original database into the new databse. If you did not
do that, than Admin is still the owner. If Admin is owner than someone else
can create a new database and import your tables in spite of your security.

Please see www.geocities.com/jacksonmacd. I used this step by step guide for
manually securing a database. It covers all the issues and why. The writer
of the document did an excellent job of explaining each step.

If you are not sure who is the owner of the database, follow these steps.

Tools/Security/User and Group Permissions/Tab=Change Owner/Object Type =
Database/Current Owner =Administrator or ?. Who is the Current Owner?

The owner should be you or a member of the development team. My first
paragraph illustrates how to change the owner but I highly recommend
following the referenced step by step guide to cover all of your bases.
Charlie
 
Hi,

Thanks for your experiences and the link to the "Holy Grail". I have read
and re-read the Microsoft Security FAQ and there was only a very short one
line about the solution you suggest but not explanation as to why you'd do
it, so thanks again for your help, much appreciated.

Ian.
 
Ian,
Glad I could help. I could not have made the advances I have made without
the assistance of the people on these discussion groups. I am giving back
what I have received.
Charlie
Hi,

Thanks for your experiences and the link to the "Holy Grail". I have read
and re-read the Microsoft Security FAQ and there was only a very short one
line about the solution you suggest but not explanation as to why you'd do
it, so thanks again for your help, much appreciated.

Ian.
[quoted text clipped - 27 lines]
following the referenced step by step guide to cover all of your bases.
Charlie
Click to expand...
Click to expand...
 
Back
Top