db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sunitha Kambhampati <skam...@Yngvi.Org>
Subject Re: Regarding Derby42 : Do not store the encryption key length and the encryption block size in service.properties:
Date Thu, 21 Oct 2004 16:50:39 GMT

> block size is an inherent value of the
>algorithm, thus if that is true, Derby does not need to store the block
>size at all. Just fetch it each time from the Cipher.getBlockSize() method.
Thanks Jan and Dan for your input on encryption block size.

This fix  for Derby46  removes code to store encryption block size in 
service.properties and instead obtains the encryption block size from 
Cipher.getBlockSize() for padding purposes.

Although with this fix, there are no upgrade issues;  there is a problem 
with downgrade of a database created with version that has this fix.

If we take this fix, what this means is-
1) No upgrade problems, so a database *created* with previous versions ( 
ie before this fix) will work OK with this fix.

2) Downgrade problem:  Create a database with version that has this fix 
and the encryption block size will not be stored in service.properties. 
But a previous engine expects to  read the encryption block size from 
the service.properties and if it doesnt find the encryption block size 
property, defaults to 8 bytes and uses this to do appropriate padding. 
Thus a database created with this fix will not necessarily work with 
previous engines.


View raw message