syslog-ng with SSL/TLS encrypted messages

[ab@novell.com]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Using stunnel or some type of socat/cryptcat application to SSLize the
data is pretty easy to do. The Novell OES 2 collector for Novell Sentinel
does this I believe so the instructions contained therein may be uuseful
for you at least as long as you avoid the parts that are OES-specific:

http://support.novell.com/products/s...entinel61.html

Look at the OES 2 collector documentation at the link above.

Good luck.





tlemons wrote:
> Hi
>
> I'm using SLES 10 SP2. On my system, I'm running syslog-ng v1.6.8.
> I've heard that syslog-ng allows remote logging to use SSL/TLS to
> encrypt the messages sent between the local and the remote logging
> system. But, according to
> http://www.balabit.com/dl/white_pape...ectures-en.pdf,
> p. 11, the TLS feature of syslog-ng is only available with Balabit's
> syslog-ng Premium Edition product. Can anyone confirm that the
> syslog-ng offered in SLES does NOT provide SSL/TLS encryption of the
> messages sent between syslog servers?
>
> If that's true, are there other ways to make this happen (I've seen
> stunnel referenced, but am not sure if that was as a solution to my
> problem)?
>
> Thanks!
> tl
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJK73EbAAoJEF+XTK08PnB5dQoQAJBJzHwAl+ m2jQYCl3OksCAx
Eqw/uK5WuXjpeXtnfxNaQAGdbeD9qt2jceQDlJ2kJ1DKIgsLYAZa1P fnwn9Pqcqi
49c245R1FrSSv0nQPWeaDTuxbS29LdD5Ne8x7txVVQjinfR67Z QlSXdkn4E1N/al
697bTSX+Bj0k9PYU8zRP1Ie26vrlFtCTfKNIhHJE4w4VYz3Lpv ZEiIozr14SB3Db
a8h/eNxiemAmL7opslXWulh6gSCg7bDZpEbcbWIHneYUDhc7/pqaBVLqvw5d6dzI
ao3OjhhHa8Df85xf7xgune6OCvkLwlz2yvr3o33pXwGh8IV+dx 9IA8nbJcJu76Ai
ue8QIh7zXxlzv2rFhgUWhJGrOFR5+qaabmYXZd3qkWhGTFPe5f 2AHRa5y2PBcOQ0
7cNK+63j7Nb8+o43DiasLKifWYJcrJMF25AnafHOJbsio0+JPD v0tb21o+Rn9zX0
mvHwF0KslQ2Hhg7cCHxe40zP9ODw5mpPMcmm4U+ynFU2Qesf+N 1vwt5ue3Hs1XT0
MW7kh+ZtIW4R4kz0n65dUVr1iw5++TDz8ng4rOmKhwcGmy7C+g iV+4yr4PKakckl
eoLV06lFs8uOkMwODY8zyVQBu/MwHoSO6fZwCcQB6fF1WteoltGFdPNibDSBIcMK
CCkb1iYwWSOSCHhmtwg5
=Yl/5
-----END PGP SIGNATURE-----