copy protection

[tentenths]

I could not find a "newbie" section so I apologize in advance.

If I designed a front end for a specific industry could I lock down the front end so it could not be copied and used by a competitor or have a company purchase one license of my "custom software" and open it up and modify it for themselves???

I'm sure the database can be locked down tight but not shure about the UI.

tia

Morgan

[Fenton]

First, I moved this thread to the Security forum, instead of the Sample Files, which is kind of a special forum.

I don't really know what you mean by the "database" as opposed to the "UI", as they're closely tied in FileMaker, unless you're using the separation of data method; but even so.

One way to be darn sure no one can "modify" your database is to remove the Full Access privilege set from it before distributing. This requires FileMaker Pro Advanced. But it is, I think, the only way to be sure. It does however make that copy no longer modifiable, by anyone. So, 1. Do it on a copy!, and 2. Do not expect to make modifications afterwards. In other words, if a client needs modifications you will have to import all their data to a modifiable version, then remove access again.

If Full Access has been removed, it is not that difficult to personalize a file, for one particular client; by putting their company name for example, so that it prints on all their documents they'd want to send out. The trouble would be that if they change their name, you wouldn't be able to modify it for them either; unless you imported all their data into modifiable version. You could charge for this. I would be up front about it, so there's no hard feelings later.

I think it comes down to the fact that any file which has not had Full Access removed can be cracked. I'm not a security expert, but I've never heard different.

[tentenths]

Hi Fenton...thanks for the response. I was not clear.

Let's say I design a really nice user interface to route messengers for delivering small packages. It has contacts, scheduling, billing and tracking. I put alot of time in to this and want to sell it for other messenger companies to use.

Can I make a 30 day demo that will expire?

Can I make this application copy protected so they cant give it away and must buy a license.

The software I want to sell would have an empty database and the customer will add the data..so I'm not trying to protect the data. I want to protect the application and user interface???

tia

Morgan

[Fenton]

That's what I was talking about, protecting the structure. Removing the Full Access password will protect the structure. The database will still work exactly the same, as far as data goes; but you will not be able to fix, copy or even see the structure; not anyone, not even you. So obviously only do it on a copy.

As far as a 30 day demo, that would a separate thing, more of a test. A simple thing like a record-level access restriction, in Accounts and Privileges could stop them creating new records or editing. Personally I think that's enough of a limitation. I don't think you really need to shut down the database entirely, blocking them from any data they've entered.

You would need a registration mechanism, which I'm not going into, as it would be a long discussion. The end result is a flag (Boolean) that they've registered.

Each privilege set could have a restriction, in the Records area, Create:

RegistrationFlag = 1 or ( Get ( CurrentDate ) < Date1stOpened + 31 )

Same for Edit.

You would script setting Date1stOpened when they first opened it (duh -). Since you've removed Full Access privileges there is nothing they can do to change any of this. Other than maybe back the date on their computer; which I doubt anyone in their right mind would do.

You'll want to read more about registrations schemas.

[tentenths]

Fenton....you are a power user and most of what you posted is above me. About 5 years ago I was able to make a simple filemaker database with a nice front end for cataloging media for a video editing company...so that's the only experience I have.

What I'm investigating is the ability to market a filemaker application and protect it's structure and let the customer protect the database.

You wrote: "you will not be able to fix, copy or even see the structure; not anyone, not even you. So obviously only do it on a copy."

Does this mean I can make a production working version and then make a copy and fully protect that copy and sell that one to the customer and they can fully use all the data entry fields and calculations and functionality built in but would not be able to modify or copy it to use on a 2nd computer?

What drove me to this is some overpriced software running on foxpro (pc only) that is very not slick and very primitive. After a week of using it, I kept thinking about filemaker and how it could probably do a better job.

I guess in summary...do many people sell the custom applications for specific businesses or do you just sell your services as the designer?...I would prefer to sell the software product.

thanks again...

Morgan

[Vaughan]

"Does this mean I can make a production working version and then make a copy and fully protect that copy and sell that one to the customer and they can fully use all the data entry fields and calculations and functionality built in but would not be able to modify or copy it to use on a 2nd computer?"

The "protection" prevents somebody from modifying the system's layouts, data structure and scripts.

There is nothing to stop them from copying it and using it on a second computer, at least nothing native in FileMaker Pro.

Some people have developed techniques that record the hard disk serial number or MAC address, but this may involve plug-ins for OS-level scripts. There are other commercial solutions that modify the executable (for Windows runtimes) that tie applications to particular computers or hard disks, but these cost $$$.

[Fenton]

I was mostly talking about:

1. Protecting your structure, keeping others from taking your solution and modifying it or reselling it.

2. Stopping them from selling it to another company, with a different name.

Yes, they could enter data all they wanted.

It is much more difficult to stop them from using it on multiple computers within the same company.

Yes, there are methods to tie a particular file to a particular computer. I could do this fairly easily on a Mac, and I suppose it can be done much same on Windows. However, and this is big however, if you did this you would be expected to support a situation where the user gets a new hard drive or computer. Are you willing to do that? Are you willing to have the support capability to do that quickly and painlessly for multiple users? If not, then realize you are going to have some annoyed people on your hands at some time in the not too distant future.

I am not a power user when it comes to such things, nor do I sell vertical solutions. If you plan to do so then you will have to educate yourself about the methods for demos and locking, not all of which are strictly FileMaker. That is one of the obligations of those who sell vertical solutions, and one reason why many of us are wary of it, though it is a good direction if you have a good idea and a market.

I believe there is some information and a solution at http://www.fmwebschool.com

[tentenths]

I will do more research on demos and locking and look at the link.

the best method for copy protection I have seen is what macromedia uses...you get 2 installs and you must install and uninstall over the web. You can move it from computer to computer this way...but if a drive fails then I'm not sure how to handle that.

thanks guys.

[Fenton]

Here is the solution I was thinking about at fmwebschool.

http://www.fmlock.com/

A caveat. On Macs it is quite possible to have no real computer serial number.* If your logic board has been replaced, such as mine was, you may or may not have a serial number. Mine does not. Yet my software registrations all work fine. So I'm not sure exactly how they do that, but it is more complex than just one serial number.

*Actually mine is now "SystemSerialNumb"

To find out what yours is, you can run this AppleScript:

do shell script "system_profiler SPHardwareDataType | grep 'Serial Number'| cut -c 22-"

There's also the MAC address:

do shell script "ifconfig en0 | grep ether | cut -c 8-24"

[tentenths]

fmlock is perfect...thanks!