Does anyone have any suggestions on how to keep your
database tables safe from anyone just going into a
database editor and "playing" with the data?
It hasn't happened yet but with more & more people
becoming knowledgable in the use of computers, what can be
done to prevent the above. We have tried "Hiding" the
directory where the data resides under Novell but it
causes some problems with FoxPro trying to locate files.
Any suggestions?
Thanks in advance!
Mike
"Michael" <mich...@altavista.com> wrote in message
news:523d01c194a0$bfb14ab0$3aef2ecf@TKMSFTNGXA09...
Anybody get this to work yet?
I would assume that the code would look something like this:
If TYPE("myApplication") <> "O"
RETU .F.
ENDIF
"Michael" <mich...@altavista.com> wrote in message
news:523d01c194a0$bfb14ab0$3aef2ecf@TKMSFTNGXA09...
Well, you know, absolute security cost is infinite ... it's a dialectic. :o((((
But there are some ways to approach it.
First, it is essential to determine a security strategy : cost vs rate service, or readibility vs access time, for example.
The database organization might be based on this strategy.
I mean, it's obvious that sentitive data splitted to differents file, with a master file exclusively containing pointers,
is more difficult to read or interpret than a database conceived like an excel sheet.
Furthermore, another level is online data encryption.
But it requires a high-level analysis and good skill to code concurrent database accesses.
Could you specify the way you aim your project ?
Gérard.
"Michael" <mich...@altavista.com> a écrit dans le message news: 523d01c194a0$bfb14ab0$3aef2ecf@TKMSFTNGXA09...
One place is running two large applications. About 100
fulltime/parttime employees. The apps are written in vfp6
and are extremely stable. The use NT terminal server to
for gaining access at there other loactions. The files are
stored in .DBF tables and can easily be read/modified by
anyone who knows how. One concern they are now having is
that someone can just modify the tables, delete records...
We were wondering if there is a "quick fix" to prevent
anyone from doing so. The applications were just re-
written over the past 2 years from fpd 2.6. The tables
were just converted to vfp 6.0 format.
--
Craig Berntson
MCSD, Visual FoxPro MVP
www.craigberntson.com
Salt Lake City Fox User Group
www.slcfox.org
Visit FoxCentral www.foxcentral.net
---
"Michael" <mich...@altavista.com> wrote in message
news:523d01c194a0$bfb14ab0$3aef2ecf@TKMSFTNGXA09...
--
Craig Berntson
MCSD, Visual FoxPro MVP
www.craigberntson.com
Salt Lake City Fox User Group
www.slcfox.org
Visit FoxCentral www.foxcentral.net
---
"Tod McKenna" <t...@opaldata.com> wrote in message
news:#xtoflKlBHA.2416@tkmsftngp04...
Gérard.
"Craig Berntson" <cr...@craigberntson.com> a écrit dans le message news: upV6RiLlBHA.1516@tkmsftngp07...
If you're using an NT/2K server and NT/2K/XP workstations, you could put the
files in a shared directory but allow access only to admins and say a user
'foxprouser'. Then when your users run the app on the workstation you could
do
net use x: \\myserver\mydatadir password PASSWORD /USER:foxprouser
.. or it's equivalent using Windows API commands. Then remove the
redirection when they exit the app. That would keep you safe unless they
were actually in the app, at which point they could alt-tab out and create
chaos on drive x:.
"Michael" <mich...@altavista.com> wrote in message
news:523d01c194a0$bfb14ab0$3aef2ecf@TKMSFTNGXA09...
Regards,
Mike
The best way to do this is:
Write a short encryption procedure.
e.g.
say you wanted to store passwords in a table.
encrypt the password before storing it.
then when you want to access it use the same algorithm to unencrypt the
password.
for example use asci values *122/4
you will no the key but no one else will
"Michael" <mich...@altavista.com> wrote in message
news:523d01c194a0$bfb14ab0$3aef2ecf@TKMSFTNGXA09...
--
Craig Berntson
MCSD, Visual FoxPro MVP
www.craigberntson.com
Salt Lake City Fox User Group
www.slcfox.org
Visit FoxCentral www.foxcentral.net
---
"MAppell917" <mappe...@aol.com> wrote in message
news:20020104052945...@mb-cu.aol.com...
\\ntserver\DataFiles$\Appdir
This way, the directory is hidden from the user, unless he knows the exact
name of the directory.
And no smart fella has messed up my tables so far!
regards
NvdK
more info on:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q90929
"Michael" <mich...@altavista.com> wrote in message
news:617201c19602$32e5da70$35ef2ecf@TKMSFTNGXA11...
> I will try that. Thanks!!!
Michael's post is really what i have been trying to convey in my post (dbc
security 12/31/01 12:47 AM) and i'm interesting in your answer.
Q: Can i apply your solution if i use a vfp native database in an NT server
*but* access it through an odbc connection? I yes, how can i do that?
TIA.
Willianto