1. 07 6月, 2018 1 次提交
  2. 06 6月, 2018 2 次提交
  3. 05 6月, 2018 1 次提交
  4. 04 6月, 2018 4 次提交
  5. 03 6月, 2018 3 次提交
  6. 01 6月, 2018 4 次提交
  7. 31 5月, 2018 2 次提交
  8. 28 5月, 2018 2 次提交
  9. 25 5月, 2018 8 次提交
  10. 28 4月, 2018 1 次提交
  11. 21 4月, 2018 1 次提交
  12. 20 4月, 2018 3 次提交
  13. 12 4月, 2018 1 次提交
  14. 07 4月, 2018 1 次提交
  15. 03 4月, 2018 2 次提交
  16. 24 3月, 2018 3 次提交
    • G
      auth: fix re-authentication of peer in all chap modules · 10ede239
      Guillaume Nault 提交于
      If the peer re-authenticates (because of option conf_interval) and pwdb
      calls auth_result(), we may add the interval timer again to the session
      context. This crashes accel-ppp when deleting the session, because the
      interval timer is removed only once and the superfluous timers are
      still running. Therefore, when removing the context, triton detects
      this issue and calls abort().
      
      To fix this, we need to detect if the session is already started and
      just send a CHAP Success message in this case.
      Signed-off-by: NGuillaume Nault <g.nault@alphalink.fr>
      10ede239
    • G
      auth: avoid sending duplicate CHAP Failure messages in mschap-v1 and mschap-v2 · 29c62668
      Guillaume Nault 提交于
      When pwdb returns PWDB_NO_IMPL and chap_recv_response() performs the
      authentication itself, it delegates this task to chap_check_response().
      This function sends a CHAP Failure message if it can't retrieve the
      password, but not in case of password mismatch. Since
      chap_recv_response() already sends a CHAP Failure message on error,
      the one sent by chap_check_response() is useless.
      Signed-off-by: NGuillaume Nault <g.nault@alphalink.fr>
      29c62668
    • G
      auth: fix missing CHAP Success message in chap-md5 · 5da833d5
      Guillaume Nault 提交于
      When pwdb returns PWDB_NO_IMPL, then chap_recv_response() tries to
      authenticate the peer itself. If this authentication succeeds but the
      session is already started (in case of re-authentication, with option
      conf_interval), no CHAP Success is sent.
      
      This patch sends the missing CHAP Success message in this case, so that
      the peer knows that its response has been received and accepted, and
      that no retransmission is required.
      Signed-off-by: NGuillaume Nault <g.nault@alphalink.fr>
      5da833d5
  17. 20 3月, 2018 1 次提交