Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 12/04/2010 in Blog Comments

  1. Thank you, Josh, for reconstructing this important thread and for posting it. What did we learn from this episode? Here is a summary: · What we call something matters. Calling a process 2 Factor Authentication does not make it so. · Manipulating the business logic layer, i.e. scripts, of the FileMaker Platform in an attempt to create additional security features requires an in-depth and nuanced understanding of how that layer performs, particularly in relation to external API’s or under the influence of such API’s. · More likely than no
    3 points
  2. My 15mins of fame! Let me help you sync accounting data to QBO from FileMaker.
    1 point
  3. This is no accurate. How they handle the processing is VERY different. Tools other than FMPerception: Run DDR Import DDR ( ours takes 10-12 hours, processing and analysis happens here ) Search for some stuff. Make changes. Export DDR Import DDR ( 10-12 hours, processing and analysis happens here ) Search for some stuff. Roughly getting updated info every other day. FMPerception: Run DDR Open FMPerception ( < 7 secs ) Search for some stuff ( the processing and analysis happens now ). Make changes to data
    1 point
  4. THANKS, very nice, was about to make my own, but this is awesome
    1 point
  5. I think another likely scenario, in addition to a "test" file, is when a user who has sufficient access, or an administrator who doesn't realize the risk, puts up a file that is not part of a secure solution... in which they don't consider the data to be critical. Honestly, I have put many such files on servers in the past... Thanks for identifying this issue, Steven.
    1 point
  6. I agree that any additional measures a developer takes are unlikely to increase the security of a file. I don't think any serious developer adds security features with this expectation. They are usually added because the FileMaker security model is not suited to all client requirements. Take the Role-Based-Access-Control model (RBAC), for example, which has grown in popularity in the last few years. It isn't possible to implement RBAC using the default FileMaker Pro security features because users can only be assigned a single privilege set, which torpedoes the inheritance concept that RBAC re
    1 point
  7. Thanks for the post, Steven. Do you know if enabling Encryption At Rest will have any performance impacts?
    1 point
  8. >> They are incorrect; yet, they believe that they are correct, and they are unaware of their errors. That reminds me of that Mark Twain quote: It ain't what you don't know that gets you into trouble. It's what you know for sure that just ain't so.
    1 point
  9. Thanks Steven and Wim.... Very useful articles while working with FMS 12.
    1 point
  10. Yes you do. FMS will look in all the nodes set up in the Directory Utility for authentication. Sounds like you already have the know-how in house if the IT people bind the workstations to the AD. Otherwise a google on "10.6 bind active directory" will get you some tutorials.
    1 point
This leaderboard is set to Los Angeles/GMT-07:00
×
×
  • Create New...

Important Information

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