Abstract: The present invention, generally speaking, provides a flexible mechanism for effecting a payment/unlock transaction for deliver-then-pay content distribution. Instead of interacting with a local client interface, purchase is effected by interacting with a commerce Web site. The content is unlocked by delivering to the client a certificate, which serves as proof of purchase. The certificate is rendered secure so that it cannot simply be replicated to gain additional unauthorized access. In a preferred embodiment, a local application (e.g., a stand-alone application or a browser plug-in) is present on the end-user's machine and is registered with the local operating system and browser to handle files of a particular type used for certificates. Downloading and processing of the certificate may therefore be done transparently, without user-intervention. Piracy is prevented by “individuation” of the certificate.

Abstract: The present invention, generally speaking, makes possible an associates program for electronic content distribution by providing a mechanism whereby a referrer may be identified at the time of purchase in a download-then-pay system. In accordance with one embodiment of the invention, an identifier or marker is added to the electronic content at the time of download. Merchant and purchase location information may also be added. At the time of purchase, a commerce module retrieves the identifier and presents it to the merchant server. The commerce module may also form part of the download or may originate from another source. The identifier may be used for various purposes. For example, the identifier may be used, directly or indirectly, to identify a referrer, to whom a referral fee is then credited. Also, the identifier may be used to look up offer information, since the price at the time of purchase may be different than the offer price at the time of download.

Abstract: The present invention, generally speaking, provides for secure electronic software packaging using a setup-external unlocking module. As a result, a software publisher can produce a single ESD-ready version of a software title that may later be prepared for distribution through multiple different ESD channels by adding channel-specific unlocking modules. Duplication of the injection process prior to the packing of the setup file set is eliminated and great flexibility is achieved. Preferably, the single ESD-ready version allows for trial of the software, e.g., a free 30-day trial. Software publishers are incentivized to produce trial versions of their software for marketing purposes. Once such a trial version of a software title has been produced, no further modifications are required on the part of the software publisher in order to distribute the software through various different channels.

Abstract: The present invention, generally speaking, provides a mechanism for modifying an executable upon first execution. Various modifications may be made to the executable, including modifications useful for purposes of electronic software distribution, such as attaching a unique serial number, encrypting or decrypting the executable, or adding protection code (license enforcement code) to the executable. A Rewriter Module performs the actual modification. First, a copy of the executable is made. The copy is then run and the original executable is deleted. Then a second copy of the executable is made using the name of the original executable, and the first copy is deleted. During one or both of the copying steps, modifications are made to the executable. The modifications may be modifications useful for purposes of electronic software distribution, especially Try/Buy. When a software product is purchased, the foregoing process may be reversed, leaving the executable in its original "pristine" condition.

Abstract: The present invention, generally speaking, provides a software protection mechanism that may be conveniently configured by a software publisher and applied to a software product. Various predefined software protection measures are presented to the software publisher, who selects which protection measures, if any, the software publisher wishes to apply to a software product. The software publisher may select all of the software protection measures, none of the software protection measures, or any logically consistent combination thereof. An option is also provided for the software publisher to provide code implementing a custom software protection mechanism. The software publisher's selections are saved in a license file that is attached to the software product. A Protector Module is also attached to the software product. The Protector Module includes code for each predefined software protection option.

Abstract: Methods of electronic software distribution are provided in which software products may be wrapped by their publishers in a straightforward, secure manner, but in such a way as to allow for the addition of information by downstream distribution channel partners, e.g., distributors and merchants (resellers). Distribution policies, or business rules, governing the distribution process may be fixed by the software publisher or may be left to the discretion of channel partners. The software product itself, however, is secured against tampering or inadvertent infection by a virus. A tool facilitates the foregoing incremental wrapping process without requiring sophistication in computer technology on the part of channel partners. The publisher may use a conventional setup tool of the publisher's choice to prepare a setup file set for distribution. That is, the wrapping tool need not influence the publisher's choice of setup tools.

Abstract: The present invention, generally speaking, provides a mechanism for use in conjunction with Electronic Software Distribution (ESD) that provides purchase documentation and that allows for convenient re-download and relicensing of soft-ware, including old software versions. In accordance with one embodiment of the invention, a relicensing manager software utility installed on an end user's machine interacts with one or more of a remote publisher site, a license clearing house and a merchant site to relicense, transfer, or obtain a refund for a software product. The term "software product" is used to refer to both executable software programs and to electronic content (e.g, pictures, recordings, etc.) The role of the publisher site is to archive both current and old versions of software products. The role of the license clearinghouse is to keep a count of licensed installations and to grant or deny permission to relicense based on the count.