Jump to content
Server Maintenance This Week. ×

TA14-098A: OpenSSL 'Heartbleed' vulnerability


This topic is 3668 days old. Please don't post here. Open a new topic instead.

Recommended Posts

OpenSSL was installed with FileMaker Server.  Will FileMaker be issuing an updater to OpenSSL?  If so, will it go back to earlier versions?  If not, will the publicly available OpenSSL updater update the FileMaker installed version?

Link to comment
Share on other sites

Unfortunately, I updated and now FM clients can no longer see hosted databases with the SSL connections enabled.  Here's what I posted in the FileMaker Support forums; maybe someone here has seen this or has an idea on how to resolve it?

 

I've been running FMS 13v1 successfully for awhile on OS X 10.9 (now at 10.9.2, fully patched), with "Require Secure Connections" checkmarked in the Database Server section and a commercial SSL cert from GoDaddy installed with fmsadmin.
 
I applied the first "emergency fix" that FMI put out, which involved copying files to certain places on the server.  That also worked fine.
 
I saw that they released a real updater and applied that tonight....and that seems to have broken something.  Now if "Require Secure Connections" is checkmarked, hosted databases do not appear in the FM client (even a client running on the same machine as the server).  The server shows up under "Local Hosts", but no databases appear.
 
All databases show as opened and Normal on the server, and if I uncheck "Require Secure Connections" and restart the server, all the databases appear just fine.
 
Note that I'm not talking about Web Services:  this is the core fmnet protocol functionality.  However, it also is broken (The server test page for both WebDirect and PHP fail) when "Require Secure Connections" is enabled in the core server, and it starts working again when "Require Secure Connections" is unchecked.
 
At the suggestion of one of the moderators on the FileMaker Discussion Forums, I generated a new key with the CERTIFICATE command, revoked and re-keyed the cert, then imported it again, rebooted the box, but that didn't fix the issue either.
 
Is anyone else seeing this?  Any ideas on a fix?  I wouldn't want to run my server without SSL security for very long.
Link to comment
Share on other sites

John, check to see if your certificate is supported by FMS. The behavior you see, is similar to some tests I did with a wildcard certificate, which is not supported by FMS13.

I am not sure, if the list of supported certificates has changed for this v1a update.

 

Another thing to notice, is that you should anyways, re-issue the certificate for security measures.

That might bring back the databases in SSL mode.

 

You can find the list of supported certificates here:

http://help.filemaker.com/app/answers/detail/a_id/11413/~/list-of-supported-ssl-certificate-vendors-and-ssl-certificate-types-for

Link to comment
Share on other sites

This topic is 3668 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.