user/mauchle/radsecproxy.git/ChangeLog, branch v6only

Ready for radsecproxy-1.6.9.

2017-08-02T13:53:51+00:00

Don't follow the NULL pointer, not even in debug printouts.

2017-08-02T11:09:43+00:00

Bug reported by Leonhard Knauff.

Closes RADSECPROXY-68.

Use a listen(2) backlog of 128.

2017-08-02T11:04:47+00:00

There's a chance that incoming (legitimate) connections arrive faster
than what it takes to spawn a new thread and get back to
listen(). Therefore we should ask the stack to queue at least one
entry, i.e. use a backlog value of at least 1. There's arguable also a
chance of more than two concurrent incoming connections, which would
make a case for a backlog value greater than one.

A reasonable high value seems to be 128, which also is what SOMAXCONN
is on many unix systems. In the choice between 1 and 128, an argument
against the higher value is that it may mask the potential problem of
spending a long time serving incoming connections.

Being reasonably confident that radsecproxy is efficient when it comes
to serving incoming connections, by handing them off to a newly
spawned thread, I think that 128 is a fine choice.

Closes RADSECPROXY-72.

Update ChangeLog with -77.

2017-08-02T08:08:47+00:00

Update ChangeLog.

2017-08-01T16:27:24+00:00

add msg-id to debug log output

2017-08-01T15:53:26+00:00

create new cert_store before reloading CAs and CRLs

2017-08-01T15:41:11+00:00

Conflicts:
	ChangeLog

Revert partial fix for RADSECPROXY-69 (47ccc9f).

2016-11-01T14:10:27+00:00

This was potentially making things worse.

Look at servers->dynamiclookuparg for deciding if a server is dynamic.

2016-11-01T09:31:22+00:00

The dynamiclookupcommand member of the _config_ of the server is being
set to NULL when it's copied in confserver_cb(), resulting in dynamic
discovery being done for realms that already have a server.

Patch from Fabian Mauchle.

Addresses RADSECPROXY-69.

radsecproxy-1.6.8.

2016-09-21T11:53:15+00:00