All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
The 4.7 release was led by Andrea Pascarelli (4Science) and the Committers.
The following individuals provided code or bug fixes to the 4.7 release: Pascal-Nicolas Becker (pnbecker), Andrea Bollini (abollini), Andrea Pascarelli (lap82)
Note | ||
---|---|---|
| ||
DSpace 4.6 contain security fix for both the XMLUI and JSPUI. To ensure your 4.x site is secure, we highly recommend ALL DSpace 4.x users upgrade to DSpace 4.6. DSpace 4.6 upgrade instructions are available at: Upgrading DSpace |
...
The 4.6 release was led by Andrea Pascarelli (4Science) and the Committers.
The following individuals provided code or bug fixes to the 4.6 release: Pascal-Nicolas Becker (pnbecker), Andrea Bollini (abollini), Roeland Dillen (rradillen), Tim Donohue (tdonohue), Bram Luyten (bram-atmire), Andrea Pascarelli (lap82), Mark Wood (mwoodiupui)
Note | ||
---|---|---|
| ||
Note | ||
| ||
DSpace 4.5 contains security fixes for both the XMLUI and JSPUI. To ensure your 4.x site is secure, we highly recommend ALL DSpace 4.x users upgrade to DSpace 4.5. DSpace 4.5 upgrade instructions are available at: Upgrading DSpace |
...
The 4.5 release was led by Tim Donohue (DuraSpace) and the Committers.
The following individuals provided code or bug fixes to the 4.5 release: Andrea Bollini (abollini), Tim Donohue (tdonohue), Ivan Masar (helix84), Mark Wood (mwoodiupui)
Note | ||
---|---|---|
| ||
DSpace 4.4 contains security fixes for the JSPUI only. To ensure your 4.x site is secure, we highly recommend JSPUI DSpace 4.x users upgrade to DSpace 4.4. |
...
The 4.4 release was led by Tim Donohue (DuraSpace), Andrea Schweer (U of Waikato) and the Committers.
Note | ||
---|---|---|
| ||
DSpace 4.3 contains security fixes for both the XMLUI and JSPUI. To ensure your 4.x site is secure, we highly recommend all DSpace 4.x users upgrade to DSpace 4.3. We also highly recommend removing any "allowLinking=true" settings from your Tomcat's <Context> configuration. Previously our installation documentation erroneously listed examples which included "allowLinking=true", while the Tomcat documentation lists it as a possible security concern. The XMLUI Directory Traversal Vulnerability (see below) is also exacerbated by this setting. |
DSpace 4.3 is a security fix release to resolve several issues located in DSpace 4.x. As it only provides security-fixes, DSpace 4.3 should constitute an easy upgrade from DSpace 4.x for most users. No database changes or additional configuration changes should be necessary when upgrading from DSpace 4.x to 4.3.
This release addresses the following security issues discovered in DSpace 4.x and below:
The following individuals provided code or bug fixes to the 4.4 release: Pascal-Nicolas Becker (pnbecker), CTU Developers (ctu-developers), Roeland Dillen (rradillen), Tim Donohue (tdonohue), Àlex Magaz Graça (rivaldi8), Bram Luyten (bram-atmire), Ivan Masar (helix84), Christian Scheible (christian-scheible), Andrea Schweer (aschweer), Jonas Van Goolen (jonas-atmire), Mark Wood (mwoodiupui)
Note | ||
---|---|---|
| ||
DSpace 4.3 contains security fixes for both the XMLUI and JSPUI. To ensure your 4.x site is secure, we highly recommend all DSpace 4.x users upgrade to DSpace 4.3. We also highly recommend removing any "allowLinking=true" settings from your Tomcat's <Context> configuration. Previously our installation documentation erroneously listed examples which included "allowLinking=true", while the Tomcat documentation lists it as a possible security concern. The XMLUI Directory Traversal Vulnerability (see below) is also exacerbated by this setting. |
DSpace 4.3 is a security fix release to resolve several issues located in DSpace 4.x. As it only provides security-fixes, DSpace 4.3 should constitute an easy upgrade from DSpace 4.x for most users. No database changes or additional configuration changes should be necessary when upgrading from DSpace 4.x to 4.3.
This release addresses the following security issues discovered in DSpace 4.x and below:
[HIGH SEVERITY] XMLUI Directory Traversal Vulnerabilities (DS-2445 - requires a JIRA account to access for two weeks, and then will be public): These vulnerabilities allow someone to potentially access any file on your local filesystem which is readable to the Tomcat user account. This includes files which are unrelated to DSpace or Tomcat, but are readable to all users on the filesystem (e.g. /etc/passwd, /etc/hosts, etc.). This also includes Tomcat configuration files (which may or may not contain passwords). These vulnerabilities have existed since DSpace 1.5.2.
Discovered by: Khalil Shreateh, with additional (related) vulnerabilities discovered by the DSpace Committer Team
[HIGH SEVERITY] XMLUI Directory Traversal Vulnerabilities (DS-2445 - requires a JIRA account to access for two weeks, and then will be public): These vulnerabilities allow someone to potentially access any file on your local filesystem which is readable to the Tomcat user account. This includes files which are unrelated to DSpace or Tomcat, but are readable to all users on the filesystem (e.g. /etc/passwd, /etc/hosts, etc.). This also includes Tomcat configuration files (which may or may not contain passwords). These vulnerabilities have existed since DSpace 1.5.2.
Discovered by: Khalil Shreateh, with additional (related) vulnerabilities discovered by the DSpace Committer Team
The 4.3 release was led by Tim Donohue (DuraSpace) and the Committers.
DSpace 4.2 provides bug-fixes and minor improvements to the 4.x platform. As it only provides bug-fixes, DSpace 4.2 should constitute an easy upgrade from DSpace 4.x for most users. No database changes or additional configuration changes should be necessary when upgrading from DSpace 4.x to 4.2 (except for DS-2036 which may affect some Oracle users ; see Fixing the effects of DS-2036 ).
Issues which have been resolved in 4.2 include:
Fixed occasional "Out of Memory" errors when indexing large bitstreams/files in Discovery (DS-1958)
Fixed issue where REST API was not releasing "context" and ignored database pooling (DS-1986)
Fixed Solr commit delays when "did you mean" functionality is enabled in Discovery (DS-2060)
Fixed the "dspace classpath" command (DS-1998)
Fixed issue where thumbnails were not displayed when using JSPUI + Oracle database (DS-2013)
The 4.2 release was led by Robin Taylor (U of Edinburgh) and the Committers.
DSpace 4.1 provides bug-fixes and minor improvements to the 4.x platform. As it only provides bug-fixes, DSpace 4.1 should constitute an easy upgrade from DSpace 4.x for most users. No database changes or additional configuration changes should be necessary when upgrading from DSpace 4.x to 4.1 (except for DS-1536; see Fixing the effects of DS-1536).
Issues which have been resolved in 4.1 include:
The 4.3 release was led by Tim Donohue (DuraSpace) and the Committers.
The following individuals provided code or bug fixes to the 4.3 release: Terry Brady (terrywbrady), Roeland Dillen (rradillen), Tim Donohue (tdonohue), Ivan Masar (helix84), Andrea Pascarelli (lap82), Avi Romanoff (aroman), Christian Scheible (christian-scheible), Robin Taylor (robintaylor)
DSpace 4.2 provides bug-fixes and minor improvements to the 4.x platform. As it only provides bug-fixes, DSpace 4.2 should constitute an easy upgrade from DSpace 4.x for most users. No database changes or additional configuration changes should be necessary when upgrading from DSpace 4.x to 4.2 (except for DS-2036 which may affect some Oracle users ; see Fixing the effects of DS-2036 ).
Issues which have been resolved in 4.2 include:
Fixed occasional "Out of Memory" errors when indexing large bitstreams/files in Discovery (DS-1958)
Fixed issue where REST API was not releasing "context" and ignored database pooling (DS-1986)
Fixed Solr commit delays when "did you mean" functionality is enabled in Discovery (DS-2060)
Fixed the "dspace classpath" command (DS-1998)
Fixed issue where thumbnails were not displayed when using JSPUI + Oracle database (DS-2013)
The 4.2 release was led by Robin Taylor (U of Edinburgh) and the Committers.
The following individuals provided code or bug fixes to the 4.2 release: Pascal-Nicolas Becker (pnbecker), Peter Dietz (peterdietz), Roeland Dillen (rradillen), Tim Donohue (tdonohue), Denis Fdz, Keith Gilbertson (keithgee), Panagiotis Koutsourakis (kutsurak), Bram Luyten (bram-atmire), Mini-Pillai, Ivan Masar (helix84), Thomas Misilo (misilot), Hardy Pottinger (hardyoyo), Antoine Snyers (antoine-atmire), Robin Taylor (robintaylor), Kevin Van de Velde (KevinVdV), Mark Wood (mwoodiupui)
DSpace 4.1 provides bug-fixes and minor improvements to the 4.x platform. As it only provides bug-fixes, DSpace 4.1 should constitute an easy upgrade from DSpace 4.x for most users. No database changes or additional configuration changes should be necessary when upgrading from DSpace 4.x to 4.1 (except for DS-1536; see Fixing the effects of DS-1536).
Issues which have been resolved in 4.1 include:
The 4.1 release was led by Mark Wood (IUPUI) and the Committers.
The 4.1 release was led by Mark Wood (IUPUI) and the Committers.The following individuals provided code or bug fixes to the 4.1 release: Andrea Bollini (abollini), Roeland Dillen (rradillen), Tim Donohue (tdonohue), Àlex Magaz Graça (rivaldi8), Panagiotis Koutsourakis (kutsurak), marsaoua, Ivan Masar (helix84), João Melo (lyncodev), Thomas Misilo (misilot), Andrea Pascarelli (lap82), Adán Román Ruiz, Andrea Schweer (aschweer), Kim Shepherd (kshepherd), Kostas Stamatis (kstamatis), Kevin Van de Velde (KevinVdV), Mark Wood (mwoodiupui)
The following is a list of the new features included for the 4.x platform (not an exhaustive list):
...