Is it safe to run the non premium version of syslog-ng? (The one that doesnt use ssl)
Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is it safe to run the non premium version of syslog-ng? (The one that doesnt use ssl)
Is it safe to run the non premium version of syslog-ng? (The one that doesnt use ssl)
Quote:
The syslog-ng Premium Edition is the direct descendant of the opensource syslog-ng project that started ten years ago. This branch is developed as a commercial product. The premium edition offers the following benefits:
Secure logging using SSL/TLS
Encrypt sensitive data: Log messages may contain sensitive information that should not be accessed by third parties. Therefore, syslog-ng Premium Edition uses the Transport Layer Security (TLS) protocol to encrypt the communication. TLS also allows the mutual authentication of the host and the server using X.509 certificates.
If your concern is that the data is transmitted in cleartext form, you can easily overcome that by setting up Stunnel. IIRC, newer versions of OpenSSH also make this a lot simpler than it was with previous ones - so that's yet another option.
If you are interested in the privacy options, you may also want to have a look at rsyslog. Rsyslog in the most recent version also support TLS natively, and supports GSSAPI for quite a while. rsyslog is all-GPL, so it is free to use. You can find a comparison to syslog-ng here:
If you are interested in the privacy options, you may also want to have a look at rsyslog. Rsyslog in the most recent version also support TLS natively, and supports GSSAPI for quite a while. rsyslog is all-GPL, so it is free to use. You can find a comparison to syslog-ng here:
Moved: The posts in this thread about phpLogCon (taxonomy: not related to OP > not Security > compile-time errors > Software) are more suitable as thread in the Software forum and has been moved accordingly to help your thread/question get the exposure it deserves. Please continue that part of the discussion at http://www.linuxquestions.org/questi...error.-646889/.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.