Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start monitoring brute-force login attempts on roobot endpoint #10

Open
patcon opened this issue Feb 22, 2014 · 1 comment
Open

Start monitoring brute-force login attempts on roobot endpoint #10

patcon opened this issue Feb 22, 2014 · 1 comment

Comments

@patcon
Copy link
Contributor

patcon commented Feb 22, 2014

If we're going to start trusting roobot to do important things, and if he lives on the public internet (which he does: https://user:[email protected]), then we need to know if someone is trying to bruteforce access through express framework's basic auth.

A failed attempt looks like this in the heroku logs:

2014-02-22T00:25:46.442907+00:00 heroku[router]: at=info method=GET path=/ host=roobot-prod.herokuapp.com request_id=3fcdfa4b-82a9-4780-b275-07058878b037 fwd="68.232.91.35" dyno=web.1 connect=7ms service=9ms status=401 bytes=214
@patcon
Copy link
Contributor Author

patcon commented Feb 24, 2014

Relevant: https://devcenter.heroku.com/articles/logging#syslog-drains

$ heroku help drains
Usage: heroku drains

 list all syslog drains

Additional commands, type "heroku help COMMAND" for more details:

  drains:add URL     #  add a syslog drain
  drains:remove URL  #  remove a syslog drain

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants