I have a desktop app that syncs with a database at
http://XXX.XXX.XX.XX:5984. I've enabled all server side security I available to me and I want to also set the desktop app to sync via SSL
https://XXX.XXX.XX.XX:6984 so that if a user has the app on their laptop and is syncing using a public connection, their data is encrypted.
I set it up with a self signed certificate on the server and tested on the command line with the following but I get this notice:
curl https://XXX.XX.XX.XXX:6984 More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option.
Since I'm the owner of the server and it's a direct ip to a port. Will turning off the verification of the cert (
curl -k https://XXX.XX.XX.XXX:6984) mean my data will be sent unencrypted?