lol dolphin malware most funny joke i ever heard XD
(05-13-2010, 11:08 PM)omegadox Wrote: [ -> ]At least you can trust the stuff you compile on your own.
Well, at least that way you can be sure that nothing else is "bundled" with the emu. But if his system is infected not even compiling on his own would help him.
Also, you can't always trust something just because you compile it. In this case, however, I'm pretty confident with Dolphin.
AVG sees a .txt as a virus *wtf???*...
i once had AVG, I never used it again after I removed it lol, I now use NOD32
, got it when I bought my PC.
(05-14-2010, 06:50 AM)MLConian Wrote: [ -> ]If I were you I'd uninstall AVG and run Stinger (http://us.mcafee.com/virusInfo/default.asp?id=stinger) and Housecall (http://housecall.trendmicro.com/). Those two should be able to clean up most of the mess as they're heavy-duty. Then, install Avast 5. Be sure to switch off the sounds though, kind of annoying to hear "virus database has been updated" every 2 hours or so. 
It's just simply a little more then a beep - while in fullscreen you don't hear it - and it updates every 24 hours (sometimes 12)
(05-14-2010, 06:50 AM)MLConian Wrote: [ -> ]If I were you I'd uninstall AVG and run Stinger (http://us.mcafee.com/virusInfo/default.asp?id=stinger) and Housecall (http://housecall.trendmicro.com/). Those two should be able to clean up most of the mess as they're heavy-duty. Then, install Avast 5. Be sure to switch off the sounds though, kind of annoying to hear "virus database has been updated" every 2 hours or so.
I think you pretty much disable that in settings.
(05-14-2010, 05:23 AM)kernel64 Wrote: [ -> ]Also, you can't always trust something just because you compile it
I don't see how, because when you have all source libraries and .cpp files, you see exactly what goes into an executable/dll and how it will function. Slipping malware into the emu source code is not feasible (unless you do it yourself) because every commit is reviewed, and by self-moderating, becomes impossible since it is too easy to note (especially when it's masked as a new' feature').
Similar self-moderation exists on non-coding projects too like wikipedia.. You can vandalize important pages and put links to trojans for about 10-20 seconds, before either a bot or one of the thousands of moderators reverts it and bans your IP range. Mass bot attacks are ineffective too because a page auto-protects if too many blanks or edits are performed in a certain timeframe. Hence the articles (ones based on verifiable reputable sources) are quite reliable as an info tool.
If you compile your own current dolphin builds it's not possible to get infected in any possible way.
(05-19-2010, 06:43 PM)Ocean Wrote: [ -> ] (05-14-2010, 05:23 AM)kernel64 Wrote: [ -> ]Also, you can't always trust something just because you compile it
I don't see how, because when you have all source libraries and .cpp files, you see exactly what goes into an executable/dll and how it will function. Slipping malware into the emu source code is not feasible (unless you do it yourself) because every commit is reviewed, and by self-moderating, becomes impossible since it is too easy to note (especially when it's masked as a new' feature').
Similar self-moderation exists on non-coding projects too like wikipedia.. You can vandalize important pages and put links to trojans for about 10-20 seconds, before either a bot or one of the thousands of moderators reverts it and bans your IP range. Mass bot attacks are ineffective too because a page auto-protects if too many blanks or edits are performed in a certain timeframe. Hence the articles (ones based on verifiable reputable sources) are quite reliable as an info tool.
If you compile your own current dolphin builds it's not possible to get infected in any possible way.
You can always check the code.