140:
Licence laundering may be identified by detecting inconsistencies in the works. Most content creators use a set of common elements that are consistent throughout their portfolio, for example a style or handwriting. Users engaged in licence laundering typically upload files with a diversity of styles,
127:
may be released with a pre-approved non-reciprocal licence permitting its use in other projects, which facilitates license laundering. To avoid such laundering, developers and project managers should determine the source of the code, and mitigate potential problems with a
269:
273:
171:
data associated with files. If the data is generally consistent in a set of files, the files were likely generated by the same individual, whereas if the data differ significantly, it may be indicative of a
300:
423:
84:
to exclude its revision history or other details. This source code is then modified or integrated into other software, possibly violating the original licence terms.
156:. These services compare the characteristics of a reference work to a database containing the characteristics for numerous works analyzed by the service provider by
246:
216:
296:
333:
270:"Operating (system) without a license: Does Section 4 of the GPL leave Google and Android device manufacturers unlicensed? (Part 2)"
460:
112:
389:
189:
87:
Another example is using code released under one licence, and redistributing it under a different licence. After
363:
80:
written by one or more other programmers but removing the licence from the source files or altering the file's
104:
100:
242:
110:
stating that "The world is not about stealing people's code, laundering it and saying everything's OK." In
173:
328:
92:
145:
124:
69:
52:
Licence laundering of media and related files is common on image hosting providers such as Flickr or
220:
81:
416:"Service Commons -- Serve and Serve Alike: Applying the Creative Commons Spirit to Web Services"
49:
with a different one. This party then illegitimately distributes the work with the new licence.
455:
129:
427:
360:
Open Source
Software: Risks, benefits & practical realities in the corporate environment
323:
164:. The results of a reverse image search may indicate the original source of the content.
161:
449:
415:
153:
38:
157:
141:
since the styles reflect those of the author, not the licence laundering uploader.
107:
377:
17:
77:
73:
88:
42:
431:
272:. Emerging Technologies Blog. Brown Rudnick LLP Attorney. Archived from
57:
46:
385:
177:
149:
117:
53:
168:
96:
378:"How can I use TinEye to find the copyright owner of an image?"
420:
176:. An example is a set of photographs generated by different
45:
is copied by another party, who then replaces the original
27:
Copying a work, replacing its licence and redistributing it
414:
Tatsubori, Michiaki; Gangadharan, G.R. (June 2012).
144:Image licence laundering may be detected by using
424:Institute of Electrical and Electronics Engineers
324:"Decision in SCO-Novell case ripples beyond Utah"
297:"Users outraged as SCO stakes Linux legal claim"
358:Davidson, Stephen J.; Levi, Stuart D. (2005).
120:was found to be the owner of Unix copyrights.
8:
167:Another technique involves inspecting the
362:. Intellectual property course handbook.
76:engages in licence laundering when using
154:Google Images' "Search by Image" feature
200:
268:Naughton, Edward J. (11 August 2011).
245:. ITNews/nextmedia. 12 November 2007.
243:"Perens urges firms to go open source"
56:, and video hosting providers such as
353:
351:
303:from the original on 13 February 2019
249:from the original on 13 February 2019
7:
210:
208:
206:
204:
215:Wattenberg, Leo (31 January 2015).
25:
392:from the original on 22 July 2019
336:from the original on 3 March 2016
113:SCO Group, Inc. v. Novell, Inc.
295:Weiss, Todd R. (19 May 2003).
1:
322:Harvey, Tom (30 March 2010).
190:c:Commons:License laundering
477:
382:Frequently asked questions
103:resulted, with SCO Groups
364:Practising Law Institute
217:"licence considerations"
105:chief executive officer
101:SCO/Linux controversies
461:Copyright infringement
174:copyright infringement
91:asserted it owned the
64:Source code laundering
329:The Salt Lake Tribune
93:intellectual property
146:reverse image search
125:open-source software
70:software development
432:10.1109/SCC.2012.93
223:on 26 February 2018
35:license laundering
31:Licence laundering
18:License laundering
299:. Computerworld.
148:engines, such as
130:quality assurance
16:(Redirected from
468:
442:
440:
438:
402:
401:
399:
397:
374:
368:
367:
355:
346:
345:
343:
341:
319:
313:
312:
310:
308:
292:
286:
285:
283:
281:
265:
259:
258:
256:
254:
239:
233:
232:
230:
228:
219:. Archived from
212:
21:
476:
475:
471:
470:
469:
467:
466:
465:
446:
445:
436:
434:
413:
410:
408:Further reading
405:
395:
393:
376:
375:
371:
357:
356:
349:
339:
337:
321:
320:
316:
306:
304:
294:
293:
289:
279:
277:
267:
266:
262:
252:
250:
241:
240:
236:
226:
224:
214:
213:
202:
198:
186:
138:
66:
28:
23:
22:
15:
12:
11:
5:
474:
472:
464:
463:
458:
448:
447:
444:
443:
409:
406:
404:
403:
369:
347:
314:
287:
260:
234:
199:
197:
194:
193:
192:
185:
182:
162:World Wide Web
137:
136:Identification
134:
99:, a series of
65:
62:
37:occurs when a
26:
24:
14:
13:
10:
9:
6:
4:
3:
2:
473:
462:
459:
457:
454:
453:
451:
433:
429:
425:
421:
417:
412:
411:
407:
391:
387:
383:
379:
373:
370:
365:
361:
354:
352:
348:
335:
331:
330:
325:
318:
315:
302:
298:
291:
288:
276:on 2017-02-23
275:
271:
264:
261:
248:
244:
238:
235:
222:
218:
211:
209:
207:
205:
201:
195:
191:
188:
187:
183:
181:
179:
175:
170:
165:
163:
159:
155:
151:
147:
142:
135:
133:
131:
126:
121:
119:
115:
114:
109:
106:
102:
98:
94:
90:
85:
83:
79:
75:
71:
63:
61:
59:
55:
50:
48:
44:
40:
39:creative work
36:
32:
19:
435:. Retrieved
419:
394:. Retrieved
381:
372:
359:
338:. Retrieved
327:
317:
307:24 September
305:. Retrieved
290:
278:. Retrieved
274:the original
263:
251:. Retrieved
237:
225:. Retrieved
221:the original
166:
143:
139:
132:inspection.
122:
111:
108:Darl McBride
86:
67:
51:
34:
30:
29:
340:11 February
280:11 February
78:source code
450:Categories
196:References
95:rights to
74:programmer
437:5 January
396:5 January
253:5 January
227:5 January
158:spidering
123:Code for
89:SCO Group
43:copyright
456:Licenses
390:Archived
334:Archived
301:Archived
247:Archived
184:See also
180:models.
58:YouTube
47:licence
386:TinEye
178:camera
150:TinEye
118:Novell
82:header
54:Picasa
41:under
439:2017
398:2017
342:2017
309:2017
282:2017
255:2017
229:2017
169:Exif
160:the
97:Unix
72:, a
428:doi
152:or
68:In
33:or
452::
426:.
422:.
418:.
388:.
384:.
380:.
350:^
332:.
326:.
203:^
116:,
60:.
441:.
430::
400:.
366:.
344:.
311:.
284:.
257:.
231:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.