librelp 1.2.7

librelp 1.2.7 [download]

This is a bugfixing release of librelp. It fixes incompatabilities with C++ and some bugs with wildcards.

Version 1.2.7 - 2014-04-29
- bugfix: librelp was incompatible with C++ without a real reason
  Thanks to Ivan Kryak for the patch
- bugfix: potential misadressing in wildcard match
  see: https://github.com/rsyslog/librelp/pull/3
  Thanks to Sebastian Schmidt for the patch.
- bugfix: always last wildcard match was reported, not first
  see: https://github.com/rsyslog/librelp/pull/4
  Thanks to Sebastian Schmidt for the patch.

sha256sum: 3a434a1c71772706104cfb1c93ba8e6809d257851d60de29ac2142c60c68d7d1


librelp 1.2.5

librelp 1.2.5 [download]

This version of librelp allows to use anonymous TLS on platforms where GnuTLS misses certificate verification function. This permits to use at least anon TLS on platforms like RHEL and CENTOS 6.

Version 1.2.5 - 2014-03-20
- permit to use anonymous TLS on platforms where GnuTLS misses
  certificate verification function. This permits to use at least
  anon TLS on platforms like RHEL and CENTOS 6.

sha256sum: 358b2de82c9aebd4efcbab5e1ff212477fb8fa89543dbeded61aa46a23dcf12b


librelp 1.2.4

librelp 1.2.4 [download]

This version of librelp is a correction for the API/ABI change in v1.2.3. Everything else stays the same.

Version 1.2.4 - 2014-03-17
- correct API/ABI change in 1.2.3
  My reasoning was flawed, and we could run into problems with
  apps that required the new version but could not detect that an
  older one was installed.
  Thanks to Michael Biebl for pointing this out.
  What we have done is:
  - revert back to previous state (return void)
    * relpSrvEnableTLS();
    * relpSrvEnableTLSZip();
    These functions are now deprecated.
  - introduce new functions that return a state
    * relpSrvEnableTLS2();
    * relpSrvEnableTLSZip2();

sha256sum: cf4f26f9a75991eedf3eaf414280c8da3532c38e619a465d23008c714f5c1cf1


librelp 1.2.3

librelp 1.2.3 [download]

This version of librelp addresses the problem that RHEL and CENTOS provide too-old versions of GnuTLS to make support librelp's TLS functionality. To "solve" this problem, TLS can now be disabled in librelp, so that base RELP functionality is also available on those platforms.

Note that librelp previously built on those platforms, but DID NOT WORK.

Version 1.2.3 - 2014-03-13
- add ability to build librelp without TLS
  This is required on some platforms where GnuTLS is too old
  Use --disable-tls to select this mode. If set, RELP_RET_ERR_NO_TLS
  will be returned on calls that selected TLS mode.
  See also: https://github.com/rsyslog/librelp/issues/1
- API change: two functions that used to return void now return state
  these are:
  * relpSrvEnableTLS();
  * relpSrvEnableTLSZip();
  This change is acceptable because the state must not necessary be
  evaluated. If not, the same error is returned a bit later in the
  calling sequence. Having it early, however, may help with better
  error messages. So it's still optional to check.
- bugfix: configure required too-old version of GnuTLS
  This lead to successful builds which later on would not execute.

sha256sum: c06e15f94f7e75d7c9f8c66faefaf5ab8808072c828ac6982c70825fe3aa20f1


librelp 1.2.2

librelp 1.2.2 [download]

New Feature release, but new feature does not affect stability of existing features.

Version 1.2.2 - 2014-01-07
- add capability to enable tcp KEEPALIVE
- introduced new API relpSrvSetKeepAlive() to support KEEPALIVE

sha256sum: f02778d9661c4746be9c16338991e99a482e4a0018f2220e7d9da18791265f48


librelp 1.2.0

librelp 1.2.0 [download]

This version offers support for epoll() on platforms that provide it. This provides both better performance and the ability to handle many more connections. 

Version 1.2.0 - 2013-07-15
- support for epoll() added
  platforms that do not support it fall back to select()
- API extension: relpEngineSetOnGenericErr

sha256sum: 5a8870fd2ae496be08d100ef8a65807311f11d6976ed37b8e0cd8024872c31e5


librelp 1.1.5

librelp 1.1.5 [download]

This is a bug-fixing release that takes care of a memory leak on connection close as well as potential misadressing on session close.

Version 1.1.5 - 2013-07-05
- bugfix: memory leak on connection close
  around 60 bytes of memory were lost on each connection close at the
  server side (when the client initiated a close)
- bugfix: potential misadressing on session close
  This can happen if also a write was outstanding, a quite unusable
  situation. In that case, already freed memory was being accessed.

sha256sum: 2322d771bd6036dd11519509177722baa36bc0e61a5d6748cbce0addf7f43243