If any of the above are true, then its quite likely that the same actors involved will also attempt to discover your passwords or any other confidential content passing over your network.

an untrusted device (or malicious user) connects to your network.

a weakly-encrypted wireless connection (e.g., WEP or WPA1).

But even for these networks, one or more of the following are possibilities: But these issues can seem esoteric for those who never access their servers remotely and where their servers are only accessible on the LAN.

greatly reduce packet sniffing/snoopingįor situations where a server is on a public (Internet) IP these goals are central.

prevent packet injection or forged content.prevent MITM (man-in-the-middle) attacks.users can trust that they are connecting to the correct server.Using SSL-based connections is a very basic step you can use to help with the following goals: Network security is a non-trivial subject that can seem overwhelming, but hopefully anyone deploying or managing a server is at least somewhat interested in their system’s security. This is after all the heart of the topic. Definitely check out the references and links if you’d like more information. In an attempt to be as brief as possible, I’ll be mainly discussing server configuration issues, and leaving out many smaller details. But where do they come into play, and how might this affect your deployments?īecause of the amount of terminology involved and the wide scope that SSL (Secure Socket Layer) connections cover, we should first go over some basics of typical SSL connections and the certificates needed to use them. Starting with version 15 however, FileMaker introduced a number of security changes, in handling SSL and certificates, on both the server and the clients. SSL certificates are a very common way to secure client/server network connections, and the FileMaker platform has made use of them for many years.

Filemaker pro server 15 ports