Back to bug 1394787

Who When What Removed Added
Patrik Kis 2016-11-14 15:01:59 UTC QA Contact qe-baseos-security jaster
Nikolai Kondrashov 2016-11-14 15:26:49 UTC Status NEW MODIFIED
Fixed In Version freeradius-3.0.4-7.el7_3
errata-xmlrpc 2016-11-14 15:40:38 UTC Status MODIFIED ON_QA
Nikolai Kondrashov 2016-11-23 07:18:34 UTC Doc Text Cause:
FreeRADIUS server executable exported several symbols conflicting with symbols defined in libltdl - a libtool helper library.

Consequence:
When FreeRADIUS tried to open a connection to a MSSQL server using rlm_sql_odbc and UnixODBC configured to use FreeTDS, the connection would fail with a message "undefined symbol: get_vtable".

Fix:
The conflicting symbols were renamed.

Result:
Connections to MSSQL servers via rlm_sql_odbc, UnixODBC, and FreeTDS work and no longer produce error message "undefined symbol: get_vtable".
Doc Type If docs needed, set a value Bug Fix
Lenka Kimlickova 2016-12-05 15:36:58 UTC CC lkimlick
Doc Text Cause:
FreeRADIUS server executable exported several symbols conflicting with symbols defined in libltdl - a libtool helper library.

Consequence:
When FreeRADIUS tried to open a connection to a MSSQL server using rlm_sql_odbc and UnixODBC configured to use FreeTDS, the connection would fail with a message "undefined symbol: get_vtable".

Fix:
The conflicting symbols were renamed.

Result:
Connections to MSSQL servers via rlm_sql_odbc, UnixODBC, and FreeTDS work and no longer produce error message "undefined symbol: get_vtable".
* Previously, the FreeRADIUS server exported symbols which were conflicting with symbols defined in the libltdl library. When the FreeRADIUS server tried to open a connection to the MSSQL server using the rlm_sql_odbc interface and UnixODBC configured to use the FreeTDS library, the connection failed with the following error message: "undefined symbol: get_vtable". To fix this bug, conflicting symbols were renamed. As a result, connections to MSSQL servers via rlm_sql_odbc, UnixODBC and FreeTDS
no longer fails.
Lenka Kimlickova 2016-12-13 11:07:50 UTC Doc Text * Previously, the FreeRADIUS server exported symbols which were conflicting with symbols defined in the libltdl library. When the FreeRADIUS server tried to open a connection to the MSSQL server using the rlm_sql_odbc interface and UnixODBC configured to use the FreeTDS library, the connection failed with the following error message: "undefined symbol: get_vtable". To fix this bug, conflicting symbols were renamed. As a result, connections to MSSQL servers via rlm_sql_odbc, UnixODBC and FreeTDS
no longer fails.
* Previously, the freeradius server exported symbols which were conflicting with symbols defined in the libltdl library. When the freeradius server tried to open a connection to the MSSQL server using the rlm_sql_odbc interface and UnixODBC configured to use the FreeTDS library, the connection failed with the following error message: "undefined symbol: get_vtable". To fix this bug, conflicting symbols were renamed. As a result, connections to MSSQL servers via rlm_sql_odbc, UnixODBC and FreeTDS no longer fail.
Lenka Kimlickova 2016-12-13 13:19:43 UTC Doc Text * Previously, the freeradius server exported symbols which were conflicting with symbols defined in the libltdl library. When the freeradius server tried to open a connection to the MSSQL server using the rlm_sql_odbc interface and UnixODBC configured to use the FreeTDS library, the connection failed with the following error message: "undefined symbol: get_vtable". To fix this bug, conflicting symbols were renamed. As a result, connections to MSSQL servers via rlm_sql_odbc, UnixODBC and FreeTDS no longer fail. Previously, the FreeRADIUS server exported symbols that were conflicting with symbols defined in the libltdl library. When the FreeRADIUS server tried to open a connection to the MSSQL server using the rlm_sql_odbc interface and UnixODBC was configured to use the FreeTDS library, the connection failed with the following error message:

"undefined symbol: get_vtable"

This update renames the conflicting symbols. As a result, connections to MSSQL servers no longer fail in the described situation.
Jaroslav Aster 2017-01-04 14:55:57 UTC Status ON_QA VERIFIED
errata-xmlrpc 2017-01-17 12:00:54 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2017-01-17 18:08:39 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2017-01-17 13:08:39 UTC
Alasdair Kergon 2019-03-06 02:36:53 UTC Pool ID 220 238

Back to bug 1394787