here's a common theme i've seen in recently compromised boxes:
sniff/bruteforce non-root user's password ftp to the user's account and upload some CGIs run the CGIs which do password bruteforcing of entire/16's (50mbit/sec of SYNs for example)
would be a simple task for them to forkbomb from a cgi. they don't even need shell access. just ftp and http.
subversion still has its warts, there are places where cvs is still more convenient than subversion, and bugs/issues with properties where subversion will eat your repository for breakfast. some aspects of subversion do not scale yet.
overall subversion is much more convenient to use (especially when digging out old commits from history), you just have to be careful. cvs is more cumbersome to use, but it's rock solid -- there's never any question if it's going to eat itself.
one can definitively say the ratio of loud/dangerous motorcyles is orders of magnitude higher than cars though.
i notice plenty of penis extender riceboys too, but since there are so many cars on the road, the ratio of idiots is much lower.
the only thing on the road isnt huge SUVs, and i dont know anyone who says that. most of the cars are little 4d sedans and such. it's not a matter of being noticeable, its a matter of simple statistics.
if one were to go to a busy intersection or street and count idiot drivers vs idiot motorcylists in a 24hr period, the results are pretty predictable. and it isnt because one is more "noticeable" than the other. its simply because one outnumbers the other.
"not all" is generally 5%, especially for the last 2.
i have yet to see someone who didnt ride their motorcycle around as some kind of penis extender.
i'll give you one point though, i haven't heard a motorcycle yet that was loud enough to knock books off my shelves from across the street like various riceboys do. i've had picture frames shaken off my walls by motorcycle-penis-extenders, but books -- not yet.
do you have an example of successful prosecutions of bank robberies after the statute of limitations expired, which used either 'continuing the conspiracy' or tax evasion, directly related to the original crime?
'reasonable effort' does not require 'absolute perfection', and 'imperfection' does not make the ISP liable.
otherwise, every little imperfection you ever made if you ever tried to do anything at all, would make you liable.
and that's simply not how it works.
so no, it really couldn't go either way. if a customer could prevail on such an argument, then it would become far too risky for any company to provide any kind of service to anyone, ever.
it would mean spamblocking and antivirus companies would be liable for every spam and virus that got through. anything less than absolute perfection, and customers would be suing left and right...
it would be impossible for companies to operate in such an environment.
and the ISP contract doesn't state that anyway. it states the ISP blocks ports to protect the ISP's infrastructure. it doesn't state it blocks ports to protect the customer.
and the client can believe the sky is green and the sun revolves around the earth. and they often do.
'tis too bad ISP customer contracts explicitly and carefully absolve the ISP of all liability for the customer's equipment.
"Your honor, the contract the customer signed (signature here, as you can see, and as the customer has acknowledged under oath) explicitly states that all responsibility and liability for the security of their own personal property lies solely on the customer..."
and fwiw the microsoft eula absolves microsoft of all liability also.
By extension of your argument, Linus is responsible for every compromised linux box. Because when you get down to it, the kernel is the absolute control of every Linux PC. The kernel in theory could stop every attack (though such a kernel would not likely be very usable). The fact it doesn't means it's Linus' fault -- not the end user's (using your arguments).
Suing Linus would surely result in a better kernel, wouldn't it?
afaik the advantage of raytracing is that you are no longer bound by polys though. you can easily have unbelievably complex scenes with little performance impact vs simple scenes. your bottleneck is no longer polys/sec but now rays/sec.
and iirc raytracing is a very simple thing to parallelize. given the performance they are getting out of their FPGA prototype, I expect this will scale nicely.
imo raytacing is the obvious future of graphics cards.
as an aside, a lot of game mechanics is dependent on raytraces for detecting collisions. now if you could use a raytracing GPU to handle that as well, you've offloaded yet more work from the CPU...:-)
a spacecraft on the surface will have to survive ~3.2 million rads/day. the galileo and cassini probes have survived short term exposures of that magnitude but they almost always got messed up pretty good (safemode at the least, permanent damage of instruments at the worst).
anything built for a surface mission would have to be unbelievably radiation hardened compared to any spacecraft flown so far.
i think it's safe to say there will be no manned europa missions for the forseeable future:-)
for any long term surface mission (more than say, 30 days) you would definitely want to burrow under the ice.
Slashdot Mirror
adolph maffie wasn't convicted of tax evasion after the statute of limitations expired. the statute of limitations on robbery was 6 years.
btw the other bank robbers were indicted just before the statute of limitations ran out. so they didn't evade it either.
Reference your quote about "pop music of today". Its not yesterday anymore and in my humble opinion its good that we aren't going back
Yeah, because britney spears and ashlee simpson is just SO much better.
fuck this worship of mediocrity.
here's a common theme i've seen in recently compromised boxes:
/16's (50mbit/sec of SYNs for example)
sniff/bruteforce non-root user's password
ftp to the user's account and upload some CGIs
run the CGIs which do password bruteforcing of entire
would be a simple task for them to forkbomb from a cgi. they don't even need shell access. just ftp and http.
disclaimer: i use subversion and cvs.
subversion still has its warts, there are places where cvs is still more convenient than subversion, and bugs/issues with properties where subversion will eat your repository for breakfast. some aspects of subversion do not scale yet.
overall subversion is much more convenient to use (especially when digging out old commits from history), you just have to be careful. cvs is more cumbersome to use, but it's rock solid -- there's never any question if it's going to eat itself.
larry's becoming a theo clone. eg great product, but all the social graces of a toad.
and you think things will get better when you're arguing on behalf of the idiot litigious customer side of things?
or is that what you really want?
i'm curious to know what correlations they did find.
one can definitively say the ratio of loud/dangerous motorcyles is orders of magnitude higher than cars though.
i notice plenty of penis extender riceboys too, but since there are so many cars on the road, the ratio of idiots is much lower.
the only thing on the road isnt huge SUVs, and i dont know anyone who says that. most of the cars are little 4d sedans and such. it's not a matter of being noticeable, its a matter of simple statistics.
if one were to go to a busy intersection or street and count idiot drivers vs idiot motorcylists in a 24hr period, the results are pretty predictable. and it isnt because one is more "noticeable" than the other. its simply because one outnumbers the other.
"not all" is generally 5%, especially for the last 2.
i have yet to see someone who didnt ride their motorcycle around as some kind of penis extender.
i'll give you one point though, i haven't heard a motorcycle yet that was loud enough to knock books off my shelves from across the street like various riceboys do. i've had picture frames shaken off my walls by motorcycle-penis-extenders, but books -- not yet.
leave it to /. readers to complain about something being too fuel efficient...
do you have an example of successful prosecutions of bank robberies after the statute of limitations expired, which used either 'continuing the conspiracy' or tax evasion, directly related to the original crime?
'reasonable effort' does not require 'absolute perfection', and 'imperfection' does not make the ISP liable.
otherwise, every little imperfection you ever made if you ever tried to do anything at all, would make you liable.
and that's simply not how it works.
so no, it really couldn't go either way. if a customer could prevail on such an argument, then it would become far too risky for any company to provide any kind of service to anyone, ever.
it would mean spamblocking and antivirus companies would be liable for every spam and virus that got through. anything less than absolute perfection, and customers would be suing left and right...
it would be impossible for companies to operate in such an environment.
and the ISP contract doesn't state that anyway. it states the ISP blocks ports to protect the ISP's infrastructure. it doesn't state it blocks ports to protect the customer.
and the client can believe the sky is green and the sun revolves around the earth. and they often do.
'tis too bad ISP customer contracts explicitly and carefully absolve the ISP of all liability for the customer's equipment.
"Your honor, the contract the customer signed (signature here, as you can see, and as the customer has acknowledged under oath) explicitly states that all responsibility and liability for the security of their own personal property lies solely on the customer..."
and fwiw the microsoft eula absolves microsoft of all liability also.
you get blamed anyway. users already blame ISPs for spam, viruses, and malware, whether they block or not.
so there's nothing to lose.
Why isn't Linus responsible for privilege escalation exploits via kernel bugs? They're used quite often to get root shells.
most ISPs do not have common carrier status. only telcos do. you cant give up something you dont have.
By extension of your argument, Linus is responsible for every compromised linux box. Because when you get down to it, the kernel is the absolute control of every Linux PC. The kernel in theory could stop every attack (though such a kernel would not likely be very usable). The fact it doesn't means it's Linus' fault -- not the end user's (using your arguments).
Suing Linus would surely result in a better kernel, wouldn't it?
but once the thing is done, they have all the time until you die to catch you.
what about the statute of limitations?
the right to use pictures and/or voice recordings of employees in advertisements.
you've just learned firsthand the collective bargaining power of worker's unions.
Broadcom hasn't released open information on any of their products.
not true. not only have they released information on their gigabit ethernet chips, they also contributed drivers to the kernel.
their wireless stuff is another story, iirc broadcom is under NDA due to some of the technology and core logic they licensed from others.
afaik the advantage of raytracing is that you are no longer bound by polys though. you can easily have unbelievably complex scenes with little performance impact vs simple scenes. your bottleneck is no longer polys/sec but now rays/sec.
:-)
and iirc raytracing is a very simple thing to parallelize. given the performance they are getting out of their FPGA prototype, I expect this will scale nicely.
imo raytacing is the obvious future of graphics cards.
as an aside, a lot of game mechanics is dependent on raytraces for detecting collisions. now if you could use a raytracing GPU to handle that as well, you've offloaded yet more work from the CPU...
amd only "recently" implemented sse? they've had it since 2001.
more recent amd chips have sse2, and sse3 on amd64 is just round the corner.
a spacecraft on the surface will have to survive ~3.2 million rads/day. the galileo and cassini probes have survived short term exposures of that magnitude but they almost always got messed up pretty good (safemode at the least, permanent damage of instruments at the worst).
:-)
anything built for a surface mission would have to be unbelievably radiation hardened compared to any spacecraft flown so far.
i think it's safe to say there will be no manned europa missions for the forseeable future
for any long term surface mission (more than say, 30 days) you would definitely want to burrow under the ice.
a database that doesnt have a field for an extension number? that would have to be a database built before 1970 or so.