> 13.04.2018 17:01, Mark Rotteveel wrote:
> > Let me rephrase: exactly what causes Firebird to perform a callback to the
> > client, and
> > what must a KeyHolderPlugin do to make sure no callback is performed.
>
>Firebird calls client callback when key holder in keyCallback() calls the
>
13.04.2018 17:01, Mark Rotteveel wrote:
Let me rephrase: exactly what causes Firebird to perform a callback to the client, and
what must a KeyHolderPlugin do to make sure no callback is performed.
Firebird calls client callback when key holder in keyCallback() calls the callback
received in
On 13-4-2018 16:56, Dimitry Sibiryakov wrote:
13.04.2018 16:47, Mark Rotteveel wrote:
The person reporting the problem indicates a different plugin did not
have this problem, which would indicate there is a way to suppress the
callback. What does the plugin need to do to not perform a
13.04.2018 16:47, Mark Rotteveel wrote:
The person reporting the problem indicates a different plugin did not have this problem,
which would indicate there is a way to suppress the callback. What does the plugin need to
do to not perform a callback?
It must be a plugin that never call the
I'm currently looking at a problem with Jaybird (which doesn't support
the callback) and a plugin that performs the callback when I think it
shouldn't. If I modify Jaybird to send an empty buffer in response, it
works fine.
The person reporting the problem indicates a different plugin did not
> How does the protocol for the database encryption callback work? If I
> look at the implementation in Firebird ADO.net, it just tries and keep
> sending the same key in a while loop until Firebird responds with
> something other than op_crypt_key_callback, which seems a bit weird.
It does.
