I have just had at least 6 emails from "Microsoft Corporation Security Support" containing a.exe for me to run, which will fix ALL of my microsoft security problems for me.
Too bad my ISP filters out virus attachments, I don't get to run it...
Wonder how many of these emails have just hit the world.
True, there is an unbelievably large number of developers, as you will see by participating in MS developer forums etc. But one main problem I have is this, I have MCP qualification, and my employers are MS vendors/partners but when I go home from work and feel the need to be creative, what can I do ? I am not going to pirate a MS development product worth many thousands of dollars, and I sure as hell cant afford to purchase it for my employers benefit, so I dont ponder work-related problems and work on solutions at home (or produce my own products to inflict on Windows users for that matter).
What I can do, is fire up my trusty KDE desktop, load up KDevelop or a host of other development environments where, wouldn't you know it, I can search out and apply a mind numbing array of support libraries, documentation and existing source code. I suspect the MS vendor/developer community is probably divided quite clearly between those huge enterprises that dont mind at all sending off truckloads of cash every time they need to upgrade their development tools etc, and those that feel the pinch and try to get by with what they can. You certainly dont get huge amounts of support from MS, and dont get to feel 'part of the community' without paying up in a big way first.
I wrote one of these last week, after reading the homepage source.
Its just a vbs script that essentially changes the default Windows action for a number of script file types to be 'edit' instead of 'open'. This mostly stops all those email-attachment clickers from running code indiscriminately.
I contemplated adding the next step, of accessing the address book and forwarding itself onwards, in the hopes that anybody still silly enough to execute script files via email will commit the final necessary act to stop this from happening again.
In the end, I decided not to distribute this because of its potential for jamming up mail servers and generally causing a nuisance for people who already know better and dont allow outlook to execute such code in the first place.
Slashdot Mirror
Like everyone said, OBD-II was installed in cars from 1996 onwards. The OpenDiag project provides an interface to this, I believe via serial port.
[http://www.opendiag.org/]
Les.
Also I just found something called Cinepaint, in my Debian sources list, no clue what its like but the description file is impressive :)
Apparently It is the most popular open source tool in the motion picture industry
Wouldn't it also be an incentive to manufacture false evidence so you can frame somebody up & collect the $$$
Trust no one
I have just had at least 6 emails from "Microsoft Corporation Security Support" containing a .exe for me to run, which will fix ALL of my microsoft security problems for me.
Too bad my ISP filters out virus attachments, I don't get to run it...
Wonder how many of these emails have just hit the world.
True, there is an unbelievably large number of developers, as you will see by participating in MS developer forums etc. But one main problem I have is this, I have MCP qualification, and my employers are MS vendors/partners but when I go home from work and feel the need to be creative, what can I do ? I am not going to pirate a MS development product worth many thousands of dollars, and I sure as hell cant afford to purchase it for my employers benefit, so I dont ponder work-related problems and work on solutions at home (or produce my own products to inflict on Windows users for that matter).
What I can do, is fire up my trusty KDE desktop, load up KDevelop or a host of other development environments where, wouldn't you know it, I can search out and apply a mind numbing array of support libraries, documentation and existing source code. I suspect the MS vendor/developer community is probably divided quite clearly between those huge enterprises that dont mind at all sending off truckloads of cash every time they need to upgrade their development tools etc, and those that feel the pinch and try to get by with what they can. You certainly dont get huge amounts of support from MS, and dont get to feel 'part of the community' without paying up in a big way first.
LesF
I wrote one of these last week, after reading the homepage source.
Its just a vbs script that essentially changes the default Windows action for a number of script file types to be 'edit' instead of 'open'. This mostly stops all those email-attachment clickers from running code indiscriminately.
I contemplated adding the next step, of accessing the address book and forwarding itself onwards, in the hopes that anybody still silly enough to execute script files via email will commit the final necessary act to stop this from happening again.
In the end, I decided not to distribute this because of its potential for jamming up mail servers and generally causing a nuisance for people who already know better and dont allow outlook to execute such code in the first place.
Les