I'm a long-time user of DBISAM (since 1998, I think) and I'm considering upgrading to ElevateDB.

I've been using Twofish encryption with DBISAM, and the use of Blowfish in EDB seems like a step backward. So...

1. Are there any plans to use a more modern encryption algorithm with EDB? AES would be great, I think. Or Twofish. The license for Twofish is
the same (I think) as for Blowfish.

2. If not, how difficult is it to modify EDB source to replace the encryption component used? I hate modifying the source, but if I have to, I'll pay
the extra and just get it done.

Thanks for your help!

-David

David,

<< 1. Are there any plans to use a more modern encryption algorithm with
EDB? AES would be great, I think. Or Twofish. The license for Twofish is the
same (I think) as for Blowfish. >>

Not at this time, no.

<< 2. If not, how difficult is it to modify EDB source to replace the
encryption component used? I hate modifying the source, but if I have to,
I'll pay the extra and just get it done. >>

Well, you have to take into account the managed code aspect of things if you
want to use it in .NET, but other than that it is all pretty self-evident.
The encryption code is in the edbcommon.pas unit.

--
Tim Young
Elevate Software
www.elevatesoft.com

David Michael wrote:
> I'm a long-time user of DBISAM (since 1998, I think) and I'm considering upgrading to ElevateDB.
>
> I've been using Twofish encryption with DBISAM, and the use of Blowfish in EDB seems like a step backward. So...
>
> 1. Are there any plans to use a more modern encryption algorithm with EDB? AES would be great, I think. Or Twofish. The license for Twofish is
> the same (I think) as for Blowfish.
>
> 2. If not, how difficult is it to modify EDB source to replace the encryption component used? I hate modifying the source, but if I have to, I'll pay
> the extra and just get it done.
>
> Thanks for your help!
>
> -David
>

David,
     I think even if you change the encryption algorithm, you're still
limited to an 8 byte symmetric block algorithm (64 bit). You can't
change it to say 256 bit AES (like what SQLite has-I'm not necessarily
recommending that database).

Dave

Dave,

<< I think even if you change the encryption algorithm, you're still limited
to an 8 byte symmetric block algorithm (64 bit). You can't change it to say
256 bit AES (like what SQLite has-I'm not necessarily recommending that
database). >>

You could, but you'd have to change the:

  IO_ALIGN_SIZE = 8;

constant in edbconfig.pas to:

  IO_ALIGN_SIZE = 32;

In order to have everything work correctly.  There is also such a constant
in edbcommon.pas that deals with the same type of alignment issue, but that
is a self-evident change once you start messing with the encryption code.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks for the information!

-David