Information items isc_info_length and fb_info_crypt_state have same code [CORE5721] #5987
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Modified by: @AlexPeshkoffdescription: During FB3 development bad code was chosen for fb_info_crypt_state information item - it was already in use for special (i.e. used in very specific manner) item isc_info_length. That does not cause troubles when fb_info_crypt_state is not first item in information block. But in cases when this item is first (or single) information block gets corrupted. => During FB3 development bad code was chosen for fb_info_crypt_state information item - it was already in use for special (i.e. used in very specific manner) item isc_info_length. That does not cause troubles when fb_info_crypt_state is not first item in information block. But in cases when this item is first (or single) information block gets corrupted. In case of FB4 there is one more conflict (fb_info_statement_timeout_db vs. isc_info_end) but as long as we still have only alpha release that should not be a problem for anybody. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0.3 [ 10810 ] Fix Version: 4.0 Beta 1 [ 10750 ] |
|
Commented by: @AlexPeshkoff Software using fb_info_crypt_state constant should be recompiled to make it work with release 3.0.3 |
Submitted by: @AlexPeshkoff
During FB3 development bad code was chosen for fb_info_crypt_state information item - it was already in use for special (i.e. used in very specific manner) item isc_info_length. That does not cause troubles when fb_info_crypt_state is not first item in information block. But in cases when this item is first (or single) information block gets corrupted.
In case of FB4 there is one more conflict (fb_info_statement_timeout_db vs. isc_info_end) but as long as we still have only alpha release that should not be a problem for anybody.
Commits: 652d32f dda1fc6
The text was updated successfully, but these errors were encountered: