On 12/15/2015 04:35 PM, Dimitry Sibiryakov wrote:
> 15.12.2015 13:47, Alex Peshkoff wrote:
>> I will review the code when finish with crypt manager.
> During your finishing, consider following case:
>
> 1) Server has two encrypted database
> 2) First DB is encrypted using CryptPlugin1 +
15.12.2015 13:47, Alex Peshkoff wrote:
> I will review the code when finish with crypt manager.
During your finishing, consider following case:
1) Server has two encrypted database
2) First DB is encrypted using CryptPlugin1 + KeyHolder1
3) Second DB is encrypted using CryptPlugin2 +
On 12/15/2015 05:11 PM, Dimitry Sibiryakov wrote:
> 15.12.2015 14:54, Alex Peshkoff wrote:
>>> During your finishing, consider following case:
1) Server has two encrypted database
2) First DB is encrypted using CryptPlugin1 + KeyHolder1
3) Second DB is encrypted using
15.12.2015 15:49, Alex Peshkoff wrote:
> If DbCryptPlugin::setKey is written badly - will not be called.
DbCryptPlugin2 won't have a chance to call it if KeyHolder1 returned 1.
Ok, I realized that KeyHolderPlugin is to be set in databases.conf only.
--
WBR, SD.
On 12/15/2015 05:29 PM, Dimitry Sibiryakov wrote:
> 15.12.2015 15:21, Alex Peshkoff wrote:
>> It does not matter because CryptKeyCallback::callback(uint dataLength,
>> const void* data, uint bufferLength, void* buffer) does contain "data"
>> (passed from crypt plugin to key holder) parameter.
>
