1. 02 Aug, 2017 5 commits
    • Linus Nordberg's avatar
      Ready for radsecproxy-1.6.9. · 59b519f6
      Linus Nordberg authored
      59b519f6
    • Linus Nordberg's avatar
      Don't follow the NULL pointer, not even in debug printouts. · 32d58a52
      Linus Nordberg authored
      Bug reported by Leonhard Knauff.
      
      Closes RADSECPROXY-68.
      32d58a52
    • Linus Nordberg's avatar
      Use a listen(2) backlog of 128. · 950306fc
      Linus Nordberg authored
      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.
      950306fc
    • Linus Nordberg's avatar
      Update ChangeLog with -77. · 3c321320
      Linus Nordberg authored
      3c321320
    • Linus Nordberg's avatar
      c00a0393
  2. 01 Aug, 2017 16 commits
  3. 28 Jul, 2017 1 commit
  4. 01 Nov, 2016 3 commits
  5. 21 Sep, 2016 2 commits
  6. 19 Sep, 2016 1 commit
  7. 23 Mar, 2016 1 commit
  8. 14 Mar, 2016 1 commit
  9. 11 Mar, 2016 4 commits
  10. 25 Feb, 2016 2 commits
  11. 19 Jan, 2015 3 commits
  12. 16 Jan, 2015 1 commit