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
Originally posted by pettersillander May 2, 2024
Could implemeting (maybe optional?) encrypted connection between client and server help to ease adoption of SQLpage in diverse environments?
Quite a few networks (even closed) are encrypted connections only nowadays. As all the SQLpage supported dbms's support TLS natively it's seems rather cumbersome to use a tunnel for encryption.
Just wondering this after configuring SQLpage in existing environments...
The text was updated successfully, but these errors were encountered:
Discussed in #299
Originally posted by pettersillander May 2, 2024
Could implemeting (maybe optional?) encrypted connection between client and server help to ease adoption of SQLpage in diverse environments?
Quite a few networks (even closed) are encrypted connections only nowadays. As all the SQLpage supported dbms's support TLS natively it's seems rather cumbersome to use a tunnel for encryption.
Just wondering this after configuring SQLpage in existing environments...
The text was updated successfully, but these errors were encountered: