@scottalanmiller said:
Here you go, posted over there too....
http://community.spiceworks.com/topic/523903-points-moving-backwards
Nice!
@scottalanmiller said:
Here you go, posted over there too....
http://community.spiceworks.com/topic/523903-points-moving-backwards
Nice!
@Huw3481 said:
Mangolassi and Spiceworks are two separate things, but going to the one to bitch about the other doesn't sit well with me.
The only reason I've posted here is for clarification, otherwise it's a "oh, those nasty people at Spiceworks" comment.
I agree! Post like this irk me: http://www.mangolassi.it/topic/1561/something-fishy-with-sw-points/3
@ambarishrh said:
@StrongBad I like it, but I am still a fan of Amazon web services!
Glad to hear from another AWS fan!
@Dominica said:
He comes across as bitter and pathetic, and not at all funny. How does he still have a job?
People still read his stuff and post links on other sites...
@Nic said:
Aaaaaannnnd they got hacked. http://techcrunch.com/2014/06/20/yo-app-allegedly-hacked-by-college-students/
Remote Rickrolling. Now that's an app I'd pay for.
@ITcrackerjack said:
His writing comes across like he has a giant chip on his shoulder towards Amazon. I mean it's find to call a spade a spade, but geez, have a little dignity.
I'd have a chip on my shoulder if they banned me from their events, too. Then again, I wouldn't have done what he did in order to get banned.
Nice example of Webroot in action! It was a good example of a user randomly clicking on things and infecting themselves.
The video's author seems more of a dabbler than a professional, however. Csrss in the user profile is not a good thing.
@garak0410 said:
@ITcrackerjack said:
"Earlier this week, Ways and Means Republicans said as many as six IRS employees involved in the scandal also lost email in computer crashes, including the former chief of staff for the acting IRS commissioner."
Convenient... They sure have a lot of "computer crashes".
I heard this on the news the other day and I just had to laugh out loud. Beyond a RAID set problem, I've not had a hard drive crash on a workstation in my 3 1/.2 years here.
Hard drives are the most frequently failing component that I've seen so far.
@scottalanmiller said:
http://blog.cari.net/carisirt-yet-another-bmc-vulnerability-and-some-added-extras/
32,000 server affected. Open port that responds with security details including password!
Sorry if this comes off a bit ranty...
It's a lot more than 32k that are impacted by it. The 32k are among the millions of folks dumb enough to expose their management interface to the public. I feel like this is a trip back to the pre-firewall days of the 1990's. "If I put my IPMI/iLO/iDRAC/CIMC forward-facing, I can remotely manage my servers in my colo!" Yes, and so can everyone else. If you want remote management of your servers, either use a VPN or put it behind a firewall with rules allowing your office's subnet access to that IP address.
Well, crap! I'd have loved to have been there to have a drink. The irony of me drinking while PSX was dry would have been delicious!
@StrongBad said:
There was IT before the Internet?
Certainly. The first LANs I worked with had no Internet connectivity.
@Bill-Kindle said:
@scottalanmiller said:
@alexntg no kidding. No backups? That's crazy.
But Cloud........
Not having backups leaves them liable for some massive lawsuits. I'd be really surprised if they ever come back. Titsup was a good word for what happened to them.
They did have backups. They were also in AWS and geographically redundant. The attacker deleted the backups as well. The issue is that a proper DR plan would have addressed the issue of what would happen if AWS failed.
@Hubtech said:
@alexntg said:
That's a brilliant example of a lack of proper Disaster recovery planning. With business practices like that, I'm glad they went under. I wonder if they attackers made copies of anything before they cleaned house?
saying you're glad they went under is pretty stupid.
Perhaps a context should be have been presented. It's like a business version of the Darwin Awards. Their stupidity took them out of the business gene pool. So while I'm not glad that it cost folks not involved with the DR plan their jobs, I'm glad that it came to an evolutionary dead end.
It's easy to win a battle when only one side thinks there's a war. It's a matter of finding the right tool for the job, not about the code base.
@Carnival-Boy said:
How did you cope with support before the internet? I remember phoning Microsoft a few times, but generally I can't really remember what I did. I'm sure that problems that take ten minutes to solve now could take a whole day back then.
Trial and error. I was fixing computer issues before I had Internet access.
That's a brilliant example of a lack of proper Disaster recovery planning. With business practices like that, I'm glad they went under. I wonder if they attackers made copies of anything before they cleaned house?