Edward Snowden certainly has name recognition in the security space, which in branding terms equals big money. He's got his share of wild and crazy times overseas doing various hijinx not always on the up and up, sorta just like other security specialists of an earlier generation. Sure, in terms of branding alone Snowden could easily become the next McAfee, and he's still very young!

And isn't as if they weren't both wanted on international warrants either; and street cred. does sell sneakers.

Here's the link to the blog post, that didn't make it into my previous reply: https://www.adayinthelifeof.nl.... It clarifies several reasons for using the standard port 22 for ssh.

Yes, you are right and I stand corrected. In fact late yesterday, I happened upon a blog post teaching me the same explanation you gave me just now:

when we start SSH on port 22, we know for a fact that this is done by root or a root-process since no other user could possibly open that port. But what happens when we move SSH to port 2222? This port can be opened without a privileged account, which means I can write a simple script that listens to port 2222 and mimics SSH in order to capture your passwords. And this can easily be done with simple tools commonly available on every linux system/server. So running SSH on a non-privileged port makes it potentially LESS secure, not MORE.

Thank you for your important clarification regarding my security practices.

Start your security process by not using port 22 for ssh, and instead using some random, legal 5-digit port number. Then block IPs from anyone doing a port scan. Also, setup port-knocking prior to any authorized user even starting to login using ssh. Of course certificates should only be used, not passwords for authorization. That should go a long way to keep the bad guys out.

Also bots tend to have the same user-agent strings, which tend to be obscure in and amongst themselves. These obscure, identifying user-agents can also be blocked, once identified.

To read and actually make sense of machine logs, the free ELK Stack rocks! Here's a guide to setup your own machine, for the purpose of reading logs in a very user-friendly way.

Replying to myself here. I was being sarcastic dammit. 'Separatists', in the most-classic sense, typically don't have such sophisticated weaponry or manpower at their disposal, when they 'rebel'. Duh.

I even cited with photos of what a BUK missile battery looks like. Please don't think I'm some sort of anarchist, okay?

Up until this period of time, airspace at that altitude, over this region, wasn't in any way shape or form considered to be a war-zone, I can assure you. Or else that commercial flight would not have been there in the first place. I do not believe this particular international commercial flight up there was something like an isolated event either. Now your point in retrospect perhaps...

That rag tag militia got lucky it seems, with a direct hit no less. Those light ammunitions gathered from round the house, what the odd Klashnikov and what have you.

Speculation at this point is this is what those rag-taggers managed to bring it down with: http://www.telegraph.co.uk/new...

6: An Amazon Glacier client for archiving documents for the long haul.

May I refer you to git-annex-assistant?

TFA says he's a producer at AOL. Seeing as how he's an AOL employee, he probably needs a lot more bandwidth than you do, as you're someone who probably just works in I.T. Go figure. I don't understand anything about AOL either.

Obviously he needs way more bandwidth than he can get via an (AOL) dial-up modem, which explains why he's been with Comcast for the last 9 years.

Someone that works from home might opt for a larger package to obtain greater uploading bandwidth. I did that to advance from 1.5 to 6 Mbps recently myself, and I'm glad I did.

Maybe this is just AOL picking a Telecom fight with Comcast. Seriously, since when is it ever legal to record a call like this? But I suppose it becomes legal when you're on hold and the recording played to you says they'll record you first.

This New York Times article states he arrived to work at Microsoft, from Hyderabad, India in 1992. It says nothing about any initial H1b status of his. Obviously he lives in America now.

http://www.nytimes.com/2014/02...