linux-kernel - My new tool/service - identify unknown kernel source trees

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 25 Jan 2013 00:18:32 +0100
From:	Tomasz Mloduchowski <q@...t.me>
To:	linux-kernel@...r.kernel.org
Subject: My new tool/service - identify unknown kernel source trees

Hello everyone,

Every now and then I see a tree of kernel sources, contributed in good
faith and compliance with the GPL, by some hardware vendor, or even
worse, a hardware distributor, without any explanation of the changes
made, or even which official tree is it based on.

Usually, some hunting reveals that they branched off the tree
maintained by the SoC manufacturer, and few diffs later, the
investigative part is over.

It had happened for me again, few days ago. I decided to implement a
more automated solution, and I would like to hear your feedback, and
whether (which) kernel trees are notable enough as points of
divergence, to include in this tool.

Before you ask - most of these 'unidentified' sources are lacking git metadata.
Before you ask again - make kernelversion can sometimes reveal what it
is, but only for direct offspring of official trees.

Enough of the introduction, if it's something that you find useful,
please head to:

http://qdot.me/kids

Cheers!
Tomasz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/