Re: Syslog-sec-misc @ SF: syslog

[Martin S. <li...@ms...>]

Adam Hamsik schrieb:
> Yes syslog-sign is part of my university Diploma thesis. Yes I'm  
> NetBSD developer so one of my tasks is integration with NetBSD base  
> system. I have had quick look at our actual code base and it differs  
> in some points, I have to thing how merge them so we can work on one  
> syslog which can run on NetBSD nad FreeBSD.

I've looked at the different versions and found some main differences:
OpenBSD: splits syslogd for privilege separation
FreeBSD: 2nd socket for privileged processes and allowed peer addresses
DragonFly: adds a ring buffer
NetBSD: seems 'just' to be refactored and with more checks

A merge of current FreeBSD and NetBSD code could be a first step.
I am just afraid it might become a political issue early on ;-)

>> Today you are applying; that nice. You can become developer  #3
> Cool:)

My SF.net-ID is 'slyh'.

> I think that there are 2-3 major tasks on which We should work

Just for information; my current GSoC application includes as a rough 
schedule:
- TLS transport
- local buffer to bridge lost connectivity
- syslog-protocol in syslogd(8)
- syslog-protocol in syslog(3)
- test & debug
- read/check existing syslog-sign
- integrate syslog-sign
- new library function
- review options and configuration

Two possible extensions are:
- reliable local delivery with a yet to be implemented
socket(PF_LOCAL, SOCK_SEQPACKET, 0)
- D. Spinellis pointed me to Apple's asl(3) API which is intended to 
replace syslog(3). Implementing these functions is probably better than 
inventing a new API for syslog-protocol. 
(http://developer.apple.com/documentation/Darwin/Reference/ManPages/man3/asl.3.html)

Accepted GSoC-proposals are announced on April 21st. Then I will know if 
I can afford to work on this full time.

-- 
Martin