It's not so much "Redundant, because somebody just said that two posts higher," as it is "Redundant, because we've seen that for the past 28,751/. stories...."
It'll essentially mean that you'll need a licence to program. The big software companies will love that - probably lobby for it - because it'll immediately put a lot of their smaller competition out of business, and their profits will go up, so the shareholders will love it.
5 years down the road, we'll start seeing spot shortages of good programmers, as old ones retire and the new ones all suck. Then big software company profits will go down, and they'll need to lobby for a new law that requires you to buy their products, which will continue to suck more and more.
It happened a few years ago. I used to have a link on my website, but the article expired from the news service, and I never bothered to track any more down.
About the only simpler method than that (other than looking for PostIts...) is to ask somebody who's done it a few times before, "Hey! Can you crack this network?"
That's right, many people live in areas where bandwidth isn't free.
I do, too. But I have a grandfathered account from when my ISP offered unlimited. Anybody new signing up gets a cap, and anybody changing anything on their account (different speed, even getting a new modem) gets the cap added. If my rented modem screws up, I'll just buy one myself and use it, as the $2 a month modem rental is less than the bandwidth costs I'd have to pay if I had the cap. Running a tor exit node gets you GBs of traffic a day.....
Your education is your responsibility. It's assumed that if you're installing a wifi router, you will do your homework on how to set it up and read all the included documentation.
The local major DSL provider to me used to provide DSL modem/routers to their customers with built in wireless. The wireless was disabled by default. When you went through the initial setup, though (had to do it before the router would let you online) it encouraged you - strongly...it would have been hard for a non-techie user to figure out how to avoid it - to enable wireless. When setting up the encryption, it had four radio button options that looked like this:
O No encryption. O 64 bit WEP O 128 bit WEP (recommended) O WPA-PSK
So the recommended option was something that could be broken into in 15 minutes or so.
About a year ago, they stopped distributing those routers, and started sending out a different type, that come by default with 128 bit WEP enabled, and with the customer's username/password pre-programmed, so the documentation just says "Your router is preconfigured. Just plug it in, and it will connect and work properly."
Microsoft's web site says if you must use WEP, change your key once a month, so if somebody gets the key, they'll be locked out again. So out of the 43200 minutes in an average month, you'll only be vulnerable for 43185 of them if you follow Microsoft's advice.
Most of the computer stores in my city are still using WEP on their networks. If the customer hires them to set up their network properly, they'll still end up hackable.
Then, on top of that, very few techs even know of the vulnerabilities in WPA. If you use a passphrase that's in a dictionary/wordlist/phraselist somewhere, you can still be broken into, even using WPA. It's a little harder, as it requires a legitimately connected client, which WEP doesn't, but it also doesn't require anywhere near the amount of wireless traffic collection that WEP does. 30 seconds will typically be long enough to collect the data you need, then you can go crack remotely, whereas WEP requires 5-15 minutes worth of data collection.
The bottom line is, you can't trust the documentation, you can't trust the advice from the "experts," and you can't trust articles you read on the Internet. The only real way to be secure is to ask somebody who knows how to break into these things if they can break into yours. If they can't, you're probably safe.
My parents bought a Tandy Co-co in 1981 or so, and I didn't see an IBM compatible till later in public school, running Ednet, and then in high school, in a real network. The Coco had 9 colour graphics in BASIC, and 256 colour graphics in machine language, could repaint the screen in a matter of 1/4 of a second or so, even in BASIC. When I got to high school, which was 7 or 8 years after getting the Coco, the state of the art IBM compatible machines they had could repaint the screen in roughly 15 minutes, one pixel at a @#%$ time.
I remember frequently having to co-opt the 286 server to get some of my graphics programming done, because the XT client machines were so blasted slow. They'd take 1/2 hour to paint the screen.
There are people who already can't see what's plain as day ahead of them.
You want to add the distraction of a HUD, with little moving blips and sprites in front of their face, so they're even worse drivers?
Sure, it works in fighter jets, but fighter pilots, for a start, are highly trained, and probably strung piano-wire taught the entire time they're flying. Also, the HUD in a fighter tends to give you information you'd need to look elsewhere for otherwise, or it helps enhance the view in front of you. Like, highlighting the plane you're shooting at with a red bracket.
Car drivers, on the other hand, are rarely trained at all, already distracted by their kids, radio, dinner, cigarette, etc. A HUD for GPS navigation wouldn't highlight the car they're going to run into, it would cover it up with a street name. It wouldn't give them speed and fuel indicators, so they don't have to look at the dash.
For a few people, yes, it would work very well. For the vast majority, it would be a nightmare.
In MINUTES you could saturate a ceiling panel with enough H2 to reach 5% mix, and then all someone has to do is smoke a ciggarette, or clip their anteanna on a ceiling tile. BOOM!
How many smokers do you know that are either 10 feet tall, or hurl their still burning cigarette butts up in the air when they're finished with them? Because that's the situation you'd need in an area with a car with a massive leak to get that kind of explosion.
And clipping their antenna on a ceiling tile? Seriously? When's the last time you saw a car with an antenna? Redneck CB toting pickup trucks notwithstanding, but how many of those are going to end up in parking garages, anyway? Besides, antennas are stainless steel, and virtually impossible to get to spark on something like cement, which is what all these parking garages are made of.
And the last point: if it takes say 3-4 minutes for a moderate leak to saturate a ceiling panel with enough H2 to reach the magical explosive mixture, then you have to ask, how long would it take a saturated ceiling to dissipate in an average modern parking garage? If it's less than 3-4 minutes, you're never going to reach that saturation point, because equilibrium kicks in before then. Thinking of every above ground parking garage I've ever seen, they all have the sloped ceilings I've already mentioned. Now imagine a 50 gallon tank of water on the third level of one of these buildings. Drill a hole in the bottom of the tank, and the water will pour out, down to the floor, then run down the slope, around the corner, and eventually out of the exit. Even if the tank suddenly split right down the middle, and the entire 50 gallons spilt on the floor in a matter of 5 seconds, it's still going to pour downhill in a big hurry, and be virtually gone in a matter of 10 seconds or less. The exact same thing happens with a hydrogen leak, only it goes up to the ceiling and pours uphill, instead, eventually leaving the building by the uncovered top level. Now, the mass:volume ratio of water:air is higher than air:hydrogen, so it's going to take a little longer, but even if it takes 10 times as long, that's still well under 2 minutes. Wind effects will also help dissipate hydrogen even quicker, whereas water (and gasoline) is too heavy to be affected. Fluidity of hydrogen is also higher, so that will speed things up, too.
Seriously, you sound like Professor Frink, with the death, and the explosions, and the crying.....
Windows is a sleek, supercharged Dodge Viper with a flaky brake system, no seatbelts or airbags, and an accelerator that sticks down.
BSD and Linux are Volvos, with airbags galore, crumple zones bigger than most small cars, 4 wheel ceramic disc brakes, and bodywork that appears stodgy to fashionistas.
You can crash either one. But the Viper is a lot more dangerous in untrained hands.
Slashdot Mirror
The judge is probably a Monty Python fan, and he's going to let the whole trial go through.
Then, at the end, he's going to say:
"I'm ruling against Wells Fargo, and in favour of Wells Fargo."
Then, promptly get up from the bench, and return to his chamber, all the while laughing at the sound of lawyer's heads exploding in the courtroom.
Because if your network card driver has a buffer overflow in it, you can still get hacked.
Although that might be true even with a firewall.
But there are definitely more possibilities of successful overflows without a firewall than with.
Yeah.
It's not so much "Redundant, because somebody just said that two posts higher," as it is "Redundant, because we've seen that for the past 28,751 /. stories...."
Do you think lawmakers will care about that?
It'll essentially mean that you'll need a licence to program. The big software companies will love that - probably lobby for it - because it'll immediately put a lot of their smaller competition out of business, and their profits will go up, so the shareholders will love it.
5 years down the road, we'll start seeing spot shortages of good programmers, as old ones retire and the new ones all suck. Then big software company profits will go down, and they'll need to lobby for a new law that requires you to buy their products, which will continue to suck more and more.
all nerds worldwide have an ascii chart, complete with hex and binary representation, taped up behind their monitor on their parents basement wall.
n00b.
Real nerds have no need for that chart, as they've got all those codes memorized.
It happened a few years ago. I used to have a link on my website, but the article expired from the news service, and I never bothered to track any more down.
I didn't think anybody at IBM threw chairs.....
About the only simpler method than that (other than looking for PostIts...) is to ask somebody who's done it a few times before, "Hey! Can you crack this network?"
Seriously....that method's not complicated.
That's right, many people live in areas where bandwidth isn't free.
I do, too. But I have a grandfathered account from when my ISP offered unlimited. Anybody new signing up gets a cap, and anybody changing anything on their account (different speed, even getting a new modem) gets the cap added.
If my rented modem screws up, I'll just buy one myself and use it, as the $2 a month modem rental is less than the bandwidth costs I'd have to pay if I had the cap. Running a tor exit node gets you GBs of traffic a day.....
Don't bet on it.
Your education is your responsibility. It's assumed that if you're installing a wifi router, you will do your homework on how to set it up and read all the included documentation.
The local major DSL provider to me used to provide DSL modem/routers to their customers with built in wireless. The wireless was disabled by default.
When you went through the initial setup, though (had to do it before the router would let you online) it encouraged you - strongly...it would have been hard for a non-techie user to figure out how to avoid it - to enable wireless.
When setting up the encryption, it had four radio button options that looked like this:
O No encryption.
O 64 bit WEP
O 128 bit WEP (recommended)
O WPA-PSK
So the recommended option was something that could be broken into in 15 minutes or so.
About a year ago, they stopped distributing those routers, and started sending out a different type, that come by default with 128 bit WEP enabled, and with the customer's username/password pre-programmed, so the documentation just says "Your router is preconfigured. Just plug it in, and it will connect and work properly."
Microsoft's web site says if you must use WEP, change your key once a month, so if somebody gets the key, they'll be locked out again. So out of the 43200 minutes in an average month, you'll only be vulnerable for 43185 of them if you follow Microsoft's advice.
Most of the computer stores in my city are still using WEP on their networks. If the customer hires them to set up their network properly, they'll still end up hackable.
Then, on top of that, very few techs even know of the vulnerabilities in WPA. If you use a passphrase that's in a dictionary/wordlist/phraselist somewhere, you can still be broken into, even using WPA. It's a little harder, as it requires a legitimately connected client, which WEP doesn't, but it also doesn't require anywhere near the amount of wireless traffic collection that WEP does.
30 seconds will typically be long enough to collect the data you need, then you can go crack remotely, whereas WEP requires 5-15 minutes worth of data collection.
The bottom line is, you can't trust the documentation, you can't trust the advice from the "experts," and you can't trust articles you read on the Internet. The only real way to be secure is to ask somebody who knows how to break into these things if they can break into yours. If they can't, you're probably safe.
He had scars, not holes. That sounds like healing damage to me.
Similar here.
My parents bought a Tandy Co-co in 1981 or so, and I didn't see an IBM compatible till later in public school, running Ednet, and then in high school, in a real network.
The Coco had 9 colour graphics in BASIC, and 256 colour graphics in machine language, could repaint the screen in a matter of 1/4 of a second or so, even in BASIC.
When I got to high school, which was 7 or 8 years after getting the Coco, the state of the art IBM compatible machines they had could repaint the screen in roughly 15 minutes, one pixel at a @#%$ time.
I remember frequently having to co-opt the 286 server to get some of my graphics programming done, because the XT client machines were so blasted slow. They'd take 1/2 hour to paint the screen.
and boaters (large water) use them extensively aswell.
Turn left on water road in 200 metres. Proceed one kilometre before turning right on water place.
Water street is 300 metres on, on the left.
You are on the beach. Recalculating route.......
There are people who already can't see what's plain as day ahead of them.
You want to add the distraction of a HUD, with little moving blips and sprites in front of their face, so they're even worse drivers?
Sure, it works in fighter jets, but fighter pilots, for a start, are highly trained, and probably strung piano-wire taught the entire time they're flying. Also, the HUD in a fighter tends to give you information you'd need to look elsewhere for otherwise, or it helps enhance the view in front of you. Like, highlighting the plane you're shooting at with a red bracket.
Car drivers, on the other hand, are rarely trained at all, already distracted by their kids, radio, dinner, cigarette, etc. A HUD for GPS navigation wouldn't highlight the car they're going to run into, it would cover it up with a street name. It wouldn't give them speed and fuel indicators, so they don't have to look at the dash.
For a few people, yes, it would work very well. For the vast majority, it would be a nightmare.
....says Andrew DiMarcangelo. "I want to get into my car and do as few things as possible."
I don't want to do anything extra, such as:
- using my mirrors
- using my turn signals
- paying attention to traffic
- planning lane changes ahead of time
- thinking
That sounds like most of the drivers around where I live.... :-)
In MINUTES you could saturate a ceiling panel with enough H2 to reach 5% mix, and then all someone has to do is smoke a ciggarette, or clip their anteanna on a ceiling tile. BOOM!
How many smokers do you know that are either 10 feet tall, or hurl their still burning cigarette butts up in the air when they're finished with them? Because that's the situation you'd need in an area with a car with a massive leak to get that kind of explosion.
And clipping their antenna on a ceiling tile? Seriously? When's the last time you saw a car with an antenna? Redneck CB toting pickup trucks notwithstanding, but how many of those are going to end up in parking garages, anyway?
Besides, antennas are stainless steel, and virtually impossible to get to spark on something like cement, which is what all these parking garages are made of.
And the last point: if it takes say 3-4 minutes for a moderate leak to saturate a ceiling panel with enough H2 to reach the magical explosive mixture, then you have to ask, how long would it take a saturated ceiling to dissipate in an average modern parking garage?
If it's less than 3-4 minutes, you're never going to reach that saturation point, because equilibrium kicks in before then.
Thinking of every above ground parking garage I've ever seen, they all have the sloped ceilings I've already mentioned. Now imagine a 50 gallon tank of water on the third level of one of these buildings. Drill a hole in the bottom of the tank, and the water will pour out, down to the floor, then run down the slope, around the corner, and eventually out of the exit. Even if the tank suddenly split right down the middle, and the entire 50 gallons spilt on the floor in a matter of 5 seconds, it's still going to pour downhill in a big hurry, and be virtually gone in a matter of 10 seconds or less.
The exact same thing happens with a hydrogen leak, only it goes up to the ceiling and pours uphill, instead, eventually leaving the building by the uncovered top level.
Now, the mass:volume ratio of water:air is higher than air:hydrogen, so it's going to take a little longer, but even if it takes 10 times as long, that's still well under 2 minutes.
Wind effects will also help dissipate hydrogen even quicker, whereas water (and gasoline) is too heavy to be affected. Fluidity of hydrogen is also higher, so that will speed things up, too.
Seriously, you sound like Professor Frink, with the death, and the explosions, and the crying.....
You mean:
VTF vith the "v"s everyvhere?
Let's see....inversely proportional...that would mean, when one is high, the other is low.
So a high level of tech knowledge, means a low level of body odour strength.
Good going. You're so stupid you even screw up the simplest flame.
Do you use Windows, by any chance?
Windows is a sleek, supercharged Dodge Viper with a flaky brake system, no seatbelts or airbags, and an accelerator that sticks down.
BSD and Linux are Volvos, with airbags galore, crumple zones bigger than most small cars, 4 wheel ceramic disc brakes, and bodywork that appears stodgy to fashionistas.
You can crash either one. But the Viper is a lot more dangerous in untrained hands.
That prevents your infected OS from writing nasty stuff to your USB drive.
But that's not what the GP was talking about.
What he's meaning is some way to prevent the infected USB drive from installing nasty stuff to the OS on the internal hard drive.
Well then, we just send somebody to the sun with a couple of really long hoses, so we can dump excess helium, and suck up some new hydrogen.
Ah...I get it.
When I first read it, though, the original post was also modded offtopic.
That's my story and I'm sticking to it.
When you burn hydrogen in a fuel cell or internal combustion engine, you get - shock of shocks - water.
As long as we keep using the fuel we generate like this, there will never be a lack of water.
If only Monty Python was still going.....