You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tomcrypt library has a kind of "unstable" API. Default built of it does not include thread safety option - i.e. some global data structures are not protected by mutex. That's not good for us itself but what is worse - if firebird binary expects shared tomcrypt library built with thread safety ON but actually it was built (by third-party) with OFF different size of data structures in API calls causes segfault when working (for example) with PRNGs.
Therefore we include tomcrypt library in 'universal' binaries for linux but it can be easily overwritten with system package. Problematic library should be placed in a way that it will be always used by our binaries instead system one.
Private libtomcrypt.so.1 moved from ${FIREBIRD_INSTALL}/lib/.tm to ${FIREBIRD_INSTALL}/lib.
No system-wide symlink on private libtmocrypt.
Currently installation checked on CentOS 7 (ncurses5, tommath0) and CentOS 8 (ncurses6, tommath1).
"Well done" :)
Submitted by: Basil A. Sidorov (basid)
Tomcrypt library has a kind of "unstable" API. Default built of it does not include thread safety option - i.e. some global data structures are not protected by mutex. That's not good for us itself but what is worse - if firebird binary expects shared tomcrypt library built with thread safety ON but actually it was built (by third-party) with OFF different size of data structures in API calls causes segfault when working (for example) with PRNGs.
Therefore we include tomcrypt library in 'universal' binaries for linux but it can be easily overwritten with system package. Problematic library should be placed in a way that it will be always used by our binaries instead system one.
Commits: 1fbc1d0
The text was updated successfully, but these errors were encountered: