I don't want to use filemaker's own login interface, I want to customize one, what should I do?
You can use File Options to auto login and then use your own layout/script to handle login
If you are using a custom login you are building an additional layer of pseudo-security. There have been many, many threads on this and why this is a very bad idea.
1. Make an account that has no rights to see or do anything except the custom login layout.
2. Make your file to auto login on this account and open the custom login layout
3. Use the 'account' script steps
@DavidZakary: I don't see any problems in this method
Suggestion: post a small sample of this method here. See how many can 'get in'.
Sent from miPhone
hbrendel There have been many people that have thought that and have been proven wrong. Ask shblackwell, jormond or wimdecorte about it. They'll set you straight.
hbrendel wrote: @DavidZakary: I don't see any problems in this method
Do a search on this forum for 'ersatz security' and read the arguments.
It makes no sense to me to compromise security in a big way just to pretty up a login dialog.
As has been said often, your strongest security is knowing who is getting into the file. If you let them into the file, half the battle is lost already.
We we don’t sound the warning because we want to be difficult. We have experience with those types of ersatz security methods, and have seen the disasterous results when a user or former employee circumvents the scripted security approach and makes off with, or exposes, a sensitive or company data. The risk is real, and the threat is devastating for a small to medium business. ( information is one if the strongest commodities in the black market )
wimdecorte reminds us regularly, “abscence of evidence is not evidence of abscence”. Just because we individually can’t see how someone can get around it, doesn’t mean it’s not possible.
If you build something thing like this for a client or a company, at the least, be sure you get them to sign a waiver showing you warned them if the danger. And the better move is to refuse to do it. Data integrity is more important than than convenience and ascetic.
A similar post came up a couple of months ago Creating Custom Professional Login Layouts for iOS SDK Apps. (No Default FM UserPass Screen)
Please read this thread and attached PDF.
A Conversation About '2 Factor Authentication'
Check these from DevCon past:
OK, I post this little database.
If someone gets in, please let me know how.
I take it that you are not in agreement that you are incurring more risk than just using the security scheme?
Let's try this, as a narrative describing your login:
Would you agree that #1 is more risky than doing proper authentication *before* there is access to the file?
I agree on the fact that the original security scheme is best.
I just wondered if my suggestion would be OK for those who want to make their own login layout.
I emphasize that I never do it myself. Just for now the finger practice.
hbrendel wrote: I just wondered if my suggestion would be OK for those who want to make their own login layout.
IMHO: an emphatic NO.
Does editing one of the scripts count as "getting in"?
Here you go...
My popcorn hasn't even finished popping.
Thanks DavidZakary. I hadn't even looked at the file yet.
I'd say so. If you can edit a script you can do pretty much anything you want.
I am convinced. As I said: I wouldn't really do it. Just was thinking with the OP.
But really: how did you do it?
David Wikström wrote: Does editing one of the scripts count as "getting in"?
David Wikström wrote:
Or preventing a script from running, running any other script, stopping a script.... if security is going to handled by scripts then any of these actions can break it.
It's not a good idea posting how to hack into a file on a public forum. My lips are sealed and fingers bound to silence.
I still am curious. What about a PM? Is this possible on this forum?
In the videos that Bev posted from DevCon, and some in that long thread I posted, it is discussed.
Retrieving data ...