To continue to advance the DSpace, Fedora and VIVO projects, your institution’s financial support is critical. Please talk to your leadership about joining DuraSpace as a member! Visit: http://duraspace.org/about_membership to learn more.
Skip to end of metadata
Go to start of metadata

Version 1.8.3

DSpace 1.8.3 was officially released to the public on July 25, 2013.

DSpace 1.8.3 can be downloaded immediately at either of the following locations:

All DSpace 1.8.x JSPUI users should upgrade to 1.8.3 (or 3.2)

DSpace 1.8.3 includes a security fix for the JSPUI. Although there are no known exploits, we recommend all 1.8.x JSPUI users upgrade to 1.8.3 (or 3.2) in order to fix this vulnerability.

Summary

DSpace 1.8.3 is a security fix release to resolve a JSPUI security vulnerability in the 1.8.x platform.

This security release includes the following fixes:

  • Resolved security issue in JSPUI (DS-1603 - requires a JIRA account to access). This fix has been backported from the DSpace 3.2 release.
  • Minor cleanup of the 1.8.x codebase so that it is Git/GitHub friendly. This means that 1.8.3 can now be forked or checked out from GitHub, using either Git or Subversion

We highly recommend all 1.8.x JSPUI users upgrade to 1.8.3.

Upgrade Instructions

No new features in DSpace 1.8.3

1.8.3 is a security fix release. This means it includes no new features.

For a list of all new 1.8 Features, please visit the DSpace Release 1.8.0 Notes.

Bug Fixes

Changes

The following fixes were released in 1.8.3.

Loading

Bugs Fixed in 1.8.3 (1 issues)

Key Summary Assignee Reporter
DS-1587 Update 1.7.x and 1.8.x branches for Git/GitHub Tim Donohue Tim Donohue

This release also included a security fix (which requires a JIRA account to view):

  • DS-1603 - Resolves a security issue in JSPUI

Organizational Details

Release Coordination

  • Release Coordinator: Committers Team (shared coordination) led by Hardy Pottinger

Timeline and Proceeding

Release Timeline:

  • Release Date: July 25, 2013.

Release Process will proceed according to the following Maven release process: Release Procedure

  • No labels