forked from andr8w/cocoafob
/
README
228 lines (164 loc) · 8.76 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
CocoaFob
========
TABLE OF CONTENTS
=================
1. DESCRIPTION
2. FEATURES
3. USAGE
4. GENERATING KEYS
5. LICENCE
6. CREDITS
1. DESCRIPTION
==============
CocoaFob is a set of helper code snippets for registration code generation and
verification in Objective-C applications, integrated with registration code
generation in Potion Store <http://www.potionfactory.com/potionstore>.
The current implementation uses DSA to generate registration keys, which
significantly reduces chances of crackers producing key generators for your
software. Unfortunately, it also means the registration code can be quite long
and has variable length.
To make registration codes human-readable, CocoaFob encodes them using a
slightly modified base32 to avoid ambiguous characters. It also groups codes
in sets of five characters separated by dashes. A sample registration code
produced using a 512-bit DSA key looks like this:
GAWQE-FCUGU-7Z5JE-WEVRA-PSGEQ-Y25KX-9ZJQQ-GJTQC-CUAJL-ATBR9-WV887-8KAJM-QK7DT-EZHXJ-CR99C-A
One of the advantages of DSA is that for a given registration name, each
generated code is different, as there is a random element introduced during
the process.
2. FEATURES
===========
CocoaFob, a random collection of code snippets as it is, provides the
following for your application:
- Secure asymmetric cryptography-based registration key generation and
verification using DSA.
- Support for key generation in Objective-C and Ruby and verification in
Objective-C for integration in both your Cocoa application and Potion Store.
- Support for custom URL scheme for automatic application registration.
There is no framework or a library to link against. You include the files you
need in your application project directly and are free to modify the code in
any way you need.
You may also find other snippets of code useful, such as base32 and base64
encoding/decoding functions, as well as categories extending NSString and
NSData classes with base32 and base64 methods.
3. USAGE
========
The best way to get the latest version of the code is to clone the main Git
repository:
git://github.com/gbd/cocoafob.git
You can also download the latest version from the CocoaFob home page at
<http://github.com/gbd/cocoafob/>.
For more complete examples of how to use CocoaFob, look at the following
projects by Alex Clarke: CodexFab <https://github.com/machinecodex/CodexFab/>
and LicenseExample <https://github.com/machinecodex/CodexFab_LicenseExample/>.
Providing a Registration Source String
--------------------------------------
To register an application that uses CocoaFob, it is necessary to provide a
string of source information, which may be as simple as a registration name
or arbitrarily complex in case your application is processing the included
information in a user-friendly way. For example, as suggested in the sample
implementation of Potion Store licence generator, a source string may contain
application name, user name and number of copies:
decloner|Joe Bloggs|1
When sending registration mail, you need to provide both the source string and
the registration code. Potion Store does this for you. However, small
modifications are needed to make automatic activation work.
Generating automatic activation URLs
------------------------------------
Potion Store supports automatic activation of an installed application by
clicking on a special link in a registration email or on the Thank You store
page. For this to work, you need to:
- make your application support a registration URL scheme;
- modify Potion Store so that automatic activation link contains not only
registration code, but registration source string as well.
The stock implementation of Potion Store registration code support assumes a
registration code is all that is needed to register an application. However,
CocoaFob needs to know both registration name and registration code in order
to verify the licence. This means when Potion Store generates an automatic
registration URL for your application, it needs to include registration source
string in it. One of the possible solutions is as follows:
- In your database migration 001_create_tables.rb, increase the length of
license_key column in line_items table to 128 characters:
t.column "license_key", :string, :limit => 128
- In the file app/models/line_item.rb, add the following line at the top:
require "base64"
- In the same file find function called license_url--it's near the bottom of
the file. Replace it with the following (or modify to your heart's content):
def license_url
licensee_name_b64 = Base64.encode64(self.order.licensee_name)
return "#{self.product.license_url_scheme}://#{licensee_name_b64}/#{self.license_key}" rescue nil
end
This will make generated registration codes to contain base64-encoded licensee
name. When your application is opened by clicking on the registration link, it
will parse the code, extract the registration name and use it to verify the
licence.
Supporting registration URL schema in your app
----------------------------------------------
The following files in objc directory provide a sample implementation of
support for custom URL schema for application registration. The code is almost
literally taken from [3].
To support registration URLs in your application:
- Add files MyApp.scriptSuite and MyApp.scriptTerminology to your project's
resources, adjusting strings inside appropriately.
- Add the following to your application's Info.plist file under /plist/dict
key (replace mycompany and myapp with strings appropriate for your company
and application):
<key>NSAppleScriptEnabled</key>
<string>YES</string>
<key>CFBundleURLTypes</key>
<array>
<dict>
<key>CFBundleURLSchemes</key>
<array>
<string>com.mycompany.myapp.lic</string>
</array>
</dict>
</array>
- Add the files URLCommand.h and URLCommand.m to your project, paying
attention to the TODO: comments in them. Specifically, you may want to save
registration information to your application's preferences, and also
broadcast a notification of a changed registration information after
verifying the supplied registration URL.
- Be sure the URL scheme name in the Info.plist file (com.mycompany.myapp.lic)
is the same as the one in the database generation script for Potion Store.
It is the file db/migrate/001_create_tables.rb, and the variable is called
license_url_scheme.
Test the URL schema support by making a test purchase which results in
displaying an activation link, and clicking on it. If you are running your
application in debugger, place a breakpoint in the URLCommand instance method
performWithURL:. The breakpoint will be triggered when you click on the
registration link. You can extract the link into a standalone HTML file so
that is available for testing without making any additional test purchases.
4. GENERATING KEYS
==================
IMPORTANT NOTE: Included keys are for demonstration and testing purposes only.
DO NOT USE THE INCLUDE KEYS IN YOUR SOFTWARE. Before incorporating CocoaFob
into your application, you need to generate a pair of your own DSA keys. I
used key length of 512 bit which I thought was enough for the registration
code generation purposes.
(0) Make sure OpenSSL is installed. (If you're using Mac OS X, it already is.)
(1) Generate DSA parameters:
openssl dsaparam -out dsaparam.pem 512
(2) Generate an unencrypted DSA private key:
openssl gendsa -out privkey.pem dsaparam.pem
(3) Extract public key from private key:
openssl dsa -in privkey.pem -pubout -out pubkey.pem
See [2] for more information.
5. LICENCE
==========
CocoaFob is Copyright (C) 2009 PixelEspresso
<http://www.pixelespressoapps.com>. All rights reserved. Written by Gleb
Dolgich (Twitter: @glebd)
CocoaFob is distributed under Creative Commons Attribution 3.0 License
<http://creativecommons.org/licenses/by/3.0/>. Attribution may take form of a
mention in your application About box or other documentation.
6. CREDITS
==========
[0] The Mac developer community that continues to amaze me.
[1] Base32 implementation is Copyright (C) 2007 by Samuel Tesla and comes from
Ruby base32 gem: <http://rubyforge.org/projects/base32/>. Samuel Tesla's blog
is at <http://blog.alieniloquent.com/tag/base32/>.
[2] OpenSSL key generation HOWTO: <http://www.openssl.org/docs/HOWTO/keys.txt>
[3] Handling URL schemes in Cocoa: a blog post by Kimbro Staken
<http://www.xmldatabases.org/WK/blog/1154?t=item>
[4] Registering a protocol handler for an App: a post on CocoaBuilder mailing
list, <http://www.cocoabuilder.com/archive/message/cocoa/2009/2/2/229297>