In some email I received from Magosanyi Arpad, sie wrote: > > A levelez�m azt hiszi, hogy Darren Reed a k�vetkez�eket �rta: > > In some email I received from Daniel Wesemann, sie wrote: > > [...] > > > hmm. would be nice if both sides could *start* the connection, too > > > (configurable). > > > if you want to transfer the logs from an agent which is located on a > > > system "outside" of a firewall, it would be nice to have the "inside" > > > system (the logserver) initiate the connection. we firewall guys get > > > nervous when some tool requires inbound tcp on the firewall... > > > > I would think that these are implementation problems. > > No, it is a protocol issue. You should have a way to initiate the > connection both from the sender and the receiver side. So you're saying your requirements are: - peer authentication (fine) - client-server connections initiated by the server The later is a completely different way of thinking about this problem... hmm. syslog server connects to another syslog server and says "send me this and that." Is this a better model, in terms of protocol, than just supporting the arbitrary sending of messages from client to server ? This may even promote better security of syslog servers - the central loghost does not need to accept connections (exposing it to various DoS problems that could impact all syslog services). Comments ? Darren
