Foxpro 2.6 on Win 10 DBF Security Question 1

[jlg13]

Hello! It has been a while since i posted on this forum but it has always been very helpful!

As many of you know, DBF files are not very secure. I am trying to figure out a way to keep the data within the DBFs protected. One idea I had was to add restrictions/permissions to the folder where the DBF files are housed. This would keep people from the ability to access the folder to copy the PDFs or use a DBF tool to read the contents (I think).

If this is possible, then my concern is whether the program files (*.prg) will be able to access the dbf without error. If not, could the prg pass the necessary security info to open the DBFs in that the folder? This is just an idea I had so perhaps there is a completely better way to provide this security?

Thanks!
Joe

 

[Scott24x7]

If you put that restriction on at Win10, then at run time, it will still be in place. If the user doesn't have access to the directory, neither will FoxPro.


Best Regards,
Scott
ATS, CDCE, CTIA, CTDC

"Everything should be made as simple as possible, and no simpler."

 

[Olaf Doschke]

It's as Scott says, there is no way to give a certain prg or fxp or exe file access permissions the user himself does not have.
You could Impersonate an application user and only give file permission to that user - the big downside is, once you have a table prompt or any file open dialog, users can get at files again, as the app has all permissions, so this only is an option, if your application really is very tight on any options like that.

Your best two options are encrypting DBFs with Cryptor, as that has the main necessary feature to only unencrypt files for a certain EXE or you stop using DBFs and use a server database with the capabiliities to grant or deny permissions based on logins or roles.

Bye, Olaf.

 

[jlg13]

Thanks Scott, Olaf,

I will investigate Cryptor! Sounds like that is exactly what I need. If you have any other helpful guidance, please pass it along.

Much appreciated guys,

Joe

 

[Olaf Doschke]

FYI, Cryptor is nothing you can apply from outside, if you don't have source code you will not be able to use it, the application code has to register itself with Cryptor and the DBFs it wants to use.
If you run a software you didn't develop yourself, ther's no option other than file acces permissions and thus no way to handle access from within the application any different than from outside.

Bye, Olaf.

 

[jlg13]

Fortunately my dad is the architect of the 30 PRGs that interact with each other. So he codes the PRG and then creates the FXP.

 

[Olaf Doschke]

That's good news, then cryptor is an option. I wonder where you could get it from, all foxpro related shops have closed up and I wonder if there is a legacy version, but you may at the same time also upgrade to VFP9.

http://www.xitech-europe.co.uk/cryptor5.php

This could be a starting point, but before you place any order mail them. This site like many foxpro sites is more like a desert with tumbleweed boincing through it.

Bye, Olaf.

 

[jlg13]

I looked up Cryptor and there are various cryptor names, so calling it a ransomware app. Do you have the legit download link? Is there a website with software documentation? Sorry for ignorance.

Joe

 

[jlg13]

Well we passed on the upgrade to Visual Foxpro when we probably should have upgraded so I doubt we would be a good candidate to do it now. We are just going to keep looking for coconut water among the tumbleweeds for now I'll let you know how this pans out. Thanks again!

 

[Olaf Doschke]

Well, but Cryptor's description tells it's god for VFP down to version5. Many other software is mentioned, but I think you need the COM interop capability.
Let's see how it evolves, first step would be to get it at all.

In the end it always pays to invest in time.

Bye, Olaf.