faspex 2.0.5 Release Notes

faspex 2.0.5 Release Notes
Version 2.0.5
Created: February 22, 2011
 
What’s New
  • Added the ability to manually stop ongoing package relays and restart failed package relays (#8799)
  • Enabled TLS support for active directory connections (#8819)
  • Update net-ldap library to latest version to support LDAP over TLS
  • Enabled AD account login on slave via the master server (#8932)
  • Enabled choice of AD property to use as faspex username


Fixed Issue
  • Fixed multiple security-related issues
  • Fixed several issues related to user attributes
  • Fixed inability to reorder home server rules (#8597, #8598)
  • Made post-processing page inaccessible with post-processing disabled in the configuration file (#8544)
  • Fixed issue with failed package relays not being retried (#8754)
  • Fixed issue with disappearing package relay status message (#8784)
  • Fixed handling of backslash-escaped commas in AD distinguished names (#8820)
  • Prevented AD users from changing their email addresses by crafting a POST request (#8883)
  • Fixed incorrect handling of apostrophe character in package metadata field names (#9039)
  • Fixed loss of forwarded note when forwarding a package from master server to slave server (#9062)
  • Removed "(relay)" prefix from package name in transfer cookies for relays
  • Fixed handling of commas in package names (#8946)


Known Issues

Package Information
MD5 Cksums:
  • 1588AD7A13561A9D52B775C489C98A34  aspera-common-1.1.2.36006-0.i386.rpm
  • 83BD988C5971F56C2F5BA26CEE890339  aspera-common-1.1.2.36006-0.x86_64.rpm
  • A0A7C59FC2A0CD65D33D0B0BF2E3D97E  aspera-faspex-2.0.5.36108-0.i386.rpm
  • C708A7811D9D6CA860B3ACD1A7F53571  aspera-faspex-2.0.5.36108-0.x86_64.rpm
  • 506387B07BA42ED8BDB32BB00A5EFA69  AsperaFaspex-2.0.5.36247-windows-32.msi


Previous Release Notes
For more information about the complete list of What's New, Fixed Issues, and Known Issues in 2.0.X, read the2.0.4, 2.0.3, 2.0.2 and 2.0.1 Release Notes.
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk