Antonio:
I want to follow your advice to move from xHarbour to Harbour but Harbour does not support the RDD SIX driver. This RDD allows for transparent record and table encryption. Any suggestions ? Thank you.
FiveTech Support Forums
FiveWin / Harbour / xBase community
Board index FiveWin for Harbour/xHarbour To Antonio:
Gustavo,
If there is no source code for the Six RDD, then I would advice not to use it, to avoid future problems.
What Six functionality do you use that DBFCDX RDD does not support ?
If you just need the encryption, you could encrypt the data before saving it and later decrypt it when you read it,
Antonio:
I use it for the encryption. If I am to encrypt the data myself, instead of being done automatically by the driver, I have to change all numeric, date and logical fields to character types so I can store the encrypted values. This will add a lot of overhead to the app and also will make reporting lot much harder to implement. The SIX libraries in xHarbour are: SDE61.DLL & SDECDX61.DLL
For those of us that develop software for health related business encryption is a must due to HIPAA regulations (patient confidentiality).
Maybe it can be incorporated in a future FW release.
Thank you.
Gustavo,
How do you tell Six to activate the encryption ?
Is it a function call ? What syntax ? thanks
Antonio,
I use to use the six-driver also when I was still using Clipper5.2e + FW
The syntax to use a password was:
When you did for example:
it was automaticly encrypted in the DBF.
With xHarbour + FWH I use now
I use sx_decrypt() to read it again.
Does functions like that are also available with Harbour?
I use to use the six-driver also when I was still using Clipper5.2e + FW
The syntax to use a password was:
USE myfile SHARED new PASSWORD "MyPassword"When you did for example:
repl firma with 'Mijn Firma"it was automaticly encrypted in the DBF.
With xHarbour + FWH I use now
repl firma with sx_encrypt("Mijn Firma","MyPassword")I use sx_decrypt() to read it again.
Does functions like that are also available with Harbour?
Regards,
Marc
FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Marc
FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Marc,
Harbour provides a very good support for Six. In fact we can do:
#include "hbsix.ch"
USE "customer" PASSWORD "mypass"
Sx_DdfEncrypt()
There is some important info about Six bugs that Przemek detected related to memo fields:
https://groups.google.com/forum/#!searchin/harbour-devel/encrypt/harbour-devel/rY8rn70IBI0/d-HoKNhkWQAJ
Harbour provides a very good support for Six. In fact we can do:
#include "hbsix.ch"
USE "customer" PASSWORD "mypass"
Sx_DdfEncrypt()
There is some important info about Six bugs that Przemek detected related to memo fields:
https://groups.google.com/forum/#!searchin/harbour-devel/encrypt/harbour-devel/rY8rn70IBI0/d-HoKNhkWQAJ
When I was adding support for SIX3 encryption to [x]Harbour i blocked
it for tables with memos. I made it intentionally when I found few
serious bugs in SIX3 implementation when tables with memos are encrypted.
I didn't want to replicate them and make [x]Harbour RDDs bug compatible
with SIX3 because SIX3 is corrupting data in some cases.
I left them to the moment when I'll find some spare time to precisely
document SIX3 bugs and differences in new implementation.
Meanwhile I decided to block support for SIX3 encrypted tables with
memos to not have backward compatibility problems with data created
by [x]Harbour RDDs before I'll introduce workarounds for SIX3 bugs.
Antonio:
Marc pointed out the correct syntax via the USE filename VIA SIX PASSWORD "mypassword" (password cannot be greater than 8 chars).
Also this is correct:
When storing data there's nothing new to do:
And the record is stored in encrypted form.
The DOS/Clipper 5.2e Six driver changes the byte that defines the presence or not of a memo field in the DBF header as follows:
1. CHR(6) - encrypted table (no Memo field)
2. CHR(134) - encrypted table with memo file (.DBT) DBFNDX driver CHR(131) - NO encryption
3. CHR(230) - encrypted table with memo file (.SMT) SIXNSX driver CHR(229) - NO encryption
4. CHR(246) - encrypted table with memo file (.FPT) SIXCDX driver CHR(245) - NO encryption
On the link you provided the PRG is using DBFNSX as the driver. On xHarbour the driver is SIX. Also the person is migrating from 16 bit. Under 16 bit you can define the default block size for memo fields. Maybe that's the cause for data corruption. I think that you, as our guru, should test it with a small program.
Thank you Antonio.
Marc pointed out the correct syntax via the USE filename VIA SIX PASSWORD "mypassword" (password cannot be greater than 8 chars).
Also this is correct:
USE filename VIA SIX
Sx_SetPass("mypassword") Â Â // this sets the password for the current workarea, can be used to change the default password for a DBFWhen storing data there's nothing new to do:
REPLACE Field1 WITH cChar, Field2 WITH dDate, etc.And the record is stored in encrypted form.
The DOS/Clipper 5.2e Six driver changes the byte that defines the presence or not of a memo field in the DBF header as follows:
1. CHR(6) - encrypted table (no Memo field)
2. CHR(134) - encrypted table with memo file (.DBT) DBFNDX driver CHR(131) - NO encryption
3. CHR(230) - encrypted table with memo file (.SMT) SIXNSX driver CHR(229) - NO encryption
4. CHR(246) - encrypted table with memo file (.FPT) SIXCDX driver CHR(245) - NO encryption
On the link you provided the PRG is using DBFNSX as the driver. On xHarbour the driver is SIX. Also the person is migrating from 16 bit. Under 16 bit you can define the default block size for memo fields. Maybe that's the cause for data corruption. I think that you, as our guru, should test it with a small program.
Thank you Antonio.
I answered your post on sub-grouping in reports.
Mr Antonio is actively attending to the other post.
Regards
G. N. Rao.
Hyderabad, India
G. N. Rao.
Hyderabad, India
There is also the possibility of subclassing TDatabase to provide automatic encryption/decryption. All we need to do is modify the Load() and Save() methods to do the encryption and decryption. If your program is already using TDatabase, the new class would just be a plugin replacement. Otherwise you would need to convert to using database object syntax, but this could allow you to eliminate lots of code.
As for this requiring more overhead than the SIX driver, I don't think it would. The encryption/decryption is just being done in a different section of code.
Encryption is something all of us need to be thinking about.
Regards,
James
FWH 18.05/xHarbour 1.2.3/BCC7/Windows 10
Gustavo,
What I meant is that as far as I know, you can encrypt/decrypt with any RDD using the syntax, as Harbour seems to support it:
USE "name" VIA "whatever" PASSWORD "mypass"
I have not tested it myself, but thats what I seemed to me
Antonio:
Does the DBUSEAREA() function supports a password parameter ? I use this function to open files instead of the USE command.
Thank you.
HunterEC wrote:Antonio:
Does the DBUSEAREA() function supports a password parameter ? I use this function to open files instead of the USE command.
Thank you.
No, you have to use Sx_SetPass() function.
EMG