No movies will teach you about real skills needed for efficient project management. People who possess those skills are usually busy doing something else and consider their PM as pure overhead. It doesn't mean you have to be harsh with them. I mean help them as much as you can, sometimes, they might even cover your ass and take the hit for you if they are good PM.
Lucky you, I am still eavesdropping on dial tones and deciphering by matching to digits. I am also faking dial tones and making long distance calls by whistling.
(also, don't make false bomb threats. They're stupid)
Does this mean real ones are smart?
What will it look like if I ever go into one of those mobile OSes from the security standpoint compared to less mobille OSes? I haven't touched mobile OSes even remotely yet. I understand the apps ecosystem might cause problems not directly linked to the OS but still, overall?
It makes sense. I have always said that keeping your kids in an aseptic environment is not helping them to build resistance for when they get out to the real world at some point.
Do you remember that South Park episode where the parents would get their kids with other sick kids for them to also get sick? Well, there is some truth to it...
large numbers of dropped packets (esp. packets over 4000-5000 bytes) in exchange for almost-no-dropped packets.
hmmm... try playing with MTU, packets over 4000-5000 bytes?
I have an MTU of 576 in similar setups. VOIP works flawlessly and I have 0 dropped packets. Using qdisc, I use htb, to do traffic shaping is recommended too. The important thing is to keep your cable-modem empty...
Well, I guess it wouldn't have been UUOC either way.
Just use CVS
Barring IPs is stupid in the first place
In short, you bar them because you are sick of profiling them and you now have too many to profile compared to a few years ago..
Ok, you bar them after sending them to honey pots, profiling them and making sure you can't profile (learn from them) anymore.
Barring IPs is like patching holes in a steam locomotive boiler. I have always felt like it was a desperate move to hide all kinds of incompetencies but now I do it.
I bar them one IP at the time. I never bar netblocks.
Makes profiling them much easier. You gather much more data this way.
Yep, and I do not disagree with the GP. If he had read more closely, it is clearly stated that I bar them manually.
$ grep -c US
grep -c US
As far as barring whole netblocks, I hope you are using ipset as stated in my OP:
For some reason, there is this huge stigma against not being available to countries and regions you couldn't possibly give a shit about.
Well, I believe in that. I just bar offending IPs more easily if not on my whitelisted country list. That's all. I do not bar any network range in advance unless they offend my systems and even then, I bar them one IP at the time. I never bar netblocks.
Thanks, you made me design the optimal solution.
On top of being written in assembly, I will even run version 2 as a daemon so 0 fork since my daemon will be single threaded with a single waiting thread listening for input.
if echo "CA FR BE US CH GB AU IL NO NZ IP" | grep -q -w -i -e "$COUNTRY"; then
echo $COUNTRY is AOK with me
Nah, this is way to slow for me, version 2 will be written in assembly because then it will be lightning fast...