Skip to content

Releases: Openwsman/openwsman

Version 2.6.6 - OpenSSL 1.1.0 support

12 Oct 10:09
Compare
Choose a tag to compare

This release provides OpenSSL 1.1.0 compatibility

Version 2.6.5 - Python3 and Ruby 2.5

28 Nov 14:47
Compare
Choose a tag to compare

This release supports Python3 and Ruby 2.5 for the bindings component.

  • Bugfixes
    • Replace obsolete pam modules with standard ones (kukuk@suse.de)
    • Include shttpd_config.h in tarball (olaf@aepfle.de)
    • Build with Python 3
    • Build with Ruby 2.5

Version 2.6.4 - security update

07 Nov 12:22
Compare
Choose a tag to compare

This update fixes CVE-2016-2183 (aka 'sweet32')

  • Bugfixes
    • setup ECDHE to allow Perfect Forward Secrecy, using the p256 NIST prime curve (CVE-2016-2183)(mmeissner)

Version 2.6.3

21 Jun 11:38
Compare
Choose a tag to compare

This is a bugfix/cleanup release

  • Bugfixes
    • Prevent buffer overflow if digest realm too long
    • Ensure path starts with '/' in client data endpoint
    • Java bindings build fix
    • Fix SSL library, usage is not thread safe (vcrhonek)
    • Improve NetBSD and OSX builds (apjanke)
    • Install winrs with correct name and permissions

Version 2.6.2

19 Oct 13:39
Compare
Choose a tag to compare

The most important bugfix of this release is the thread-safety of iniparser, which could crash when reading the openwsman.conf file.

Fixing the selector extraction from URI query allows to specific an instance as resource URI + key properties within a single URI in wsman.

  • Features
    • Install winrs.rb (Windows Remote Shell) to /usr/bin
    • New package: winrs
  • Bugfixes
    • Make iniparser thread-safe (Emil Bartczak)
    • Fix excessive RPM rebuilds (Olaf Hering)
    • Fix selector extraction from URI query (Markus Kolb)
    • Fix RPM building on older distributions
    • Fix RPM building on Fedora 22

Version 2.6.1

28 Aug 08:16
Compare
Choose a tag to compare

This release contains two important fixes, one of them disguised as a feature.

With multithreading client applications, the libcurl backend might crash if DNS lookups time out. This is due to the way libcurl handles timeouts using setjmp, longjmp, and signals.
openwsman_client.conf now provides an option curlopt_nosignal within the [client] section to work around that crash. Setting curlopt_nosignal = 1 prevents these crashes at the risk of hanging DNS lookups.
See http://curl.haxx.se/libcurl/c/CURLOPT_NOSIGNAL.html for details.

The other fix is in dictionary_get() of iniparser.c which can crash in strcmp if a NULL pointer is passed. This bug has been there all the years and probably got triggered due to new versions of GCC.

From the ChangeLog:

  • Features
    • Add curlopt_nosignal option to openwsman_client.conf to prevent
      CURL crashes in multithreaded client applications
    • Limit EnvelopeSize to 32767 if wsman:MaxEnvelopeSize not set in
      request (WS-Man 1.2 compatibility) (Prabhakar Pujeri)
  • Bugfixes
    • fix memory leaks (Vitezslav Crhonek)
    • honor client:agent from openwsman_client.conf
    • fix possible crash in dictionary_get()

Version 2.6.0

09 Jun 10:36
Compare
Choose a tag to compare

Main feature of this release is support for Section 6.3 (wsman:Locale) of DSP 0226 (aka WS-Management standard)

The downside is a size change of the client_opt_t structure, requiring a so version increase for libwsman-client.

Special thanks to Prabhakar Pujeri for this release !

Version 2.5.2

03 Jun 08:22
Compare
Choose a tag to compare

This version provides native Python packaging, see http://openwsman.github.io

Version 2.5.1

02 Jun 15:13
Compare
Choose a tag to compare

This release adds RFC1866 support in allowing ; as a separator for resource uri query parameters (selectors).
It also prints a warning if a resource URI (wrongly) uses , as query parameter separator.

Do NOT use http://...?Foo="Bar",Baz="Boo",...
Use http://...?Foo="Bar"&Baz="Boo"&... or http://...?Foo="Bar";Baz="Boo";...

Version 2.5.0

02 Jun 15:07
Compare
Choose a tag to compare

Version 2.5.0 completely rewrites the handling of key/value pairs for selectors and properties. This brings a breakage of an internal(!) API which was used by wsmancli.
The .so version of libwsman was therefore increased to 3. wsmancli was fixed to use public APIs only.

You must upgrade wsmancli to 2.5.0 (or later) together with Openwsman

  • Rewrite selector and property handling to keep
    them in order (#49)
    Selectors and properties can now handle EndpointReferences
    as values. This increases compatibility with Intel AMT 7.0
    and later.
  • ABI change, .so version 3
  • Ruby: Add EndPointReference#to_s