Get off my lawn, whippersnappers!

IP addresses should not be used as the sole means to identify people.

The argument was definitely around in the BBS days, when (almost) everybody knew it was pronounced like "gif." ;)

FTPS is WORSE. The problem with FTP in general is with stateful firewalls and NAT/PAT.

FTP is a ridiculous protocol. For FTP to work at all these days, firewalls actually need to go out of their way to snoop in on the control channel and watch for the data channel IP & port, and then use that to pre-populate the state table with an entry for the data session.

This breaks down on a lot of firewalls if you change the control port, or if you use FTPS where the control session is encrypted and the firewall can't snoop in on the session to make it work. Instead, a common solution is to configure a large static range of ephemeral ports for the data connections that just need to be always allowed through the firewall.

Using FTP these days makes zero sense when there are better alternatives, or as OP stated, FTP just needs to die!!

SFTP on the other hand at least works over a single port (SSH), but has its own problems with SSH flow control fighting TCP flow control, multiplexed sessions over a single blocking TCP stream, etc.

Apparently Microsoft is in the smartphone business now too.. Who knew?

How do you figure?

"This attack required over 9,223,372,036,854,775,808 SHA1 computations. This took the equivalent processing power as 6,500 years of single-CPU computations and 110 years of single-GPU computations."

That works out to about 45mil computations/sec for CPU or 2.65 bil computations/sec for GPU.

To get it done in 30 days would take a 79,000 machine CPU botnet, or a 1,342 machine GPU botnet.

Fudge the numbers a bit as they probably won't be running full-tilt for 30 days straight, and they won't all have CPU/GPU as spec'd in the attack (paper protoyped on Nvidia GTX 970 btw). Still, we're nowhere remotely close to 10mil machine botnet taking 3 years.

=(

I'm convinced that Casper Dik was just a code-name for the entire SunOS/Solaris support team, and that there's no way any one individual can know and contribute so much.

Decades later, and I still aspire to have even a tenth of a clue as him.

Try Singapore.

I ran a Renegade board for several years. Good times!

There were still a handful connected to the Internet last time I checked.

The same guy (Jason Scott) has hundreds of the old shareware (and other) CDs up for download on archive.org as well. Lots of good stuff there.

Atari 130XE? I had the 64K version, the Atari 65XE.

YMMV, but I got together with a friend a few months ago and got him to drag his Commodore 64 stuff out of the closet. We couldn't get video output on his fancypants modded C64, but his vanilla C64 worked fine, along with disk drives and every single floppy we tried (likely from late 80s, last touched in early 90s).

I've heard before that some floppy drives may have components that wear with age (e.g. rubber belts that rot and disintegrate with age), but it's worth a shot.

Regarding expansion, as I understand it, the effects on objects within something as small as a galaxy are insignificant compared to the force of gravity holding the galaxy together.

The greater the distance between two objects, the greater the effect of expansion; and so it does become significant when comparing two distant galaxies.

ipfwadm.. ipchains.. iptables.. nftables... progress sucks. :(

Ditto.

My next question is: is his machine compromised and part of a botnet. I.e. is he the one doing the DoSing, and his router is falling over as a result.

Is this:
  "Network Admin" as in switches, routers, firewalls, etc.;
  "Network Admin" as in the often used anachronism dating from the 80s for novell admins but actually referring to what's presently known as "Windows Admin," or generically "Server Admin"; or
  "Network Admin" as in "Jack of all Trades IT guy" in smaller organizations?

If you meant the first one, which maybe you did given that you have a CCNA, then you don't need to learn Exchange and SQL server. It won't hurt, but it sure won't help as much as going for your CCNP will.

Also, consider this a branching-off point. It sounds like you might presently have a job in the "jack of all trades" category, which can give you a high-level perspective of many of the areas of specialization. Pick the one you like the most, and start learning your new specialty. Cross-training on the basics can be very valuable. Learning how to do basic scripting (perl, python, lua, whatever..) will save you much more time over the years than you spend learning it. If you encounter a repeatable process then automate it. If you don't know how, then learn how, and automate it. Sorry if I'm drifting away from your question, and into general advice for someone starting out. :-)

I also have to agree with some of the other posters, even if it seems like they're trolling. Get that A+ and Network+ crap off your resume! Nobody respects it, and it only serves to accentuate your inexperience. Start cramming and replace it with something better -- schedule your exam today if you need motivation to pick up the books!

Oh, and lastly.. Don't hang out posting on slashdot. Big waste of time!