Copyright Protection Product

Hi All, you may recall a couple of months ago (February I think) I came up with a novel idea for copyright protection of any sort of digital media/software/product. Now, we did a mock up of it for desktop software use but also did an internet based version. We've completed the algorithm for it and are hoping to publish it on here in the coming days for analysis.

This, to those who don't know about it, is the principle and method behind it:

- It is a cheap, easy, quick and effective (or so we hope) copyright protection method that rivals poor mans copyright, but in a more efficient way.

- The "User" (The individual who wishes to protect their works); Registers on our service, And chooses a username & a password. The user then simply enters the following information into the online tool:

> Author Name

> Company Name

> Company Incorporation Status

> Product Name

> Product Version

> Country

> Creation Date

> License Terms

> And a Password of their choice

> The Product/File It's Self

With this information and the following other bits of information that is generated automatically by the service:

> A Random PIN Number

> A Second Random PIN Number

> The Current Date/Time (Showing when the tool/protection procedure was run)

A Fingerprint of the file is taken, this fingerprint is then merged with all of the other provided/randomly generated pieces of information. Several Salts are applied (including an acute way of avoiding dictionary/rainbow table attacks) and encrypted using SHA512 encryption. The result is then a unique copyright finger print that is then used to identify the owner of the file, the file it's self, and most importantly WHEN the file was put through this procedure and protected.

Their IP Address, Their Username, The Files Individual Fingerprint, The License Terms, The Current/Date Time and the Unique Copyright Finger Print are stored in the online database and then made publically available to view.

The Unique Copyright Finger Print should also be distributed with that product.

Now then, we believe it will work and be successful and is therefore different because of the following reasons:

> A copy of the file and the relevant author/owners details and the current date time is combined together into a unique digital fingerprint which can not be a fraud or edited. This information proves there and then when the procedures was run as the Current/Date Time is taken from a neutral, non-fake able source. Thereby showing, that the product existed at this time. If the user ever needed to prove the said product was theirs, they should log on to our service, and using the checker tool, they supply their two PIN Numbers that were generated as part of the procedure and the Password they choose as part of the procedure. This will then be combined with the files individual finger print, their personal information and the date of the procedures execution and it will check the checksums to see if they match, if they do, the copyright ownership is proved to be of that individual.

The crucial element to this is that the users PIN Numbers & Password are what are able to "unlock" the encryption and confirm it's ownership. Aslong as you were to keep these three pieces of information to your self, no one could fake/fraud the license key.

Also, The copyright entry is publically available which shows it was run, showing the finger print also, which can be compared to distributes of the said product.

If someone tried to protect this file again, it would be rejected as the file already exists in the databanks.

Also, even if (somehow) the file was "protected" again, the earlier execution of the procedure would be defacto. Basically, as long as you protect your own work first, you should be fine.

I've have taken opinions from various individuals and it has all so-far been positive, many regarding it as an interesting concept.

So everyone, idea's, flaws, problems? Anything you've spotted would be helpful, I'd love to hear them and really appreciate your input.

Edited July 19, 200917 yr by SLGWN2P