- Dec 25, 2008
- 155
- 0
- 0
Is spyware programs the product of visual basic, or programming ? How would a code to scan the computer for a file, to keep it simple, look like ?
Originally posted by: darkmandaddy
If its written in C/C++ how do you create a gui for it ? What does GNU stand for ? (I'm sorry, stupid question). I understand the code above, that seems kinda cool. Thx
Originally posted by: darkmandaddy
oooh, I thought I heard of that term but I forgot where. Thank you.
Also, would creating gui with C++ similar to html ?
Originally posted by: darkmandaddy
Well thanks. I was looking at free spyware detection programs and after I took some classes of C++ and VB, I thought that the cyberworld are all compose of codes like that. I didn't mean to create a spyware, but just how does one of those program work to find the right thing to delete.
Mark: I figured we where starting to head towards dangerous waters. The only thing is, once you know how to program, viruses really aren't THAT hard to write. I also figured that making a GUI really wasn't so much a part of writing malware as it is general programming practice.
Originally posted by: darkmandaddy
wow, that site is awesome. Does anyone know what the other extentions mean ? other than c, cpp, doc ?
Originally posted by: MrChad
There's a good article posted on /. today that reminded me of this thread.
An interesting read: http://philosecurity.org/2009/...-with-an-adware-author
Originally posted by: Markbnj
Originally posted by: MrChad
There's a good article posted on /. today that reminded me of this thread.
An interesting read: http://philosecurity.org/2009/...-with-an-adware-author
Yeah, I read that earlier. Interesting, however they were really trying to avoid writing malware, if you believe the guy. Used many of the same techniques though.
Originally posted by: Crusty
Originally posted by: Markbnj
Originally posted by: MrChad
There's a good article posted on /. today that reminded me of this thread.
An interesting read: http://philosecurity.org/2009/...-with-an-adware-author
Yeah, I read that earlier. Interesting, however they were really trying to avoid writing malware, if you believe the guy. Used many of the same techniques though.
I wonder how many of those techniques still work in Vista/Windows 7.... I would think running IE7 in protected mode coupled with UAC would prevent most of those techniques from
working.
Originally posted by: degibson
For my part, I think as long as one OS and one browser are as popular as XP/Vista/7 and IE6/7/+, there will be a lot of known exploits. The only way to get rid of that kind of exploit is a massive diversification of (at least) browser and hopefully OS.
Originally posted by: Markbnj
Diversification cuts both ways. You can choose a small pond and be a big fish in it, but when it dries up you're farked. If we had real OS diversification, a thriving market in versions and flavors, they'd all have to support something like .NET as a standard. It's hard to imagine ten or fifteen good, stable office productivity packages across ten or fifteen OS flavors of the month. MS Office has what.. twenty years now? Some of it's great, some of it sucks, but everyone can use it.
Originally posted by: degibson
Originally posted by: Markbnj
Diversification cuts both ways. You can choose a small pond and be a big fish in it, but when it dries up you're farked. If we had real OS diversification, a thriving market in versions and flavors, they'd all have to support something like .NET as a standard. It's hard to imagine ten or fifteen good, stable office productivity packages across ten or fifteen OS flavors of the month. MS Office has what.. twenty years now? Some of it's great, some of it sucks, but everyone can use it.
Diversification would also cut down on the motivation to make ad-ware in the first place, there wouldn't be a single logical target. That is, diversification would nerf ad-ware's usefulness in the first place, but it would also magnify legitimate development costs.
I suppose I'm somewhat of a pessimist, but I think we're always going to have buggy exploitable code, and exploits that exploit the exploits.