Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

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

Recommended Posts

Posted

Hello,

When developing an FM-based runtime application, preventing access to the database structure and scripts is an essential prerequisite to me.

Password based protection doesn't seem to be very effective, since the passwords can be figured out if the user has the know-how.

My question is: by permanently removing adm access from files, when creating the runtime application, can I be 100% sure that nobody, no matter his/her skill level, will have access to the runtime application database structure and scripts?

Are there any other valid alternatives?

natursalus

Posted

My question is: by permanently removing adm access from files, when creating the runtime application, can I be 100% sure that nobody, no matter his/her skill level, will have access to the runtime application database structure and scripts?

No. You can make it more difficult, but not impossible.

Steven

Posted

Hello,

Password based protection doesn't seem to be very effective, since the passwords can be figured out if the user has the know-how.

Filemaker close the login window after 5 error attempts? I think this prevents the brute force method, or reduce the risk.

But, there are other methods like lostpassword.

Posted

A brute force attack likely would not use the login window UI. Removing [Full Access] Accounts with the Developer Tool usually thwarts most of the password crackers.

Steven

This topic is 4719 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.