[Bug]: Mono TLS support

[vmato]

Problem description

Mono build seems to lack TLS support:

mono-rt: [ERROR] FATAL UNHANDLED EXCEPTION: Npgsql.NpgsqlException (0x80004005): Exception while performing SSL handshake ---> System.NotSupportedException: TLS Support not available. ---> System.NotSupportedException: TLS Support not available.
at Mono.Net.Security.MonoTlsProviderFactory.CreateDefaultProviderImpl () [0x00033] in <543bc30eab194d8e8dccb6a115e0fc13>:0
at Mono.Net.Security.MonoTlsProviderFactory.InitializeInternal () [0x00023] in <543bc30eab194d8e8dccb6a115e0fc13>:0
--- End of inner exception stack trace ---
at Mono.Net.Security.MonoTlsProviderFactory.InitializeInternal () [0x00037] in <543bc30eab194d8e8dccb6a115e0fc13>:0
at Mono.Net.Security.MonoTlsProviderFactory.GetProviderInternal () [0x00010] in <543bc30eab194d8e8dccb6a115e0fc13>:0
at Mono.Net.Security.MonoTlsProviderFactory.GetProvider () [0x00000] in <543bc30eab194d8e8dccb6a115e0fc13>:0
at Mono.Net.Security.NoReflectionHelper.GetProvider () [0x00000] in <543bc30eab194d8e8dccb6a115e0fc13>:0
at Mono.Security.Interface.MonoTlsProviderFactory.GetProvider () [0x00000] in :0
at System.Net.Security.SslStream.GetProvider () [0x00000] in <543bc30eab194d8e8dccb6a115e0fc13>:0
at System.Net.Security.SslStream..ctor (System.IO.Stream innerStream, System.Boolean leaveInnerStreamOpen, System.Net.Security.RemoteCertificateValidationCallback userCertificateValidationCallback, System.Net.Security.LocalCertificateSelectionCallback userCertificateSelectionCallback) [0x00008] in <543bc30eab194d8e8dccb6a115e0fc13>:0
at System.Net.Security.SslStream..ctor (System.IO.Stream innerStream, System.Boolean leaveInnerStreamOpen, System.Net.Security.RemoteCertificateValidationCallback userCertificateValidationCallback) [0x00000] in <543bc30eab194d8e8dccb6a115e0fc13>:0
at (wrapper remoting-invoke-with-check) System.Net.Security.SslStream..ctor(System.IO.Stream,bool,System.Net.Security.RemoteCertificateValidationCallback)
at Npgsql.Internal.NpgsqlConnector.NegotiateEncryption (Npgsql.SslMode sslMode, Npgsql.Util.NpgsqlTimeout timeout, System.Boolean async, System.Boolean isFirstAttempt) [0x001f5] in <4f7f324cabc54f54bda45f1fe72203f8>:0
at Npgsql.Internal.NpgsqlConnector.NegotiateEncryption (Npgsql.SslMode sslMode, Npgsql.Util.NpgsqlTimeout timeout, System.Boolean async, System.Boolean isFirstAttempt) [0x00320] in <4f7f324cabc54f54bda45f1fe72203f8>:0
at Npgsql.Internal.NpgsqlConnector.RawOpen (Npgsql.SslMode sslMode, Npgsql.Util.NpgsqlTimeout timeout, System.Boolean async, System.Threading.CancellationToken cancellationToken, System.Boolean isFirstAttempt) [0x00445] in <4f7f324cabc54f54bda45f1fe72203f8>:0
at Npgsql.Internal.NpgsqlConnector.g__OpenCore|211_1 (Npgsql.Internal.NpgsqlConnector conn, Npgsql.SslMode sslMode, Npgsql.Util.NpgsqlTimeout timeout, System.Boolean async, System.Threading.CancellationToken cancellationToken, System.Boolean isFirstAttempt) [0x000a9] in <4f7f324cabc54f54bda45f1fe72203f8>:0
at Npgsql.Internal.NpgsqlConnector.Open (Npgsql.Util.NpgsqlTimeout timeout, System.Boolean async, System.Threading.CancellationToken cancellationToken) [0x00369] in <4f7f324cabc54f54bda45f1fe72203f8>:0
at Npgsql.PoolingDataSource.OpenNewConnector (Npgsql.NpgsqlConnection conn, Npgsql.Util.NpgsqlTimeout timeout, System.Boolean async, System.Threading.CancellationToken cancellationToken) [0x00172] in <4f7f324cabc54f54bda45f1fe72203f8>:0
at Npgsql.PoolingDataSource.g__RentAsync|34_0 (Npgsql.NpgsqlConnection conn, Npgsql.Util.NpgsqlTimeout timeout, System.Boolean async, System.Threading.CancellationToken cancellationToken) [0x00097] in <4f7f324cabc54f54bda45f1fe72203f8>:0
at Npgsql.NpgsqlConnection.g__OpenAsync|42_0 (System.Boolean async, System.Threading.CancellationToken cancellationToken) [0x001c6] in <4f7f324cabc54f54bda45f1fe72203f8>:0
at Npgsql.NpgsqlConnection.Open () [0x00012] in <4f7f324cabc54f54bda45f1fe72203f8>:0
at NHibernate.Connection.DriverConnectionProvider.GetConnection (System.String connectionString) [0x00031] in <9f9650bd0a4d48eeaf42465c4f09b8b8>:0
at NHibernate.Connection.ConnectionProvider.GetConnection () [0x00007] in <9f9650bd0a4d48eeaf42465c4f09b8b8>:0
at NHibernate.Tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.Prepare () [0x00000] in <9f9650bd0a4d48eeaf42465c4f09b8b8>:0
at NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.GetReservedWords (NHibernate.Dialect.Dialect dialect, NHibernate.Tool.hbm2ddl.IConnectionHelper connectionHelper) [0x00000] in <9f9650bd0a4d48eeaf42465c4f09b8b8>:0
at NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.UpdateDialectKeywords (NHibernate.Dialect.Dialect dialect, NHibernate.Tool.hbm2ddl.IConnectionHelper connectionHelper) [0x00000] in <9f9650bd0a4d48eeaf42465c4f09b8b8>:0
at NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.Update (NHibernate.Engine.ISessionFactoryImplementor sessionFactory) [0x00011] in <9f9650bd0a4d48eeaf42465c4f09b8b8>:0
at NHibernate.Impl.SessionFactoryI

What steps will reproduce the bug?

Run via mono any .net application with encrypted connection to postgresql

What is the expected behavior?

Encrypted connection to postgresql established

System information

Termux Variables:
TERMUX_EXEC__PROC_SELF_EXE=/data/data/com.termux/files/usr/bin/termux-info
TERMUX_VERSION=googleplay.2025.01.18
TERMUX__USER_ID=0
Packages CPU architecture:
aarch64
Subscribed repositories:
URIs: https://termux.net
Updatable packages:
All packages up to date
termux-tools version:
3.0.8
Android version:
11
Kernel build information:
Linux localhost 4.14.186+ #1 SMP PREEMPT Fri Jun 24 19:54:55 CST 2022 aarch64 Android
LD Variables:
LD_LIBRARY_PATH=
LD_PRELOAD=/data/data/com.termux/files/usr/lib/libtermux-exec.so