Red Hat Bugzilla – Bug 236309
itext contains Sun confidential code
Last modified: 2007-11-30 17:12:02 EST
Description of problem:
The following files in the itext tarball:
contain code with the following copyright header:
* Copyright 1998 by Sun Microsystems, Inc.,
* 901 San Antonio Road, Palo Alto, California, 94303, U.S.A.
* All rights reserved.
* This software is the confidential and proprietary information
* of Sun Microsystems, Inc. ("Confidential Information"). You
* shall not disclose such Confidential Information and shall use
* it only in accordance with the terms of the license agreement
* you entered into with Sun.
Version-Release number of selected component (if applicable):
itext is a dependency of rssowl, so if itext is pulled, rssowl has to go to.
The offending code has been zapped upstream in version 2.0.3:
> Removal of EPS support. The code that was used from SUN's PostscriptDemo had
> ambiguous license information. Therefore it is better to look for an
However, itext is really a license minefield, searching for "Sun Microsystems"
covered up some code which is essentially BSD-licensed, but with the following
obnoxious clause added:
> You acknowledge that Software is not designed,licensed or intended for use
> in the design, construction, operation or maintenance of any nuclear
The "licensed" part is the issue, because this appears to restrict the
BSD-style license preceding this paragraph, making the code non-Free.
I wonder how many other supposedly Free Software Java projects are
incorporating Sun code under similar non-Free licenses.
Sadly, much of the java world has typically been poor with licence checking and
The source contains a text file that tries to justify the sun licensed code. I
don't have time to sort all this out, so I intend to EOL itext and rssowl in
Extras and F7. If somebody wants to dig through the licensing issues then they
should feel free to take these packages over. overholt tells me that rssowl2
doesn't require itext, so it looks like it can return in Fedora 8.
I've just completed the EOL process and am closing this bug.