Many thanks to Omair Majid for preparing the 1.12.1 release while I was still returning home from FOSDEM. Much appreciated!

The IcedTea project provides a harness to build the source code from OpenJDK using Free Software build tools, along with additional features such as a PulseAudio sound driver and support for alternative virtual machines.

A new security release is now available for the OpenJDK 6 series: 1.12.1. Regarding 7, we’ve hit bootstrapping issues that we’re trying to work around so it can still be built with OpenJDK 6, but if you fancy rolling your own using an earlier build of 7, the forests are already up-to-date for 2.3 as is the IcedTea7 2.3 repository.

The update contains the following security fixes:

Full details can be found below.

What’s New?

New in release 1.12.1 (2012-02-04)

The tarball can be downloaded from:

SHA256 checksum:

  • 8e73a3939ba8c2cca888defc6c90811c959273a9bc7bd1352338a72cefcf1157 icedtea6-1.12.1.tar.gz

The tarball is accompanied by a digital signature available at the above ‘sig’ link. This is produced using Omair’s public key. See details below.

  • PGP Key: 66484681 (http://pgp.mit.edu/)
  • Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681

The following people helped with these releases:

  • Andrew John Hughes (applying all security patches & backports, release testing)
  • Omair Majid (identification of ordering issues with security patches, porting security patches to 1.12)

We would also like to thank the bug reporters and testers!

To get started:

$ tar xzf icedtea-1.12.1.tar.gz
$ cd icedtea-1.12.1

Full build requirements and instructions are in INSTALL:

$ ./configure [--with-parallel-jobs --enable-pulse-java
--enable-systemtap ...]
$ make

Happy hacking!

The IcedTea project provides a harness to build the source code from OpenJDK using Free Software build tools, along with additional features such as a PulseAudio sound driver and support for alternative virtual machines.

A new security release is now available for the OpenJDK 6 series: 1.11.6. An update for the recent release, 1.12.1, will follow shortly,as will updates for 7: 2.1.5, 2.2.5, 2.3.5 and eventually a 2.4.1. (2.4.0 will sadly have to now be just another tag release). Regarding 7, we’ve hit bootstrapping issues that we’re trying to work around so it can still be built with OpenJDK 6, but if you fancy rolling your own using an earlier build of 7, the forests are already up-to-date for 2.3 and the IcedTea7 2.3 repository will be as well, shortly (allowing Classpath JDK builds too).

The update contains the following security fixes:

Full details can be found below.

What’s New?

New in release 1.11.6 (2012-02-03)

The tarball can be downloaded from:

SHA256 checksum:

  • 1d4efe74bf8902c6682512ddb3cf71620e4fe107d1fb364b71453b551860fcca icedtea6-1.11.6.tar.gz

Each tarball is accompanied by a digital signature available at the above ‘sig’ link. This is produced using my public key. See details below.

The following people helped with these releases:

  • Andrew John Hughes (applying all security patches & backports, release management)
  • Omair Majid (identification of ordering issues with security patches)

We would also like to thank the bug reporters and testers!

To get started:

$ tar xzf icedtea-1.11.6.tar.gz
$ cd icedtea-1.11.6

Full build requirements and instructions are in INSTALL:

$ ./configure [--with-parallel-jobs --enable-pulse-java
--enable-systemtap ...]
$ make

Happy hacking!

Or the blog that wanted to be a talk… ;-)

Disclaimer: as usual for this blog, these are my personal thoughts, and not necessarily those of Red Hat.

The History

IcedTea started at Red Hat in the summer of 2007 as a means to deal with the requirements of building the new OpenJDK source code base on GNU/Linux platforms using only Free Software build tools. The OpenJDK source code was (and still is, to a large extent) built on a completely different set of inherent assumptions to those held by a GNU/Linux distribution packager; it was designed to produce a set of binaries which Sun could ship and which would run on as many platforms as possible with as few dependencies as possible. In contrast, a packager wants to make use of existing packages as much as possible, because this reduces the support footprint of the package. In fact, not bundling libraries is a requirement on some distributions, such as Fedora, one of Red Hat’s primary targets. It also didn’t matter too much to Sun what tools were used to build the JDK, as long as they were available and didn’t impact on the end result; the binaries. In contrast, distribution builds need to work with tools available within the distro and often without network access.

When OpenJDK first shipped, a proprietary JDK was required to build and some parts were still in process of being opened up, and so were provided by proprietary binary blobs. Red Hat did an admirable job of fixing things, within the auspices of IcedTea, within a month of the first OpenJDK source code drop, so that OpenJDK could be built and run with Free Software tools, using parts of GNU Classpath to replace some of the plugs. This was packaged in Fedora and provided an early version of what would become OpenJDK 7 to its users.

The Progress of Time

The situation has changed in the four and a half years since IcedTea first appeared, both in terms of OpenJDK and IcedTea itself. When OpenJDK started, code was provided simply as tarballs. There were no source code repositories and no bug tracker. The first of those changed by December 2007 when the Mercurial repositories were first populated. We’re still waiting on the latter, though there has been a Bugzilla experiment in the interim. Thus, IcedTea was setup as a place to do work on OpenJDK because there was no other place. Now, that there is, with its own groups, projects, repositories and bylaws, and with the proprietary plugs long a thing of the past, we have to question whether IcedTea is still required.

A number of issues arise when we start to consider dropping IcedTea and moving work upstream:

  • IcedTea still contains a lot of local patches. Progress is being made on getting these into OpenJDK, but it’s still a very slow process. A patch that is ok for the users of IcedTea needs to be reconsidered and often even rewritten for adoption in OpenJDK. A large amount of work was done in that area prior to the first release of IcedTea 2.x (the OpenJDK 7 series); notably, the system library patches were written to become build options rather than a one-way transition to using the system versions. However, the origin and need for some patches is hard to trace, and of course, work continues so new patches are needed all the time.
  • IcedTea is now home to a number of other sub-projects;

    • it has support for replacing HotSpot with CACAO or JamVM
    • it has its own fork of the jtreg testsuite so it can be built easily and used to test the build
    • it has a PulseAudio sound driver
    • it includes a plugin and web start implementation which aren’t present in OpenJDK; this started in IcedTea itself, but was split off into its own repositories and development cycle (IcedTea-Web), so it wasn’t tied to IcedTea releases.
    • It includes an ARM32 port which, for licensing reasons, can probably never go upstream.
  • Working in OpenJDK requires signing a contributor agreement with Oracle and working with a team overwhelmingly dominated by Oracle employees, where occasional things happen behind closed doors (though the new governing bylaws and IBM’s involvement seem to have reduced this a little). Some people just feel a lot more comfortable putting their patch in IcedTea instead, which is much more akin to a traditional FOSS development project.

The Future

With the advent of OpenJDK 8 later this year, it comes time again, as with 7, to consider whether and how IcedTea should continue. In that respect,I’d like to use this blog to ask people for their thoughts on the matter, in particular how they see their ability to work with IcedTea as opposed to OpenJDK.

From my perspective, I think we could move to a situation, on a technical basis, where we work primarily with OpenJDK itself, with the odd patch that needs to be applied locally. My main concerns are with release management. IcedTea has followed a traditional path of updating existing releases with security updates and providing new releases with feature improvements. In the case of the work on 7, these have mirrored the upstream 7u project as close as possible. However, the situation upstream leaves a lot to be desired. Security updates are not applied to the last 7u release tree, instead being applied to the next in-development version. This leaves open the question of how do we get these security fixes out to users if we don’t have IcedTea? Moreover, the release process lacks transparency, and releases such as u10 have just been withdrawn with little explanation. If, for 8, we were to work closer to upstream, this would need to change.

I do see IcedTea continuing in some form, at the very least for things like CACAO & JamVM. If it continues as a patch provider, then I strongly suggest we start afresh from OpenJDK and only apply what patches are needed, with solid written reasoning for each one, rather than dragging along the baggage from 6 and 7.

Thoughts?

Update: It appears a question mark is too subtle for most people… :) So I changed the title.

We are pleased to announce the release of IcedTea6 1.12.0!

The IcedTea project provides a harness to build the source code from OpenJDK6 using Free Software build tools, along with additional features such as a PulseAudio sound driver and support for alternative virtual machines.

This is the first major release in a year (1.11 was released on 2012-01-30). In accordance with the release policy, 1.10 will no longer receive security updates.

If you find an issue with one of these releases, please report it in our bug database under the appropriate component. Development discussion takes place on the OpenJDK distro-pkg-dev mailing list and patches are always welcome.

Full details of each release can be found below.

What’s New?

New in release 1.12.0 (2013-01-29)

  • Import of OpenJDK6 b27 (all changes already in security updates)
  • Import of OpenJDK6 b26
    • S7071826: Avoid benign race condition in initialization of UUID
    • S7123896: Unexpected behavior due to Solaris using separate IPv4 and IPv6 port spaces
    • S7142509: Cipher.doFinal(ByteBuffer,ByteBuffer) fails to process when in.remaining() == 0
    • S7157903: JSSE client sockets are very slow
    • S7174440: JDK6-open build breakage
    • S7175845: JSSE client sockets are very slow
    • S7176477: TEST: Remove testcase test/java/lang/SecurityManager/CheckPackageDefinition.java from jdk6-open
    • S7184700: Backout changes with wrong id for 7157903
    • S7199153: TEST_BUG: try-with-resources syntax pushed to 6-open repo
  • Import of OpenJDK6 b25
    • S6790292: BOOTDIR of jdk6 u12 will not work with jdk7 builds
    • S6967036: Need to fix links with // in Javadoc comments
    • S7007299: FileFontStrike appears not to be threadsafe
    • S7022473: JDK7 still runs /etc/prtconf to find memory size
    • S7058133: Javah should use the freshly built classes instead of those from the BOOTDIR jdk
    • S7107919: Remove hotspot assertion due to Solaris 8 kstat “unimplemented”.
    • S7123519: problems with certification path
    • S7126889: Incorrect SSLEngine debug output
    • S7127104: Build issue with prtconf and zones, also using := to avoid extra execs
    • S7128474: Update source copyright years
    • S7128505: Building on em64t system does not work
    • S7149751: another krb5 test in openjdk6 without test infrastructure
  • Backports
    • S6706974: Add krb5 test infrastructure
    • S6764553: com.sun.org.apache.xml.internal.security.utils.IdResolver is not thread safe
    • S6761072: new krb5 tests fail on multiple platforms
    • S6883983: JarVerifier dependency on sun.security.pkcs should be removed
    • S4465490: Suspicious about double-check locking idiom being used in the code
    • S6763340: memory leak in com.sun.corba.se.* classes
    • S6873605: Missing finishedDispatch() call in ORBImpl causes test failures after 5u20 b04
    • S6980681: CORBA deadlock in Java SE believed to be related to CR 6238477
    • S7162902: Umbrella port of a number of corba bug fixes from JDK 6 to jdk7u/8
    • S6414899: P11Digest should support cloning
    • S4898461: Support for ECB and CBC/PKCS5Padding
    • S6604496: Support for CKM_AES_CTR (counter mode)
    • S6682411: JCK test failed w/ ArrayIndexOutOfBoundException (-1) when decrypting with no data
    • S6682417: JCK test failed w/ ProviderException when decrypted data is not multiple of blocks
    • S6687725: Internal PKCS5Padding impl should throw IllegalBlockSizeException and not BadPaddingException
    • S6812738: SSL stress test with GF leads to 32 bit max process size in less than 5 minutes with PCKS11 provider
    • S6867345: Turkish regional options cause NPE in sun.security.x509.AlgorithmId.algOID
    • S6924489: sun.security.pkcs11.wrapper.PKCS11Exception: CKR_OPERATION_NOT_INITIALIZED
    • S7088989: Improve the performance for T4 by utilizing the newly provided crypto APIs
  • Bug fixes
    • PR902: PulseAudioClip getMicrosecondsLength() returns length in milliseconds, not microseconds
    • PR1050: Stream objects not garbage collected
    • PR1113: Add tapset tests to distribution.
    • PR1117: IcedTea6 prebuilds far too many classes on bootstrap
    • PR1121: Old installs still suffer from GCC PR41686
    • PR1119: Only add classes to rt-source-files.txt if the class (or one or more of its methods/fields) are actually missing from the boot JDK
    • PR1114: Provide option to turn off downloading of tarballs (–disable-downloading)
    • PR1176: Synchronise CACAO rules between IcedTea6/7/8 where possible
    • RH513605, PR1171: Updating/Installing OpenJDK should recreate the shared class-data archive
    • G422525: Apply pax markings before using a freshly built JVM.
    • PR986: IcedTea7 fails to build with IcedTea6 CACAO due to low max heap size
  • CACAO
    • PR1120: Unified version for icedtea6/7
    • CA166, CA167: check-langtools fixes for icedtea6
    • Implemented sun.misc.Perf.highResCounter
    • CACAO now identifies by its own Mercurial revision
    • Some memory barrier maintenance
    • Ability to run when compiled as Thumb on armv5 (no Thumb JIT though)
    • Stop creating pseudo files for OpenJDK (libjsig.so, Xusage.txt)
    • Clang fix for the i386 backend
    • CONTRIBUTE: Reference code submission process wiki instructions.
    • INSTALL.CACAO: Update, so following the instruction actually works.
    • Make doxygen work
    • CA172, PR1266, G453612: ARM hardfloat support
    • src/scripts/java.in: Look for cacao executable in install path, not in PATH.
    • src/vm/jit/alpha/asmpart.S: Fix copyright header.
    • src/vm/jit/alpha/asmpart.S: Properly set up GP in asm_abstractmethoderror
    • Use @abs_top_builddir@ for support scripts
  • JamVM
    • ARMv6 armhf: Changes for Raspbian (Raspberry Pi)
    • PPC: Don’t use lwsync if it isn’t supported
    • X86: Generate machine-dependent stubs for i386
    • When suspending, ignore detached threads that have died, this prevents a user caused deadlock when an external thread has been attached to the VM via JNI and it has exited without detaching
    • Add missing REF_TO_OBJs for references passed from JNI, this enable JamVM to run Qt-Jambi
    • PR1155: Do not put version number in libjvm.so SONAME
  • SystemTap
    • Addition of garbage collection probes

The tarball can be downloaded from:

SHA256 checksums:

  • 4f27f3f42b57836cfb11541736282ccfc22de3f4acc0e540560fcf5512d66ced icedtea6-1.12.0.tar.gz

Each tarball is accompanied by a digital signature available at the above ‘sig’ link. This is produced using my public key. See details below.

The following people helped with this release:

We would also like to thank the bug reporters and testers!

To get started:

$ tar xzf icedtea6-1.12.0.tar.gz
$ cd icedtea-${version}

Full build requirements and instructions are in INSTALL:

$ ./configure [--with-parallel-jobs --enable-pulse-java
--enable-systemtap ...]
$ make

Happy hacking!

[As sent to distro-pkg-dev]

I’d like to do a couple of new releases of both 6 & 7 by the end of this week (Friday the 25th of January, 2013). This will enable us to get some fixes out to users that are lurking only in HEAD. This is particularly true of 6 where the last major release is nearly a year ago (30th of January, 2012). Note that 2.4.0 is already tagged in the forest, so any remaining changes prior to release will only take place in IcedTea7.

These release will also make the upcoming security release easier, as we will then update them rather than the aging 1.10 and 2.2, as stated in the release policy. In particular, it is becoming painful to maintain 1.10 as it has two HotSpot releases. Others are, of course, welcome to update these releases if they so wish.

I intend to delay creating branches for these releases until after the release, as neither repository is particularly high traffic at the moment. Please bear this in mind if you intend to commit work this week, and perhaps consider delaying it until the week after if it will be fairly disruptive.

If anyone has objections to the release of 1.12 and 2.4 this Friday, please reply to this mail as soon as possible. I’m unwilling to delay them much further as we get closer to the update, and I’d rather not be bundling feature updates with security updates.

The security update will still bring updates for 1.11, 2.1 and 2.3 (2.1 being for the ARM32 port), so an option remains between the new releases and the old.

I don’t like to go into too much detail about security updates, but I think it’s necessary to point out a few facts about the one we released yesterday, given some of the inaccuracies I’ve seen been spread on Twitter and elsewhere.

Patches were belatedly approved for OpenJDK 7u. OpenJDK 6 is not affected.

Running Java code from the command-line is quite different from running it via a browser plugin. In the latter situation, the user generally does not invoke the code and it runs in a sandbox with a much restricted set of privileges. Security issues occur when ways are found of achieving privilege escalation and being able to do thiings from the browser plugin that shouldn’t be allowed, such as invoking a program on the user’s computer. Bugs that allow this have a much higher security impact. Such escalation is fairly irrelevant when running Java from the command line as generally users run without a security manager and the code has full privileges anyway.

It is generally advisable to only run plugins in the browser that are needed (this applies to both Java and others such as Flash) and, where possible, whitelists should be used so that plugins are only used on pages approved by the user (of course, this depends on how informed the user is about giving such approval). So, all these advisories to turn off the Java browser plugin have some merit, as if you don’t use the plugin, you won’t be hit by browser-based exploits from either this issue or any future issues which may occur. Some people, of course, have no choice but to use the plugin, as some sites they use require it. In these situations, the plugin should only be used on those sites and disable for others; browsers such as Firefox and Chromium are now starting to provide users with more options (such as ‘click to play’) as to when and where plugins are invoked, and this will also help with security issues.

As always, any opinions expressed here are my own, and not those of Red Hat, Inc.

Thanks to Matthias Klose, we just discovered that building Zero with the recent 2.3.4 release is broken (as is the earlier 2.3.3 release). Zero on 2.3.x uses the HotSpot from the 2.1.x tree (which includes the ARM32 assembler port), and, when we backported 7158800 in 2.1.3, we broke the application of 6924259 to this HotSpot in 2.3.3. This changeset, just applied to the 2.3 branch, fixes the issue. It will be included in the eventual 2.3.5 release, but, if you want Zero on 2.3.4 now, you’ll need to apply this patch yourself. Sorry for the inconvenience.

The IcedTea project provides a harness to build the source code from OpenJDK using Free Software build tools, along with additional features such as a PulseAudio sound driver and support for alternative virtual machines.

These releases update our OpenJDK7 support to include the latest security updates just released:

In addition, IcedTea includes the usual IcedTea patches to allow builds against system libraries and to support more estoric architectures.

If you find an issue with one of these releases, please report it in our bug database under the appropriate component. Development discussion takes place on the OpenJDK distro-pkg-dev mailing list and patches are always welcome.

Full details of the releases can be found below.

What’s New?

New in release 2.3.4 (2013-01-15)

  • Security fixes
  • Backports
    • S7197906: BlockOffsetArray::power_to_cards_back() needs to handle > 32 bit shifts
  • Bug fixes
    • G422525: Fix building with PaX enabled kernels.

New in release 2.2.4 (2013-01-15)

New in release 2.1.4 (2013-01-15)

The tarball can be downloaded from

SHA256 checksums:

  • 7762ce53479e49f8afffc81621515eb6c3f765c578ff13d4c601ce4af8935db6 icedtea-2.1.4.tar.gz
  • 6fd07ef223de0a24428384f56c848ce5e33e1030749de920adade570218f9ef3 icedtea-2.2.4.tar.gz
  • ea859f37fb20904ffd40802a41396326f7e301fa6873d88d01bf4afef5a60ca8 icedtea-2.3.4.tar.gz

Each tarball is accompanied by a digital signature available at the above ‘sig’ link. This is produced using my public key. See details below.

The following people helped with these releases:

We would also like to thank the bug reporters and testers!

To get started:

$ tar xzf icedtea-${version}.tar.gz
$ cd icedtea-${version}

where ${version} is the version you’ve downloaded.

Full build requirements and instructions are in INSTALL:

$ ./configure [--with-parallel-jobs --enable-pulse-java
--enable-systemtap ...]
$ make

Happy hacking!

The IcedTea project provides a harness to build the source code from OpenJDK using Free Software build tools, along with additional features such as a PulseAudio sound driver and support for alternative virtual machines.

A new set of security releases is now available:

  • IcedTea6 1.10.10
  • IcedTea6 1.11.5
  • IcedTea7 2.1.3
  • IcedTea7 2.2.3
  • IcedTea7 2.3.3

We recommend that users upgrade to the latest release from the appropriate branch as soon as possible.

All updates contain the following security fixes:

The following fix is backported from 2.3.x to all other releases:

  • S7158800: Improve storage of symbol tables

Updates for OpenJDK6 also include:

  • S7176337: Additional changes needed for 7158801 fix

Updates for OpenJDK7 also include:

We believe that the 2.3.3 release takes IcedTea beyond u9[*], providing security updates from u7 and u9 on top of an OpenJDK7 u6 base, along with additional IcedTea patches to allow builds against system libraries and to support more estoric architectures.

Please note support for alternative VM solutions (CACAO, Shark, Zero) may be lacking in this release, as there has been little time for testing non-standard builds, and Zero is known to not work with 2.2.x (and only with 2.3.x via using the HotSpot from 2.1.x). Patches are welcome; please contact the mailing list and/or file bugs under the appropriate component. An update release may follow to correct issues with these builds, if necessary, but we deem it important to get the security updates out for mainstream builds as quickly as possible without further delay.

Full details of each release can be found below.

[*] It is difficult to make authoritative statements about u9 as the release
is proprietary. Oracle still do not provide GPL binaries based on OpenJDK.

What’s New?

New in release 1.10.10 (2012-10-16)

New in release 1.11.5 (2012-10-16)

New in release 2.1.3 (2012-10-17)

New in release 2.2.3 (2012-10-17)

New in release 2.3.3 (2012-10-17)

The tarballs can be downloaded from:

SHA256 checksums:

  • 644804a85b5b446d7840e3d11adf45782d73fcd880a2df5403c53c96cc288c3e icedtea6-1.10.10.tar.gz
  • 258d81d957f8ab9322fbaf7c90647f27f6b4e675504fa279858e6dfe513f7574 icedtea6-1.11.5.tar.gz
  • 1929e57eb6718d30735e1e04e9e129457f845f7d7a8404b2b028740d0779ddb6 icedtea-2.1.3.tar.gz
  • 4397ef71a0d729521be70f920bfc3fb6aec3455f1619b538cea75df512df1a16 icedtea-2.2.3.tar.gz
  • e5ac5564e00c4a8d7b3376ed6de91b18a2587c8abdad802ccc92c780765b1073 icedtea-2.3.3.tar.gz

Each tarball is accompanied by a digital signature (see above links). This is produced using my public key. See details below.

The following people helped with these releases:

We would also like to thank the bug reporters and testers!

To get started:

$ tar xzf icedtea-${ver}.tar.gz

Full build requirements and instructions are in INSTALL:

$ mkdir icedtea6-build
$ cd icedtea6-build
$ ../icedtea6-${ver}/configure [--enable-zero --enable-pulse-java --enable-systemtap ...]
$ make

Happy hacking!

We are pleased to announce the release of IcedTea 2.1.2, based on OpenJDK7 u2, and IcedTea 2.2.2, based on OpenJDK7 u4, with additional security fixes.

The IcedTea project provides a harness to build the source code from OpenJDK using Free Software build tools, along with additional features such as a PulseAudio sound driver and support for alternative
virtual machines.

These releases includes fixes for the zero-day issues that arose this week:

Patches are welcome; please contact the mailing list (distro-pkg-dev at openjdk.java.net) and/or file bugs under the appropriate component.

Full details of the release can be found below.

What’s New?

New in release 2.2.2 (2012-08-31)

  • Security fixes
  • OpenJDK
    • Fix Zero FTBFS issues
    • PR1101: Undefined symbols on GNU/Linux SPARC
    • S7180036: Build failure in Mac platform caused by fix # 7163201
    • S7182135: Impossible to use some editors directly
    • S7183701: [TEST] closed/java/beans/security/TestClassFinder.java – compilation failed
    • S7185678: java/awt/Menu/NullMenuLabelTest/NullMenuLabelTest.java failed with NPE
    • S7188168: 7071904 broke the DEBUG_BINARIES option on Linux
    • S7190813: (launcher) RPATH needs to have additional paths

New in release 2.1.2 (2012-09-02):

  • Security fixes
  • OpenJDK
    • PR1101: Undefined symbols on GNU/Linux SPARC
    • S7182135: Impossible to use some editors directly
    • S7183701: [TEST] closed/java/beans/security/TestClassFinder.java – compilation failed
    • S7185678: java/awt/Menu/NullMenuLabelTest/NullMenuLabelTest.java failed with NPE
    • S7190813: (launcher) RPATH needs to have additional paths
  • ARM
    • ARM: Fix trashed thread ptr after recursive re-entry from
    • ARM: Rename a bunch of misleadingly-named functions
    • Enable _adapter_opt_spread* jsr 292 code, now passes
    • Fix call to handle_special_method(). Fix compareAndSwapLong.

The tarballs can be downloaded from:

SHA256 checksums:

  • c7ebdb84581dca48a4389e12790d2d506b9cfc05f16612169284d5a5e3a02269 icedtea-2.1.2.tar.gz
  • e645fdcae825e0c60093962cb0a8fbf194c94a5e669162b3b357d99a6e36c86d icedtea-2.2.2.tar.gz

Each tarball is accompanied by a digital signature (see above links). This is produced using my public key. See details below.

The following people helped with these releases:

We would also like to thank the bug reporters and testers!

To get started:

$ tar xzf icedtea${ver}.tar.gz
$ cd icedtea${ver}

Full build requirements and instructions are in INSTALL:

$ ./configure [--enable-zero --enable-pulse-java --enable-systemtap ...]
$ make

Happy hacking!

« Previous PageNext Page »