Overall Security???

  • Thread starter Dimitrios Tanis
  • Start date
D

Dimitrios Tanis

I am currently developing a distributed database application (database side
is complete in sql 2000 DE) and I am in the verge of developing the FE. What
I want to know is if there is a way (which developing environment) to use to
adequately protect both the BE (sql) and FE (?) from being seen by others,
aka secure theft of both db BE and FE structure and containing data.
As I know sql is profoundly one of the secure ways but how do I 'encrypt' my
db structure from being seen by others? (uncluding the customers that buy
the program)????
Currently for the FE I have the following enviroments in mind:
1. VB .NET
2. Access
3. FoxPro
What should I choose.

Any help of reference is mostly appreciated.

Thanx in advance.
 
A

Arvin Meyer [MVP]

The first and third have executables which cannot be read. The second
(Access) has a tokenized file called an MDE which also cannot be read. Even
with a hex editor, very little if any of the 3 formats can be read.

As far as data security, unauthorized people can be excluded using the file
system. The data (BE) structure is usually visible to anyone with the
administrative rights to install. Access databases can be protected by
creating a BE with no permissions to anyone except an owner. MSDE databases
are protected with SQL-Server security.

Security is a multi-faceted property and requires not only good data
practices, but also limiting access to that data with physical locks and
firewalls.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 
C

Chris Mills

Have you perused the last month's posts in this newsgroup (security)?

Your question is sufficiently general-purpose that I suggest you do, then come
back with specifics.

Chris
 
A

Anders

Security will reside in the SQL Server database and in the user priviledges
the system administrator sets up. It will not depend on VB.Net, Access or
Visual FoxPro. Choose whatever development tool for the user interface you
prefer. It's a different decision.
-Anders
 
Ä

ÄߺìÒ«

Ϊʲô°¡
Anders said:
Security will reside in the SQL Server database and in the user priviledges
the system administrator sets up. It will not depend on VB.Net, Access or
Visual FoxPro. Choose whatever development tool for the user interface you
prefer. It's a different decision.
-Anders
 
A

aaron.kempf

yeah.. i think that it's ridiculous in this day and age to have any
confidence in MDB security.

use an ACCESS DATA PROJECT man it rocks
 
T

TC

yeah.. i think that it's ridiculous in this day and age to have any
confidence in MDB security.

The next version (Access 12) uses Office Encryption. This will change
the story completely.

TC
 
D

Dan Freeman

TC said:
The next version (Access 12) uses Office Encryption. This will change
the story completely.

Whether for better or worse remains to be seen. <g>
 
A

aaron.kempf

yeah.. i just dont understand why they're always changing shit instead
of fixing shit

i just dont think that MDB is safe for any data anywhere and I think
that you kids would be better off writing in ADP than in MDB.
 
T

TC

Given that you don't have the slightest idea of my customer base, or
their needs, I will file your suggestion for further consideration some
time in the next millenium.

TC
 
A

aaron.kempf

i just know that spyware and malware is a lot bigger threat than you
guys could possibly comprehend.

i did proxy log analysis at microsoft- i know that the largest
companies in the world can't deal with this problem

and you guys are just giving them a blank check when you use mdb
 
A

aaron.kempf

I got fired TWICE. for complaing.

I worked in a dept called 'MSN Quality of Service' and those drunk
monkeys couldn't keep hotmail up reliably for 10 minutes

and SQL authentication?

I call for the immediate arrest of Bill Gates and other Sr Management
for TREASON. putting our troops at risk shit; they should all be
rounded up and shot on live TV.

I mean-- SQL authentication is used all over the world; and in SQL 2000
and SQL 2005; it can't stand up to a simple dictionary attack.

RIGHT???

-Aaron
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top