Differences between revisions 29 and 30
Revision 29 as of 2015-02-08 16:09:04
Size: 2299
Editor: JakubWilk
Comment: Remove my old e-mail address. All the bug have been retagged with the new one.
Revision 30 as of 2015-02-26 03:45:19
Size: 2537
Editor: PaulWise
Comment: add clonewise link so it doesn't get lost
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
[[https://github.com/silviocesare/Clonewise|Clonewise]] is a tool not yet in Debian that [[https://lists.debian.org/debian-security/2012/07/msg00000.html|could be used to find unfixed vulnerabilities because of embedded code copies]].

Debian Policy 4.13 states that Debian packages should not use convenience copies.

The list of packages embedding code from other projects is maintained in the secure-testing svn repository:

https://anonscm.debian.org/viewvc/secure-testing/data/embedded-code-copies?view=co

This list also contains information about code forks so that the security team can check if all forks contain the same vulnerabilities. Send suggestions or additions to the debian-security-tracker mailing list.

Lintian detects embedding of feedparser, common JavaScript/C/C++/PEAR/PHP libraries and ?PostScript fragments (1 2).

The Debian duplication detector detects duplicate files in binary packages and may be useful for detecting verbatim duplication of interpreted code and data.

Clonewise is a tool not yet in Debian that could be used to find unfixed vulnerabilities because of embedded code copies.

If you have a particular piece of code with some interesting aspect (security issue etc) you can likely find other copies using the Debian code search site or external code search engines such as Ohloh code, searchcode and GitHub.

Various Debian folks keep track of embedded code copies they found via usertags:

rbrito@ime.usp.br jwilk@debian.org pabs@debian.org sramacher@debian.org