The first version of Stuxnet (Stuxnet-A), uses a special "autorun.inf", that has an executable at the beginning of the file (which the autorun.inf parser skips). After the executable the "proper" information for the autorun.inf add another "Open" option for the rightclick menu. Selecting this will execute the content of autorun.inf (the malware). read about it here.
The second version (Stuxnet-B or Stuxnet!lnk), uses the zero-day.lnk file vulnerability, that will automatically execute the content, when you browse the content of the USB stick.
See the links for more detail - it's quite fascinating (also from a technical perspective).
"Why would a Wookiee, an eight-foot tall Wookiee, want to live on Endor, with a bunch of two-foot tall Ewoks? That does NOT MAKE SENSE! But more important, you have to ask yourself: What does this have to do with this case? Nothing. Ladies and gentlemen, it has nothing to do with this case! It does NOT MAKE SENSE! Look at me. I'm a lawyer defending a major electronics company, and I'm talkin' about Chewbacca! Does that make sense? Ladies and gentlemen, I am not making any sense! None of this makes sense! And so you have to remember, when you're in that jury room deliberatin' and conjugatin' the Emancipation Proclamation, does it make sense? No! Ladies and gentlemen of this supposed jury, it does NOT MAKE SENSE! If Chewbacca lives on Endor, you must acquit!"
Ellison offered in September to settle the case with $100 million in charitable donations and without admitting wrongdoing.
I'm really puzzled about this. Can someone explain to me, how you can pay yourself out of a wrongdoing?
To - you have either done nothing wrong, and you are free, or you have done something wrong and have to pay for it. Maybe I'm just naiive, but how can it be "nothing wrong" and paying back money?
Found these on the official site - Are these what you need:
Windows (x86) - 75.2MB:
magnet.
Linux (x86) - 101.7MB:
magnet.
Solaris (x86) - 95.4MB:
magnet.
Solaris (Sparc) - 104.3MB:
magnet.
Source - 260.0MB:
magnet.
WTF is with that "Your comment has too few characters per line (currently 17.0)". Since when is a large number of characters per line a sign of a good post? At least I hope this rant fills up enought characters to please the bot.
Well flash media doesn't have seeking like harddrives.
Flash media DOES have seeking. There are no movable parts, but it still takes time. Most around 1ms, but some have quite a bit more. xbitlabs have observed >20ms on 2GB Sandisks in tests, for instance.
It seems like Flash producers are sacrificing seek speed for burst speed, which is fine for common Flash use (Digital photos, Music, etc), but bad for HD-like usage.
Now that you are so kind to supply a link, please read the following pages. As you'll undoubtably notice it's a bit of give and take. It wins some benchmarks, it looses some. All that these benchmarks show is that all these three types of CPU's are rather equal in terms of performance.
Btw. and testing one overclocked product against several stock clocked products just doesn't seem right.
I now personally look for other stuff, mainly performance per $ and how cool these things operate.
It isn't just an issue of clock speed, but also CPU core voltage. Throttling the clock speed from 2Ghz to 400Mhz can also be combined with a lower CPU voltage. So you are not only running the CPU slower, but also supplying it with a lower voltage.
I don't know about P4, but on AMD systems this allows for the CPU fan to completely stop when the CPU is idle (on desktop systems).
Both parent posts make good points. And this leads to some points I've experinced from outsourcing.
Testing
You need to have proper testing. Actually you also need this even when doing development inhouse.
You need to hire testers for your work, if your product is anything more complex than a utility for yourself. You can hire students, inhouse ressources or whatever you can pick up on the street. You need to make it clear in the contract that the program isn't finished until it has been tested, and that you'll respond with test results within X days of recieving a program revision.
Sourcecode
You should ALWAYS get the sourcecode. No code is perfect, and something always pops up after one or several months. If it, for some reason, isn't possible for the original firm to fix the problem at least your option isn't a complete program rewrite. This also ensures that there isn't any license problems with "borrowed" code and stuff like that.
Both of these issues should be explicit in your contracts, but also be fair to the third party, and restrict bug report times, so they don't have to fix bugs in two year old code for free.
Regaring the "when is something gained by outsourcing" question, at my work we outsource when we either don't have the inhouse compentencies or ressources - and most importantly: When the task can be clearly defined. Having a rather 'loose' project description not only frustrates the programmer, but it also frustrates us, when we recieve something way other than we expected. So: Clear contracts & clear project definitions, and hopefully you'll have a good working relation with the people you outsource to.
They finally get it working, and hand it into the boss,
without telling him how badly they got fucked by the outsourcing.
How on earth did he expect his boss to know not to hire the same firm again? I know most bosses are stupid assholes, but at least give the boss a chance to make an intelligent decision!
[...]Direct
Wow! We are really getting into the good stuff here.
And btw, you are 100% wrong. Crashes in DirectShow, D3D (Mostly related to quartz.dll) does NOT cause BSOD. Bugs in DRIVERS cause BSOD. If you had been developing with these for more than a day, you'd know that.
Slashdot Mirror
The first version of Stuxnet (Stuxnet-A), uses a special "autorun.inf", that has an executable at the beginning of the file (which the autorun.inf parser skips). After the executable the "proper" information for the autorun.inf add another "Open" option for the rightclick menu. Selecting this will execute the content of autorun.inf (the malware). read about it here.
.lnk file vulnerability, that will automatically execute the content, when you browse the content of the USB stick.
The second version (Stuxnet-B or Stuxnet!lnk), uses the zero-day
See the links for more detail - it's quite fascinating (also from a technical perspective).
I don't think tweaking the clock will be one of their biggest problems.
To: None <netbsd-users@netbsd.org>
:)
Seems my clairvoyant abilities aren't as precise as I've been trying to tell my customers. :(
"Why would a Wookiee, an eight-foot tall Wookiee, want to live on Endor, with a bunch of two-foot tall Ewoks? That does NOT MAKE SENSE! But more important, you have to ask yourself: What does this have to do with this case? Nothing. Ladies and gentlemen, it has nothing to do with this case! It does NOT MAKE SENSE! Look at me. I'm a lawyer defending a major electronics company, and I'm talkin' about Chewbacca! Does that make sense? Ladies and gentlemen, I am not making any sense! None of this makes sense! And so you have to remember, when you're in that jury room deliberatin' and conjugatin' the Emancipation Proclamation, does it make sense? No! Ladies and gentlemen of this supposed jury, it does NOT MAKE SENSE! If Chewbacca lives on Endor, you must acquit!"
The defense rests.
Ender's Game (2008).
Great book and series - hope we'll actually see a finished movie.
Thank God! I had almost given up waiting for Mambo No. 5.
To - you have either done nothing wrong, and you are free, or you have done something wrong and have to pay for it. Maybe I'm just naiive, but how can it be "nothing wrong" and paying back money?
Ah - I'm not the best at these new fancy P2P features ;)
Found this in Azureus. It should work for the Win32 binary:
Win 32 binary.
Found these on the official site - Are these what you need:
Windows (x86) - 75.2MB: magnet.
Linux (x86) - 101.7MB: magnet.
Solaris (x86) - 95.4MB: magnet.
Solaris (Sparc) - 104.3MB: magnet.
Source - 260.0MB: magnet.
WTF is with that "Your comment has too few characters per line (currently 17.0)". Since when is a large number of characters per line a sign of a good post? At least I hope this rant fills up enought characters to please the bot.
... are the ones your boss doesn't know about.
Not sure everybody at Rockstar Games agree with me on that one, though.
This is all right, as long as I don't have to look up at Uranus.
for the obligatory pr0n comments... Are you loosing your touch?
Seems like rounding to 115 - (18 + 19) was binary enough.
0) 55 47 55 2e 20 55 4e 41 51 2e
1) UGU. UNAQ.
2) HTH. HAND.
3) Hope That Helps. Have A Nice Day.
01010110 01000111 01101000 01101100 01001001 01000111 00110101 01101100 01100101 01001000 01010001 01100111 01100011 00110010 01101000 01110110 01100100 01010111 01111000 01101011 01001001 01000111 01001010 01101100 01001001 01000111 01101000 01101000 01100011 01101101 01010010 01101100 01100011 01101001 00110100 01001011
Btw. and testing one overclocked product against several stock clocked products just doesn't seem right.
I now personally look for other stuff, mainly performance per $ and how cool these things operate.
It isn't just an issue of clock speed, but also CPU core voltage. Throttling the clock speed from 2Ghz to 400Mhz can also be combined with a lower CPU voltage. So you are not only running the CPU slower, but also supplying it with a lower voltage.
I don't know about P4, but on AMD systems this allows for the CPU fan to completely stop when the CPU is idle (on desktop systems).
Both parent posts make good points. And this leads to some points I've experinced from outsourcing.
Testing
You need to have proper testing. Actually you also need this even when doing development inhouse.
You need to hire testers for your work, if your product is anything more complex than a utility for yourself. You can hire students, inhouse ressources or whatever you can pick up on the street. You need to make it clear in the contract that the program isn't finished until it has been tested, and that you'll respond with test results within X days of recieving a program revision.
Sourcecode
You should ALWAYS get the sourcecode. No code is perfect, and something always pops up after one or several months. If it, for some reason, isn't possible for the original firm to fix the problem at least your option isn't a complete program rewrite. This also ensures that there isn't any license problems with "borrowed" code and stuff like that.
Both of these issues should be explicit in your contracts, but also be fair to the third party, and restrict bug report times, so they don't have to fix bugs in two year old code for free.
Regaring the "when is something gained by outsourcing" question, at my work we outsource when we either don't have the inhouse compentencies or ressources - and most importantly: When the task can be clearly defined. Having a rather 'loose' project description not only frustrates the programmer, but it also frustrates us, when we recieve something way other than we expected. So: Clear contracts & clear project definitions, and hopefully you'll have a good working relation with the people you outsource to.
[...]Direct Wow! We are really getting into the good stuff here. And btw, you are 100% wrong. Crashes in DirectShow, D3D (Mostly related to quartz.dll) does NOT cause BSOD. Bugs in DRIVERS cause BSOD. If you had been developing with these for more than a day, you'd know that.
404 Patent doesn't exist.
;)
Do you mean 2750221 (Luggage rack for cars) - pretty stupid.
Or is it 2775021 (Burial Casket - from 1956) - also pretty silly.
Guess you can throw up any random patent number, and the patent will seem rather obvious.
We'll at least have some impressive fireworks, when one of these fail.
Ironic that a link collection doesn't allow direct linking. ;)
(just copy the link to a new window)