I browsed the code busybox/syslogd.c. I found that in create_socket() they are using UDP protocol " xsocket(AF_UNIX, SOCK_DGRAM, 0);" Please let me know whether the syslogd should be upgraded to support TCP or existing will work.
Regards, Girish -----Original Message----- From: Christoph Gysin [mailto:[email protected]] Sent: Friday, December 04, 2015 12:49 AM To: Girish Kumar Cc: [email protected]; [email protected] Subject: Re: TLS support for syslog in busybox Yes, it does: $ busybox syslogd --help BusyBox v1.24.1 (2015-10-24 21:37:54 MSK) multi-call binary. Usage: syslogd [OPTIONS] ... -R HOST[:PORT] Log to HOST:PORT (default PORT:514) On Thu, Dec 3, 2015 at 5:46 PM, Girish Kumar <[email protected]> wrote: > Thanks all for the information. > > Stunnel expects TCP-based syslog. Please let me know whether syslogd of > busybox supports TCP communication. > > Regards, > Girish > > -----Original Message----- > From: busybox [mailto:[email protected]] On Behalf Of > Christoph Gysin > Sent: Thursday, December 03, 2015 7:55 PM > To: [email protected] > Cc: [email protected] > Subject: Re: TLS support for syslog in busybox > >> If you really need it you may consider tunneling via ssh/busybox. > > Or for TLS, use stunnel: > https://www.stunnel.org > > Chris > _______________________________________________ > busybox mailing list > [email protected] > http://lists.busybox.net/mailman/listinfo/busybox -- echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3 _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
