4D SQL over SSL: Need separate port numbers.

Tony Ringsmuth (4/9/14 1:09PM)


Tony Ringsmuth (4/9/14 1:09 PM)

My comment is about 4D's lack of separate port numbers for serving SSL
vs
NON-ssl, especially for SQL calls.

It's my understanding that all SSL certificates authenticate to a
specific
domain name, such as MyDomain.com, or MyDb.MyDomain.com. ?And if you
attempt
a connection to an ssl socket via the numeric address, you may have
problems.

So, in the case where you have clients that connect to your database
from an
internal network, and 4D SQL is set to use SSL, how are they doing a
proper
SSL handshake?

I really wish 4D had two ports for SQL, one SSL, the other non-ssl.

(Also the same for the 4D data port)

FYI, I've made a feature request for this ?(from 2011):
http://forums.4d.fr/Post//5290754/1/

--
Tony Ringsmuth
Business Brothers Inc.
763-420-8686

Reply to this message

Summary created 4/9/14 at 4:39PM by Intellex Corporation

Comments welcome at: feedback@intellexcorp.com