1. 25 Nov, 2016 1 commit
    • Michal 'vorner' Vaner's avatar
      amihacked: Swap indexes · 9b75ddfc
      Michal 'vorner' Vaner authored
      Use the attack kind as the first index and the date as second. First,
      the resulting JSONs are likely to be smaller, second, it makes sense to
      do a graph of one kind of attack over time, but it makes little sense to
      do a graph for single day comparing pears and apples.
      9b75ddfc
  2. 24 Nov, 2016 1 commit
    • Michal 'vorner' Vaner's avatar
      amihacked: Avoid 0-valued items · 7c7a752b
      Michal 'vorner' Vaner authored
      Sometimes (observed with at least telnet) it could generate item with 0
      occurrences. That one is of no real use for the graphs or statistics, so
      avoid generating them altogether.
      7c7a752b
  3. 20 Nov, 2016 2 commits
  4. 14 Nov, 2016 3 commits
  5. 07 Nov, 2016 1 commit
  6. 10 Oct, 2016 1 commit
  7. 29 Sep, 2016 1 commit
  8. 09 Sep, 2016 1 commit
    • Michal 'vorner' Vaner's avatar
      Don't resend the flow config every two minutes · d0add18c
      Michal 'vorner' Vaner authored
      Due to a bug in 6c262476, we were
      resending the config every two minutes. We resend a config when we mark
      a client as it asked for a config. However, to resend it, we mark the
      client again for the next 2-minute long while, creating a loose loop.
      
      We now have three states:
      • We haven't seen the client at all
      • We have seen it, and answered the first request for config
      • We have seen it and we haven't answered at least one of the requests
      
      We resend it only in the third case, but resending it puts the client
      into the second, so the loop is broken.
      d0add18c
  9. 07 Sep, 2016 9 commits
  10. 30 Aug, 2016 1 commit
  11. 29 Aug, 2016 2 commits
    • Michal 'vorner' Vaner's avatar
      flows: Rate-limit sending of configs · 6c262476
      Michal 'vorner' Vaner authored
      While we have a fix for the config-request-loop in the previous commit,
      it is going to take some time to propagate to clients. Have a workaround
      in the meantime, deploying on server is much faster.
      6c262476
    • Michal 'vorner' Vaner's avatar
      flows: Don't loop asking for config · f5121535
      Michal 'vorner' Vaner authored
      Previously, if the diff data structure requested complete rebuild, the
      plugin asked for new config. The config came, but it happened to be the
      same ID, so it was thrown away. Then offers of new versions of the data
      structure came and it asked to be rebuilt again. So this created a loop
      asking for new config.
      
      We reset the config ID when asking for rebuild (and the server should
      never have config no. 0). This way it shall think the config is
      different and do the actual rebuild.
      f5121535
  12. 23 Aug, 2016 1 commit
  13. 22 Aug, 2016 1 commit
  14. 17 Aug, 2016 1 commit
  15. 09 Aug, 2016 3 commits
  16. 08 Aug, 2016 1 commit
  17. 14 Jul, 2016 1 commit
  18. 08 Jul, 2016 1 commit
  19. 29 Jun, 2016 1 commit
  20. 21 Jun, 2016 1 commit
  21. 26 May, 2016 2 commits
  22. 25 May, 2016 1 commit
  23. 19 May, 2016 1 commit
  24. 18 May, 2016 2 commits