|
Use FIPS-approved encryption implementations for communication encryption.
Separately licensed component requiredECC encryption and FIPS-certified encryption require a separate license. All strong encryption technologies are subject to export regulations. |
fips={ y | n }
HTTPS, TLS
No
FIPS is only supported for RSA encryption.
Non-FIPS clients can connect to FIPS servers and vice versa.
The following example sets up FIPS-approved RSA encryption for a TCP/IP protocol. This requires setup on the server and client. Each command must be written on one line.
On the server, the implementation is:
mlsrv10
-c "dsn=SQL Anywhere 10 Demo;uid=DBA;pwd=sql"
-x tls(
port=9999;
tls_type=rsa;
fips=y;
certificate=c:\sa10\win32\rsaserver.crt;
certificate_password=test )
On a SQL Anywhere client, the implementation is:
dbmlsync -e
"CommunicationType=tls;
CommunicationAddress=
'tls_type=rsa;
fips=y;
trusted_certificates=\rsaroot.crt;
certificate_name=RSA Server'"
In an UltraLite application written in embedded SQL in C or C++, the implementation is:
info.stream = "tls";
info.stream_parms = TEXT(
"tls_type=rsa;
fips=y;
trusted_certificates=\rsaroot.crt;
certificate_name=RSA Server");