Commented by: @dyemanov

The easiest solution might be extending MON$REMOTE_VERSION with flag characters 'C'/'Z' like "show version" does (e.g. P13/C), but this does not look user friendly. Maybe pass such a line internally via DPB but parse it inside the MON handler and decode into different fields?

Commented by: @AlexPeshkoff

Yes, I was thinking about something like this. Separate boolean fields are much better than characters in protocol version.

Commented by: @AlexPeshkoff

In FB3 adding fields to monitoring table means minor ODS change which we avoid in point releases. Therefore only new tag for attachment information call was backported.

Commented by: @pavel-zotov

I've checked fresh 3.0.3 snapshot and found that there is _no_ differences in MON$REMOTE_VERSION
content when parameter 'WireCompression' is changed to true and/or parameter WireCrypt is set to
Required or Enabled.
This field contains 'P15' in any case, w/o suffix(es) 'C/Z'.

Following firebird.conf was used to initialize security3.fdb and check content of mon$attachments (build WI-V3.0.3.32798):

AuthServer = Srp
AuthClient = Srp,Win_Sspi
WireCrypt = Required
WireCompression = true
UserManager = Srp

Then:

echo set list on; select * from mon$attachments where mon$attachment_id = current_connection; show database; | C:\MIX\firebird\fb30\isql -z /:e30

Log of this command:

ISQL Version: WI-V3.0.3.32798 Firebird 3.0
Server version:
WI-V3.0.3.32798 Firebird 3.0
WI-V3.0.3.32798 Firebird 3.0/tcp (csprog)/P15:CZ --------------------------------------- [1]
WI-V3.0.3.32798 Firebird 3.0/tcp (csprog)/P15:CZ
Database: /:e30, User: SYSDBA
SQL>
MON$ATTACHMENT_ID 56
MON$SERVER_PID 2012
MON$STATE 1
MON$ATTACHMENT_NAME e30
MON$USER SYSDBA
MON$ROLE NONE
MON$REMOTE_PROTOCOL TCPv4
MON$REMOTE_ADDRESS 192.168.1.57/1082
MON$REMOTE_PID 2208
MON$CHARACTER_SET_ID 0
MON$TIMESTAMP 2017-08-29 08:08:34.1090
MON$GARBAGE_COLLECTION 1
MON$REMOTE_PROCESS C:\MIX\firebird\fb30\isql.exe
MON$STAT_ID 8
MON$CLIENT_VERSION WI-V3.0.3.32798 Firebird 3.0
MON$REMOTE_VERSION P15 ------------------------------------------------------ [2]
MON$REMOTE_HOST csprog
MON$REMOTE_OS_USER zotov
MON$AUTH_METHOD Srp
MON$SYSTEM_FLAG 0

NB: line [1] _does_ contain:
1) suffix 'Z' when WireCompression= true (and does not in opposite case).
2) suffix 'C' when WireCrypt = Required or Enabled

But line [2] has no such sufixes (of course, I did restart FB after each changing).

Commented by: @AlexPeshkoff

This is as designed in fb3 - one must use Attachment::getInfo() call with new tag (fb_info_conn_flags) in order to obtain compress/crypt info, monitoring tables remain unchanged. Read carefully what I've written: "only new tag for attachment information call was backported".

Commented by: @pavel-zotov

So why 3.0.3 is included into "Fix Version/s" ? We stilll have to use 'show version' rather than query to mon$attachments in order to obtain info about compression/encryption. Author of this ticket asked about mon$-approach, AFAIU..

Commented by: @AlexPeshkoff

Do you think it makes sense to change fix list here and add new ticket for fb3?

Commented by: @pavel-zotov

No, I don't think like this.

Commented by: Sean Leyne (seanleyne)

IMO, this case should be changed to be v4 only, since the requirement/subject described is not met in v3.x.

A separate v3.x & 4.x case "new tag ( fb_info_conn_flags) to getInfo() API call" should be created, since it is only that functionality which is supported in v3.x