How secure is a mde ?

  • Thread starter Thread starter TC
  • Start date Start date
T

TC

As you obviously know, there are tools that recover the usernames &
passwords from a workgroup file.

If you distribute >your< workgroup file, and that file has any user(s) in
the Admins group, those tools will break your security.

But if you do >not< distribute your workgroup file - and your end-users run
your secured database using their own workgroup files - then, the workgroup
files that your users are using, >are not< "the workgroup file that was used
to create the database". So the Admins groups of those other workgroup
files, >do not< have any aministrative permissions to your secured database.

So as long as you set it all up correctly, I believe you will be safe from
the tools in question.

Of course, it is pssible to desecure a fully secured database wthout having
any workgroup file of any description. But the knowledge required to do this
is not generally available (AFAIK), and therefore, not worth bothering
about. (And you can't prevent it anyway!)

HTH,
TC
 
Hi,

I've been reading up on mdb cracking in order to make my mdb/e more secure.

There are many mdb/e username/password recovery tools available out there.

I have secured both my mdb fe and be with the same wgf and I do not
distribute the wgf. I know that the admin username and password can be
recovered using these tools but can they reconstruct the wgf and gain admin
privileges for my mdb/e ?
 
Let's see if I got this right...

It's my understanding that if you distribute your Access table without the
workgroup file that was used to secure it, you will not be able to open and
access that secured Access table.

I have Access 2003 and have verified this by renaming the security.mdw file;
it does NOT work then.

Perhaps i am misunderstanding this?

Gary D
 
You say:
If you distribute your Access table without the workgroup file that
was used to secure it, you will not be able to open and access that
secured Access table
Click to expand...

Not so. For example, you could:
- create a new workgroup file;
- secure your database against that workgroup file;
- give the standard Admin user permission to open the database & read that
table, then
- distribute your secured database >without< your workgroup file.

Access securty is a very complex topic. Post some more specific questions, &
we can take it from there :-)

HTH,
TC
 
TC,

I have 2 outstanding issues with security at the moment...

a) I cannot disable the shift-key on application start up,

b) without the security.mdw I cannot start the app.

TIA..

Gary D
 
Hi Gary

I'm getting a bit confused as to where we are at present! Let's start again.
I've snipped the old stuff, & responded as if this was a new thread. Please
advise if I am missing the point about anything you are saying or asking.

==> Disabling the shift key:

You just need to set the AllowBypassKey database property to false. There
are a few tricks to this. The following (UNTESTED) code should be fairly
close. Remember you have to close & reopen the database before the change
will take effect.

const PNAME = "AllowBypassKey"
dim db as database, prp as property
set db = currentdb()
on error resume next
db.properties.delete pname
on error goto 0
set prp = db.createproperty (pname, dbboolean, true)
db.properties.append prp
db.properties.refresh ' not sure if required.
db.properties(pname)=true
set prp = nothing
set db = nothing

However, remember that any user of the Admins group can change that property
back to whatever he/she wants. If the database is unsecured, any standard
Admin user can do that.

==> cannot start app without security.mdw

Not sure what is the question/problem there.

Cheers,
TC


Gary Dikkema said:
TC,

I have 2 outstanding issues with security at the moment...

a) I cannot disable the shift-key on application start up,

b) without the security.mdw I cannot start the app.

TIA..

Gary D
Click to expand...

(snip rest)
 
Back
Top