I fail to see how a memory stick can blow up and hurt someone.
Fire is always a hazard when dealing with electronics. A faulty memory stick isn't very likely to explode, but it could quite possibly smoulder and burn.
Of course. Any victim of assault, sustaining a head injury no less, will remain fully collected and cognizant so that they can recall the event in full detail for the police once they've regained conciousness.
There's no way to know exactly what was going through his mind at the time, but you can be relatively certain it went a little something like this: "Holy shit, adrenaline!!" and "baseball bats hurt."
First of all, when you take something out from the library, a small royalty is actually paid out.
In what country? I'm aware of such a royalty scheme in Europe, but in the US royalties are only paid out on duplication of articles and journal issues (Periodicals. Books are never duplicated). When you request periodical material from a library, they give you a photocopy.
Even then, the library is only charged if the duplications exceed the "suggestion of five".
There is no royalty associated with loaning books to the public.
BTW, if it's an "english" sytem, why to the Americans have a different-sized "gallon" to the Imperial gallon?
America uses the old English wine gallon for all fluid measurements, which is equal to 231 cubic inches.
At the time, the Brits had a wine gallon as well as an ale gallon (282 cu. in), but they later replaced both with a unified gallon that was defined as being equal to the volume occupied by 10 avoirdupois pounds of water at a temperature of 62 F.
This change allowed convenient subdivision and equivalency between dry and liquid measurement (because the gallon is defined by the avoirdupois pound, which also applies to dry measurement). It simplified things and caught on in Britain, but wasn't adopted by the Americas.
Instead, America kept the British wine gallon and defined a fluid ounce as 1/128th of that gallon (the English ounce is 1/160th of their gallon).
It's an English system because it's an English system. It's just an old one that the English stopped using a long time ago.
As you can see, America's resistance to change has been around much longer than the metric system.
Fun fact: Avoirdupois is actually a french phrase slightly mangled together- "avoir du poids", which literally means "to have weight".
Except that you can't spoof someone else's IP and expect to receive any data destined for it. In order to phish those credit cards, you need to have a path back to yourself... One which said vigilantes will follow easily.
Phishers can't hide from or misdirect vigilantes specifically because their method of operation makes it impossible to do so.
p is not a point in space. It's a vector quantitiy consisting of mass times velocity observed at radius r (also a vector quantity) from the axis of symmetry.
L = rp sin(theta)
In this particular case, the trig function cancels itself out because we take the measurement at the equator, directly perpendicular to the axis of symmetry, and sin(90deg) = 1. Careful never to forget that you're dealing with vectors, though.
Since p = mv, the magnitudes of a planet's rotation at the equator are defined by the equation L = r x mv
The earthquake decreased r, and since m cannot change in such a local event, v must increase in order to maintain L. As luck would have it, that's exactly what happened.
Um, no he didn't. Unless it's written in the post using a font size too small for me to see... The site certainly does have a count on the front page, but the grandparent made no reference to it. And who's made any argument that Iraq is better or worse off now? Only that the US military seems to be the biggest killer of civilians at the moment.
Sensationalism, my foot. You're being presumptious.
I can see in the site's database that terrorist attacks tend to cause low numbers of casualties per incident compared to US military action. Just a couple mistargeted bombs kill off enough civvies to render all the insurgents' car bombs insignificant. There are analyses right on the site which cover this. The US was way ahead at last count.
You're article merely mentions civilian deaths, not US civilian deaths.
That do US civilian deaths have to do with Iraqi civilian deaths? Or did you ruin the sentence in your haste and actually mean US-caused civilian deaths?
"Again" I'm not properly informed? I've never even spoken to you before that post. You also failed to follow up on the article's sources, and you accuse me of being uninformed?
I'd point out the linked sources in the article, but another poster has beaten me to it.
And for the love of God, it's "your". "You're" means "you are" and is not appropriate where you've used it.
I feel as if I've just bitten on a troll. Oh well.
Your figures prompted me to do a search to see for myself, but it seems as if you've been a little selective about what to present.
The commitment period for Kyoto is between 2008-2012, so I don't think it's quite time yet to go pointing fingers at Canada for non-compliance. Their emissions growth rate has also been slowing since 1998 and it looked like it was going to receed if it hasn't started already. Seeing as Kyoto was signed in December of 1997 & ratified by Canada only as recently as December of 2002, they aren't doing too badly.
Changes like these take time, and I don't know if they're going to make it in time, but it hardly seems like they're doing nothing.
Actually, given how wired Canada is, it makes perfect sense to put content on the net even if it's only intended for local consumption. People often have net access in places they don't even have a radio, or where radio reception is poor. At the very least, they're increasing coverage over their intended audience.
15+ character passwords are overkill if you disable LM hashing, and you can bet your booty they'll get written down. Using current hardware, cracking 8 characters with numbers and punctuation will take far longer than the default NT password expiry interval.
A phrase rife with numbers, punctuation and intentional (or un-) spelling errors would be a long password that also serves as a mnemonic to aid in memorization... but if your system requests your password frequently, then such a passphrase would be very tedious to enter each time.
The case of the characters is of no consequence because the LM hashing algorithm converts everything to uppercase. If the trend in L0phtCrack's figures continues for the 3rd column in the LM hash table, we can expect that the 7-character mark will be cracked after a total of around 10-11 days. Characters beyond the 7th will be trivial due to the way the LM hashing scheme carves up the password into 7-character chunks. At best a 14-character password would only double the time required, rather that cause it to continue rising exponentially.
So no, you're not very safe. A couple weeks is a rather short amount of time for a brute force attack, and that can be drastically reduced by using beefier or distributed systems.
If we reduced software bugs mostly to the type leading to denial of service attacks, then that would be paradise compared to the situation we're in now. Why buffer overflows are still an issue really is beyond me. The worst that should happen is abnormal program termination due to a detected overflow.
This is pretty much the case for operating systems and compilers that guard the stack and enforce no_exec memory on architectures that don't do it themselves. eg: PaX-enabled Linux & gcc on x86. The OS simply terminates the app on overflow, rather than allow it to corrupt the stack or return with an altered address.
It's no silver bullet against exploitable flaws, because buffer overflows are only one of many avenues of attack... but it certainly helps.
You and those who modded you up as informative, however, failed to note that the slowdown applied only to the Inspiron line of Dell machines.
This was specified right in the summary of the article. You didn't even need to click through and read it.
You also did a clean install, which would have cleaned up the cruft from your SP1 setup very nicely...
From what we've been able to determine here by testing clean pre- and post-SP2 installs prior to rollout, SP2 is marginally more sluggish in most respects. It seems mostly processor-bound, as slower machines suffer more even if they have an abundance of other resources.
We had to put the rollout on hold, but not because of any bloat; that wasn't show-stopping. Turns out that SP2 broke some important software and we have to wait on those.
That's because cheating ruins the game. You kind of stop being frightened of monsters in the shadows if you're invincible and toting a BFG with unlimited ammo.
I never played MGS2, but if 800 hours is anywhere near accurate I think I'll avoid it. There's no way there's that much gameplay without a lot of repetition and boredom.
I have the same problem with games that have gimmiky boss battles.
Doom 3 has one very gimmicky boss like you've described, and another semi-gimmicky one. The second one is in-line with the story and kind of works, though.
The others are gimmick-free. They're just "boss" monsters because they're huge badasses.
100% correct here, but the test removed a very useful tool for detecting a phish and made a couple frauds more difficult to identify than they should have been. This no doubt skewed the results.
The tool? Just the real link location, rather than just the link text. Checking the link for a dotted quad or the wrong domain entirely is a fast way to identify a phish.
You chuckle now but did you think 10 years ago that there would be such a thing as a smartphone?
Yes I did, actually.
Bluejacking?
No, but then that's brand-specific. I was fully expecting eavesdropping, hijacking, and other malicious misuse of wireless data communications should they ever become commonplace. But I also expected that solid security would be implimented far faster and more widely than it actually has.
Nokia phone viruses?
Again, not brand-specific, but I fully expected cell phones to fall prey to malware as they became smarter. I also remember friends dismissing the idea on the basis that phones aren't computers, even after I'd remind them that there's a small computer inside the phone.
MP3s, PDFs, or PNGs that could exploit your computer?
MP3s, PDFs and PNGs can't exploit my computer. If they can exploit yours, perhaps it's time for you to switch platforms.
Do you believe Coke when they say "it can only call us" and "there's no way to hijack it"? I sure don't.
I wouldn't trust those cans, either. Even if it's only Coke that's supposed to receive through those things and assuming the cans aren't hacked, Coca Cola, Inc isn't supposed to hear classified information any more than your average citizen.
Slashdot Mirror
I fail to see how a memory stick can blow up and hurt someone.
Fire is always a hazard when dealing with electronics. A faulty memory stick isn't very likely to explode, but it could quite possibly smoulder and burn.
Fire and lanterns existed in 1883. And of course as others have pointed out, people can lie.
Of course. Any victim of assault, sustaining a head injury no less, will remain fully collected and cognizant so that they can recall the event in full detail for the police once they've regained conciousness.
There's no way to know exactly what was going through his mind at the time, but you can be relatively certain it went a little something like this:
"Holy shit, adrenaline!!" and "baseball bats hurt."
I downloaded a meg every 3 seconds using the torrent. Download completed in about 28 minutes.
First of all, when you take something out from the library, a small royalty is actually paid out.
In what country? I'm aware of such a royalty scheme in Europe, but in the US royalties are only paid out on duplication of articles and journal issues (Periodicals. Books are never duplicated). When you request periodical material from a library, they give you a photocopy.
Even then, the library is only charged if the duplications exceed the "suggestion of five".
There is no royalty associated with loaning books to the public.
BTW, if it's an "english" sytem, why to the Americans have a different-sized "gallon" to the Imperial gallon?
America uses the old English wine gallon for all fluid measurements, which is equal to 231 cubic inches.
At the time, the Brits had a wine gallon as well as an ale gallon (282 cu. in), but they later replaced both with a unified gallon that was defined as being equal to the volume occupied by 10 avoirdupois pounds of water at a temperature of 62 F.
This change allowed convenient subdivision and equivalency between dry and liquid measurement (because the gallon is defined by the avoirdupois pound, which also applies to dry measurement). It simplified things and caught on in Britain, but wasn't adopted by the Americas.
Instead, America kept the British wine gallon and defined a fluid ounce as 1/128th of that gallon (the English ounce is 1/160th of their gallon).
It's an English system because it's an English system. It's just an old one that the English stopped using a long time ago.
As you can see, America's resistance to change has been around much longer than the metric system.
Fun fact: Avoirdupois is actually a french phrase slightly mangled together- "avoir du poids", which literally means "to have weight".
Except that you can't spoof someone else's IP and expect to receive any data destined for it. In order to phish those credit cards, you need to have a path back to yourself... One which said vigilantes will follow easily.
Phishers can't hide from or misdirect vigilantes specifically because their method of operation makes it impossible to do so.
What is more to the point is what is it used for now?
4 .torrent
A quick check of my bt client shows that, right now, it's used for http://torrent.linux.duke.edu/FC4-test3-DVD-x86_6
I figure a week+ without screams of horror says this one's ready to try out.
p is not a point in space. It's a vector quantitiy consisting of mass times velocity observed at radius r (also a vector quantity) from the axis of symmetry.
L = rp sin(theta)
In this particular case, the trig function cancels itself out because we take the measurement at the equator, directly perpendicular to the axis of symmetry, and sin(90deg) = 1. Careful never to forget that you're dealing with vectors, though.
Since p = mv, the magnitudes of a planet's rotation at the equator are defined by the equation L = r x mv
The earthquake decreased r, and since m cannot change in such a local event, v must increase in order to maintain L. As luck would have it, that's exactly what happened.
And by luck, I mean the basic laws of physics.
They do copy and convert to thumbnail the pictures they index, which I imagine is a significant cost in terms of bandwidth and processing.
Instead, you take a number off the front page
Um, no he didn't. Unless it's written in the post using a font size too small for me to see... The site certainly does have a count on the front page, but the grandparent made no reference to it. And who's made any argument that Iraq is better or worse off now? Only that the US military seems to be the biggest killer of civilians at the moment.
Sensationalism, my foot. You're being presumptious.
I can see in the site's database that terrorist attacks tend to cause low numbers of casualties per incident compared to US military action. Just a couple mistargeted bombs kill off enough civvies to render all the insurgents' car bombs insignificant. There are analyses right on the site which cover this. The US was way ahead at last count.
You're article merely mentions civilian deaths, not US civilian deaths.
That do US civilian deaths have to do with Iraqi civilian deaths? Or did you ruin the sentence in your haste and actually mean US-caused civilian deaths?
"Again" I'm not properly informed? I've never even spoken to you before that post. You also failed to follow up on the article's sources, and you accuse me of being uninformed?
I'd point out the linked sources in the article, but another poster has beaten me to it.
And for the love of God, it's "your". "You're" means "you are" and is not appropriate where you've used it.
I feel as if I've just bitten on a troll. Oh well.
Also, I would recon that more innocents have been killed by their own people (i.e. suicide bombers) than have been killed by the US military.
You'd reckon, but you'd be wrong.
Your figures prompted me to do a search to see for myself, but it seems as if you've been a little selective about what to present.
The commitment period for Kyoto is between 2008-2012, so I don't think it's quite time yet to go pointing fingers at Canada for non-compliance. Their emissions growth rate has also been slowing since 1998 and it looked like it was going to receed if it hasn't started already. Seeing as Kyoto was signed in December of 1997 & ratified by Canada only as recently as December of 2002, they aren't doing too badly.
Changes like these take time, and I don't know if they're going to make it in time, but it hardly seems like they're doing nothing.
Actually, given how wired Canada is, it makes perfect sense to put content on the net even if it's only intended for local consumption. People often have net access in places they don't even have a radio, or where radio reception is poor. At the very least, they're increasing coverage over their intended audience.
15+ character passwords are overkill if you disable LM hashing, and you can bet your booty they'll get written down. Using current hardware, cracking 8 characters with numbers and punctuation will take far longer than the default NT password expiry interval.
A phrase rife with numbers, punctuation and intentional (or un-) spelling errors would be a long password that also serves as a mnemonic to aid in memorization... but if your system requests your password frequently, then such a passphrase would be very tedious to enter each time.
No, definitely this year:
;)
Lacie portable 1TB drive
Sooner than you expected, wouldn't you say?
The case of the characters is of no consequence because the LM hashing algorithm converts everything to uppercase. If the trend in L0phtCrack's figures continues for the 3rd column in the LM hash table, we can expect that the 7-character mark will be cracked after a total of around 10-11 days. Characters beyond the 7th will be trivial due to the way the LM hashing scheme carves up the password into 7-character chunks. At best a 14-character password would only double the time required, rather that cause it to continue rising exponentially.
So no, you're not very safe. A couple weeks is a rather short amount of time for a brute force attack, and that can be drastically reduced by using beefier or distributed systems.
If we reduced software bugs mostly to the type leading to denial of service attacks, then that would be paradise compared to the situation we're in now. Why buffer overflows are still an issue really is beyond me. The worst that should happen is abnormal program termination due to a detected overflow.
This is pretty much the case for operating systems and compilers that guard the stack and enforce no_exec memory on architectures that don't do it themselves. eg: PaX-enabled Linux & gcc on x86.
The OS simply terminates the app on overflow, rather than allow it to corrupt the stack or return with an altered address.
It's no silver bullet against exploitable flaws, because buffer overflows are only one of many avenues of attack... but it certainly helps.
Nice shill.
You and those who modded you up as informative, however, failed to note that the slowdown applied only to the Inspiron line of Dell machines.
This was specified right in the summary of the article. You didn't even need to click through and read it.
You also did a clean install, which would have cleaned up the cruft from your SP1 setup very nicely...
From what we've been able to determine here by testing clean pre- and post-SP2 installs prior to rollout, SP2 is marginally more sluggish in most respects. It seems mostly processor-bound, as slower machines suffer more even if they have an abundance of other resources.
We had to put the rollout on hold, but not because of any bloat; that wasn't show-stopping. Turns out that SP2 broke some important software and we have to wait on those.
At least it doesn't look like we're missing much.
That's not a typo. The display shows video of modern ruins using ascii text as the graphics. Hence the title of the work, "Ruins in ASCII".
There is irony, though, in that their webserver is now in ruins.
That's because cheating ruins the game. You kind of stop being frightened of monsters in the shadows if you're invincible and toting a BFG with unlimited ammo.
I never played MGS2, but if 800 hours is anywhere near accurate I think I'll avoid it. There's no way there's that much gameplay without a lot of repetition and boredom.
I have the same problem with games that have gimmiky boss battles.
Doom 3 has one very gimmicky boss like you've described, and another semi-gimmicky one. The second one is in-line with the story and kind of works, though.
The others are gimmick-free. They're just "boss" monsters because they're huge badasses.
100% correct here, but the test removed a very useful tool for detecting a phish and made a couple frauds more difficult to identify than they should have been. This no doubt skewed the results.
The tool? Just the real link location, rather than just the link text. Checking the link for a dotted quad or the wrong domain entirely is a fast way to identify a phish.
You chuckle now but did you think 10 years ago that there would be such a thing as a smartphone?
Yes I did, actually.
Bluejacking?
No, but then that's brand-specific. I was fully expecting eavesdropping, hijacking, and other malicious misuse of wireless data communications should they ever become commonplace. But I also expected that solid security would be implimented far faster and more widely than it actually has.
Nokia phone viruses?
Again, not brand-specific, but I fully expected cell phones to fall prey to malware as they became smarter. I also remember friends dismissing the idea on the basis that phones aren't computers, even after I'd remind them that there's a small computer inside the phone.
MP3s, PDFs, or PNGs that could exploit your computer?
MP3s, PDFs and PNGs can't exploit my computer. If they can exploit yours, perhaps it's time for you to switch platforms.
Do you believe Coke when they say "it can only call us" and "there's no way to hijack it"? I sure don't.
I wouldn't trust those cans, either. Even if it's only Coke that's supposed to receive through those things and assuming the cans aren't hacked, Coca Cola, Inc isn't supposed to hear classified information any more than your average citizen.