Hmm, well it appears as though I am using RijndaelAES encryption, which, judging from the fascinating Wikipedia pages (MD5, AES), is considered much more secure than MD5. I wonder if our little small business cares about having bullet-proof login passwords, but it would feel wrong to downgrade to a less secure encryption standard.
That custom function is a good suggestion though. I don't like having to resort to a plugin if one can do things natively in FileMaker.
That custom MD5 function just gave me an idea… I could probably modify my standard opener file to allow the FM Go user to store their login information locally, in MD5. Then when this is all set and stored, I could pass the username + password as script parameters to the startup script on the server, authenticating directly through normal FileMaker methods (ignoring my server-stored encrypted password altogether).
So that would allow me to continue to distribute and maintain a single version of an opener file, the user would have the option to store their username + password, and this would all be done with relative security. If they lose their device, we can easily change the password on the server side and the thief wouldn't be able to login.
I could even enable this for desktop clients who have their own computer (like me). I like this idea…