Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Information items isc_info_length and fb_info_crypt_state have same code [CORE5721] #5987

Closed
firebird-issue-importer opened this issue Jan 22, 2018 · 5 comments

Comments

@firebird-issue-importer

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

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jan 22, 2018

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jan 22, 2018

Modified by: @AlexPeshkoff

description: 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.

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jan 22, 2018

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0.3 [ 10810 ]

Fix Version: 4.0 Beta 1 [ 10750 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jan 22, 2018

Commented by: @AlexPeshkoff

Software using fb_info_crypt_state constant should be recompiled to make it work with release 3.0.3

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jan 22, 2018

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: No test => Deferred

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment