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
LibLogging 1.0.3 released
liblogging 1.0.3 [download]
We have released liblogging 1.0.3.
v1.0.3 2014-03-18
– fix build problem in Ubuntu 10.04
Thanks to Assaf Gordon for reporting
See: https://github.com/rsyslog/liblogging/issues/11
– do not override user varibale CFLAGS
Thanks to Thomas D. for reporting this problem and suggesting a solution.
closes: https://github.com/rsyslog/liblogging/issues/15
– make liblogging-rfc3195 not export private symbols
Thanks to Michael Biebl for his help in getting this right.
– explain that stdlog_log() return code usually most not be checked
(if same level of reliability like syslog(3) is desired)
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.
– 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
LibLogging 1.0.2 released
liblogging 1.0.2 [download]
We have released liblogging 1.0.2.
The man page for the standard logging library is available at
https://github.com/rsyslog/liblogging/blob/master/stdlog/stdlog.rst
Please report issues and feature requests to
https://github.com/rsyslog/liblogging/issues
Note: if the journal driver is to be build (enabled by default), a new dependency libsystemd-journal exists. This is the required to use the journal API. You can turn off building the journal driver via the –disable-journal configure option.
sha256sum: 1fecfdc506ee937c21c30d868c76842506dc34ea5eb168b81fd11eb9483e4388
LibLogging 1.0.1 released
liblogging 1.0.1 [download]
This version primarily clarifies the licensing and fixes some packaging issues. Otherwise, it is identical to 1.0.0.
Changelog:
v1.0.1 2014-02-10
– rfc3195 component now 2-clause BSD licensed
This means the complete liblogging is now under 2-clause BSD
– new component names:
* liblogging-stdlog
* liblogging-rfc3195
made some necessary name adjustments
See also: https://github.com/rsyslog/liblogging/issues/2
sha256sum: 99d09101cc3c22e2388fe2a817bb1c6f5fe2275623aadb94a49d1c2259102bfa
LibLogging 1.0.0 released
liblogging 1.0.0 [download]
We have released liblogging 1.0.0.
This release now has the rfc3195 library as optional component and we added the libstdlog component which is used for standard logging.
sha256sum: b74b456e21d08465dc5a52b1bbbc6a00caa313186cea4751c6eccf468fc84cfa
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
How to Contribute to rsyslog?
Rsyslog is a real open source project and open to contributions. By contributing, you help improve the state of logging as well as improve your own professional profile. Contributing is easy, and there are options for everyone – you don’t need to be developer.
These are many ways to contribute to the project:
- become a rsyslog ambassador and let other people know about rsyslog and how to utilize it for best results. Help rsyslog getting backlinks, be present on Internet news sites or at meetings you attend.
- help others by offering support on
- help with the documentation; you can either contribute
- to the rsyslog doc inside the project git
- to the rsyslog project web site — just ask us for account creation
- on the rsyslog wiki
- become a bug-hunter and help with testing rsyslog development releases
- help driving the rsyslog infrastructure with its web sites, wiki’s and the like
- help creating packages
- or, obviously, help with rsyslog code development
This list is not conclusive. There for sure are many more ways to contribute and if you find one, just let us know. We are very open to new suggestions and like to try out new things.
We have also some more in-depth information on specific contribution topics available and more is upcoming. Right now, dig down into
Again, your contribution is highly appreciated, and very rewarding. Participate in the open source movement!
Contribution Policy
Rsyslog is very open to contributions and they are highly appreciated. Basically, we accept any contribution that can potentially be of use for the rsyslog community. Documentation and code contributions are especially welcome. A successful contribution should
- come under the Apache Software License (ASL) 2.0; much of rsyslog’s code already has been converted to this license, but not everything yet. So please make sure you feel OK with ASL 2.0. We generally do not like GPL contributions any longer, as this causes trouble with the long-term goal of changing to ASL.
- provide a bugfix or feature that is -at least potentially- of general interest. If it’s really just for you and so specific that nobody else will ever want it, chances are a bit lower we’ll merge (except, of course, if it is an interesting PoC).
- a bit of documentation for new features or modules would be immensely useful. While we usually merge even without that, this actually means nobody will ever know about that particular new feature (we are way behind with doing our own doc, don’t expect us to document any other work ;)).
- do not break upward compatibility; if you really need to, discuss this on the rsyslog mailing list first
- do not unnecessarily duplicate a module; while we tend to accept such contributions, the process can take much longer as we will try to merge the functionality into the alread existing module
- if you contribute a new module with some non-standard tools, do not expect that we actually try the module out. We’ll usually merge it, but will flag it as non-project-supported and name the original author as contact points. Omoracle is one example. Don’t be put off contributing such a module — they can be immensly useful to the community, we just can’t work on all of them. If things become popular, we may involve ourselfs into it (ommongodb is an example for that).
- doc contributions should not be primarily promotional for some third party. If you contribute something you have originally written for another party, it’s usualy fine to include a “orignaly appeared on” backlink, but that should be sufficient.
As usual, these are just some general rules, and most of them common knowledge in any case. In simple words it’s very hard to find a reason NOT to merge a serious contribtion.