I was still running against the FB 3 Alpha 1 and just upgraded to
3.0.0.30708 by overwriting my Firebird 3 Alpha 1 install except
firebird.conf and security3.fdb.
Now when using legacy_auth, instead of op_accept, all connection
attempts receive an op_reject.
I had to explicitly set WireCrypt = Disabled to get it to work (setting
this to Enabled had no effect).
I am not sure if this behavior is desirable or correct. Based on the
documentation ("Enabled behavior depends another side requirements. If
both sides set to enabled, connection is encrypted") I'd say that
setting it to Enabled should have been sufficient. The current wire
protocol implementation of Jaybird does not support encryption. I'd
expect not having encryption support would in itself imply 'Disabled'
for the client and if the server then is configured for 'Enabled' then
no encryption should be required (as implied by the documentation).
Mark
--
Mark Rotteveel
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
