Java Birthmarks--Detecting the Software Theft--

Haruaki TAMADA; Masahide NAKAMURA; Akito MONDEN; Ken-ichi MATSUMOTO

doi:10.1093/ietisy/e88-d.9.2148

Java Birthmarks--Detecting the Software Theft--

Haruaki TAMADA, Masahide NAKAMURA, Akito MONDEN, Ken-ichi MATSUMOTO

Full Text Views

0

Share
Cite this

Summary :

To detect the theft of Java class files efficiently, we propose a concept of Java birthmarks, which are unique and native characteristics of every class file. For a pair of class files p and q, if q has the same birthmark as p's, q is suspected as a copy of p. Ideally, the birthmarks should satisfy the following properties: (a) preservation - the birthmarks should be preserved even if the original class file is tampered with, and (b) distinction - independent class files must be distinguished by completely different birthmarks. Taking (a) and (b) into account, we propose four types of birthmarks for Java class files. To show the effectiveness of the proposed birthmarks, we conduct three experiments. In the first experiment, we demonstrate that the proposed birthmarks are sufficiently robust against automatic program transformation (93.3876% of the birthmarks were preserved). The second experiment shows that the proposed birthmarks successfully distinguish non-copied files in a practical Java application (97.8005% of given class files were distinguished). In the third experiment, we exploit different Java compilers to confirm that the proposed Java birthmarks are core characteristics independent of compiler-specific issues.

Publication: IEICE TRANSACTIONS on Information Vol.E88-D No.9 pp.2148-2158

Publication Date: 2005/09/01

Publicized

Online ISSN

DOI: 10.1093/ietisy/e88-d.9.2148

Type of Manuscript: PAPER

Category: Application Information Security

Authors

Haruaki TAMADA
Masahide NAKAMURA
Akito MONDEN
Ken-ichi MATSUMOTO

Keyword

Cite this

Copy

Haruaki TAMADA, Masahide NAKAMURA, Akito MONDEN, Ken-ichi MATSUMOTO, "Java Birthmarks--Detecting the Software Theft--" in IEICE TRANSACTIONS on Information, vol. E88-D, no. 9, pp. 2148-2158, September 2005, doi: 10.1093/ietisy/e88-d.9.2148.
Abstract: To detect the theft of Java class files efficiently, we propose a concept of Java birthmarks, which are unique and native characteristics of every class file. For a pair of class files p and q, if q has the same birthmark as p's, q is suspected as a copy of p. Ideally, the birthmarks should satisfy the following properties: (a) preservation - the birthmarks should be preserved even if the original class file is tampered with, and (b) distinction - independent class files must be distinguished by completely different birthmarks. Taking (a) and (b) into account, we propose four types of birthmarks for Java class files. To show the effectiveness of the proposed birthmarks, we conduct three experiments. In the first experiment, we demonstrate that the proposed birthmarks are sufficiently robust against automatic program transformation (93.3876% of the birthmarks were preserved). The second experiment shows that the proposed birthmarks successfully distinguish non-copied files in a practical Java application (97.8005% of given class files were distinguished). In the third experiment, we exploit different Java compilers to confirm that the proposed Java birthmarks are core characteristics independent of compiler-specific issues.
URL: https://globals.ieice.org/en_transactions/information/10.1093/ietisy/e88-d.9.2148/_p

Copy

@ARTICLE{e88-d_9_2148,
author={Haruaki TAMADA, Masahide NAKAMURA, Akito MONDEN, Ken-ichi MATSUMOTO, },
journal={IEICE TRANSACTIONS on Information},
title={Java Birthmarks--Detecting the Software Theft--},
year={2005},
volume={E88-D},
number={9},
pages={2148-2158},
abstract={To detect the theft of Java class files efficiently, we propose a concept of Java birthmarks, which are unique and native characteristics of every class file. For a pair of class files p and q, if q has the same birthmark as p's, q is suspected as a copy of p. Ideally, the birthmarks should satisfy the following properties: (a) preservation - the birthmarks should be preserved even if the original class file is tampered with, and (b) distinction - independent class files must be distinguished by completely different birthmarks. Taking (a) and (b) into account, we propose four types of birthmarks for Java class files. To show the effectiveness of the proposed birthmarks, we conduct three experiments. In the first experiment, we demonstrate that the proposed birthmarks are sufficiently robust against automatic program transformation (93.3876% of the birthmarks were preserved). The second experiment shows that the proposed birthmarks successfully distinguish non-copied files in a practical Java application (97.8005% of given class files were distinguished). In the third experiment, we exploit different Java compilers to confirm that the proposed Java birthmarks are core characteristics independent of compiler-specific issues.},
keywords={},
doi={10.1093/ietisy/e88-d.9.2148},
ISSN={},
month={September},}

Copy

TY - JOUR
TI - Java Birthmarks--Detecting the Software Theft--
T2 - IEICE TRANSACTIONS on Information
SP - 2148
EP - 2158
AU - Haruaki TAMADA
AU - Masahide NAKAMURA
AU - Akito MONDEN
AU - Ken-ichi MATSUMOTO
PY - 2005
DO - 10.1093/ietisy/e88-d.9.2148
JO - IEICE TRANSACTIONS on Information
SN -
VL - E88-D
IS - 9
JA - IEICE TRANSACTIONS on Information
Y1 - September 2005
AB - To detect the theft of Java class files efficiently, we propose a concept of Java birthmarks, which are unique and native characteristics of every class file. For a pair of class files p and q, if q has the same birthmark as p's, q is suspected as a copy of p. Ideally, the birthmarks should satisfy the following properties: (a) preservation - the birthmarks should be preserved even if the original class file is tampered with, and (b) distinction - independent class files must be distinguished by completely different birthmarks. Taking (a) and (b) into account, we propose four types of birthmarks for Java class files. To show the effectiveness of the proposed birthmarks, we conduct three experiments. In the first experiment, we demonstrate that the proposed birthmarks are sufficiently robust against automatic program transformation (93.3876% of the birthmarks were preserved). The second experiment shows that the proposed birthmarks successfully distinguish non-copied files in a practical Java application (97.8005% of given class files were distinguished). In the third experiment, we exploit different Java compilers to confirm that the proposed Java birthmarks are core characteristics independent of compiler-specific issues.
ER -