AgentOJ - Slashdot User

Boonana Trojan Horse for Mac OS X Spreads-> 0

Submitted by Orome1 on Wednesday October 27 2010, @03:11AM

Orome1 writes "SecureMac has discovered a new Trojan horse in the wild that affects Mac OS X, including Snow Leopard (OS X 10.6). The trojan horse, trojan.osx.boonana.a, is spreading through social networking sites, including Facebook, disguised as a video. The Trojan is currently appearing as a link in messages on social networking sites with the subject "Is this you in this video?" When a user clicks the infected link, the trojan initially runs as a Java applet, which downloads other files to the computer, including an installer, which launches automatically. When run, the installer modifies system files to bypass the need for passwords, allowing outside access to all files on the system."
Link to Original Source

Comment: Source Code Available Here (Score 5, Informative) 151

by AgentOJ on Sunday August 30 2009, @07:10PM (#29255765) Attached to: Skype Trojan Can Log VoIP Conversations

It appears that a guy named Ruben Unteregger published the source code on his site at http://www.megapanzer.com/source-code/#skypetrojan

According to his site, he removed a plugin system from the source as well as code to bypass firewalls, but he'll add it back in at a later date.

From looking at the source, this is heavily geared toward Windows, so the current iteration of the source doesn't affect OS X at this time.

Emergent AI In an Indie RTS Game 146

Posted by Soulskill on Wednesday June 03 2009, @02:18AM
from the no-path-found dept.

x4000 writes "My recent RTS game uses a new style of AI that hybridizes rules-based AI with emergent AI logic. As a disclaimer, I'm really not an AI programmer at all — my background is in databases, financial modeling, etc. But it just so happens that database experience, which often involved distilling data points from multiple sources and then combining them into suggested decisions for executives, also makes a great foundation for certain styles of AI. The approach I came up with leans heavily on my database background, and what concepts I am familiar with from reading a bit about AI theory (emergent behavior, fuzzy logic, etc). The results are startlingly good. Total development time on the AI was less than 3 months, and its use of tactics is some of the best in the RTS genre. I'm very open to talking about anything and everything to do with the design I used, as I think it's a viable new approach to AI to explore in games, and I'd like to see other developers potentially carry it even further."

Comment: Can't trust Roper (Score 1) 12

by AgentOJ on Sunday May 17 2009, @12:49PM (#27987581) Attached to: <em>Champions Online</em> Delayed Until September

I'm sorry, but after the abomination that was Hellgate: London, it will take a very, very long time for Bill Roper to earn my trust again. That game was a prime example of what NOT to do in an MMORPG. I just feel bad for all the people who blew their money on a "lifetime" subscription which ended basically being an extended beta masquerading as a finished game, full of broken promises, missed release dates, glitchy content, and eventually a slow death. I hope he's learned his lesson, but I'll let other people test the water before I'd be willing to jump in; I'm not ready to get burned by Roper again.

Comment: Re:Dies the Fire (Score 1) 145

by AgentOJ on Monday February 23 2009, @10:36PM (#26965417) Attached to: First Evidence of Supernovae Found In Ice Cores

That entire series is excellent, but having read all of the books in the series that have been published up to this point makes the wait until next fall for a new hard! Be sure to read the other series that starts with Island in the Sea of Time by S.M. Stirling as it ties in with the event in Dies the Fire.

Three Unforgivable Usability Sins 1

Submitted by Esther Schindler on Wednesday December 26 2007, @05:05PM

Esther Schindler writes "It's hateful when a developer takes a "shortcut" that saves that individual a couple of minutes, but thereafter causes extra effort from every single user. Awful as they are, these application design errors—all the fault of lazy developers—are entirely too common."