Ok, can I see your credit card statements for the last 5 years? Can I listen to all of your phone conversations? Can I watch you shower and use the bathroom? I mean, you sound like an average person with nothing to hide...../s
This approaches one thing I always wonder when this comes up: Are people with that argument really okay with their co-workers finding out what porn they watch and when they watch it?
It's perhaps a little extreme, but I can totally see it becoming a possibility due to large leaks like this.
You are ignoring the possibility that people saying that don't watch porn. I don't.
Regardless, I disagree with the argument, as things you don't need to hide now can become things you wish you had hidden later (think of Jewish people in Germany in the 1920s whose religion and ethnicity were obvious).
Sure. The only condition is that you don't share the information in public, on pain of massive fines and imprisonment - you can only use it to improve your internal business processes.
What you’re looking for is the CloudKey. It is the local Controller and can be accessed via “the Cloud” if needed, but not mandatory. I tried running the Java controller on my Mac, it worked but sucked. Having an independent dedicated piece of hardware is worth every penny IMO.
To each, their own. In my case, the ease of use was worth every penny. If I take my hourly rate and apply that to how long I spent trying to setup a controller on a raspberry pi, then I could’ve bought 2 or 3 CloudKeys.
Recently, I got a different take on this from a book called ‘Mad Genius’. The author says in today’s fast moving world if you keep doing what you have been doing, you will perish very quickly. Like Nokia.
While it monitors SSH by default out of the box, people here are talking about creating custom filters which will monitor their Apache or Nginx logs. (Although, that said, we also have it monitor our non-standard SSH port with v. aggressive blocking rules, even though it's also behind a firewall. Defence in depth, and all that.)
The documentation isn't the greatest, but this page explains the concepts well enough and was easy to find using Google.
A filter matches lines in the nginx log using regular expressions. If the line matches, it uses another regexp to extract the IP address, and then calls out to scripts to block that IP address.
I'm not going to post the exact configuration files I use, but the GitHub repo for fail2ban contains examples.
I like Fail2Ban, but as I remember it, my learning process looked a lot like this:
1.) Read through the documentation.
2.) Pour myself a scotch.
3.) Read through more documentation.
4.) Start drinking right out of the bottle.
5.) Try something.
6.) Get an error or experience a spectacular failure.
7.) Use StackOverflow.
8.) GOTO 5.
-------------
In good news, it worked - the light went on and now I'm confident that I could adapt Fail2Ban to suit any use. But, in bad news, honestly, I feel your pain and understand where/why you are getting stuck. Fail2Ban is a very complicated, yet extremely useful piece of software.
