On an aside.. I thought the original article discussion was about banning handsets by ESN. All that is required to do this is to have a centralized ESN registry of stolen handsets and an agreement from carriers to refuse service to stolen ESN's. It wold be more effective than software on the phone, mainly because it works with ALL handsets, regardless of their type and cannot be undone by anything short of changing the ESN, which is not generally something just anybody can do beyond the manufacturer.
You're looking at the wrong level. The proposal was for software embedded in the phone (not the HLR) so that it would brick if it received the right command. So no need to corrupt the HLR at all, just send the brick yourself command to the phones.
This.
Why do all that work, just tell the phone to do the work for you! If this gets implemented, that is...
I don't think that is what they where discussing. I thought it was about banning the ESN at the carrier level. This would effectively render the handset unserviceable by any carrier that refused to service the ESN. No need to put software on the phone.
You're looking at the wrong level. The proposal was for software embedded in the phone (not the HLR) so that it would brick if it received the right command. So no need to corrupt the HLR at all, just send the brick yourself command to the phones.
I was responding to the previous post.
... until someone hacks into a carriers network, and deactivates and wipes EVERY PHONE on the carriers registry.
This registry in the carrier's network is the HLR infrastructure. Nothing else fits the description the previous author was discussing. Now if the previous author was at the wrong level, take it up with them.
Shifting to neutral with the throttle wide open WOULD blow the engine complete with thick blue smoke everywhere and possibly fire.
I'm no expert in engine control units, but.... I'm told that they have rev limiters built in to avoid having the engine come apart under the conditions you describe. Manufacturers generally don't like replacing engines, and if it was that easy to blow one up, you can bet there would be a rash of "Oh my gosh, it's 1,000 miles before my drive train warranty dies" engine blow ups.
The push button start thingy does complicate things, but neutral is still an option when faced with freeway traffic and uncontrolled acceleration. Personally, I'd rather buy an engine than crash my car going in excess of 60 MPH, but I doubt it would come to that.
If I'm a carrier, why would I NOT want to sell service to whomever stole your phone?
Since the carriers have no culpability in the theft of your device, the legal fiduciary obligation to the shareholders trumps any perceived moral obligation to you.
But they WILL refuse to service a phone that is on a delinquent account. That's what BAD ESN means. If they think you still owe them money on the "contract" you can bet they will refuse to allow the phone to be used on their network.
... until someone hacks into a carriers network, and deactivates and wipes EVERY PHONE on the carriers registry.
Not going to happen for two reasons.
1. There are multiple HLR's (Home Location Registers) in almost every carrier's network. This is where the subscriber information is kept and they are fully redundant (i.e. have multiple copies in the network). In order to kill everybody in a carrier's network, you are going to have to disrupt multiple HLR's and all of the redundancy built into the network.
2. The configuration interface of an HLR is very isolated and allowed transactions are limited to a single handset at a time. There is no way to bulk erase the database from the public interface of the HLR, you are going to have to get access INSIDE of the HLR. Trying to disrupt a network one handset at a time will take a LONG time and I'd bet they'd figure out what was happening and shut down the public HLR interface before you get very far.
But even if you did manage to break into multiple HLR's and their redundant backups and bulk erase their subscriber data, you have the problem of the VLR (Visitor Location Register) which is what the network *actually* uses when dealing with your handset. The local MSC (Mobil Switch Center) which runs the cell your phone is in only consults the HLR when it first sees your handset or you receive a call, loads the data from the HLR into the VLR. MSC's usually cover fairly large geographic areas, so even if the HLR's are trashed, most people's handsets will still work great for making calls. Receiving calls and voice mail might be more of an issue but how do you know you didn't receive a call or a voice mail didn't get collected?
Then there is the problem with backups. You KNOW that they keep backups of the HLR data. I've seen an HLR that used Oracle as it's back end. They kept *hourly* snapshots to disk and *daily* complete backups. Plus they copied off the transaction logs as soon as they where written by Oracle. If you managed to corrupt their on disk data in the HLR, they could get the HLR restored to within an hour of your attack in less than an hour, then recover the HLR to exactly what it should be by inspecting the transaction logs and just taking out the bogus deletes. It would be a pain, but the bulk of the disruption would be short lived.
If his lawsuit is about fracking, then SlashDot is about rocket science because it sometimes has articles about NASA.
His primary complaint is about how the water tower will ruin the view from his deck, the rest of the lawsuit is every other reason he can come up including the kitchen sink for not building the tower in a specific place. It's common in lawsuits to come up with *every* possible reason you can think of, no matter how unlikely, just in the slight chance one of these reasons stick or perhaps scare the defendant into a settlement by the shear volume of the lawsuit and the costs of defending themselves on every single point you bring up.
I'm guessing he's going to loose, so why not let him opine with abandon? After it's all said and done, and the tower goes up, he won't be able to complain he was unfairly treated or not listened to. That he squandered his chance, is all the better..
Seriously?... Forbes throws up a headline like that and if you RTFA it's all about a freaking municipal water tower... only a single throw-away line about the tower providing water to a nearby drilling operation. That's quite a stretch... What a troll!
Welcome to Environmentalist Wack-o's view of the world. Any angle that might snag some unsuspecting soul and help further their cause. They do this kind of thing ALL the time.
Just a nit pick here.. But Water Towers don't "provide" water, they are part of the distribution system. The water must be obtained from some kind of source like a well or lake.
Problem here is that the height of a water tower is related to the working pressure of the distribution system. So a low rise tower would cause the distribution system to be redesigned to work at lower pressures.
But I'm not clear how THIS tower has any direct impact on the fracking activity. Water for fracking is usually delivered to the well head by tanker truck and not the water mains.
Yea, I've seen such cars. Usually key-less cars are the exception and come at a premium so I'm guessing the owners of a Toyota are not usually going to have such options. But, in all cases there are TWO things you can do. 1. Turn it off (however the car is designed to accomplish this) and 2. put it in neutral. Both will cause the car to eventually stop. If you have the presence of mind and can accomplish either of the previous things, you can assist in the stopping of the car by doing one of two things.. 1. Depressing the break peddle or 2. Applying the emergency break.
Driving car 101 should teach this. Where is Driver's Education these days?
Turning off the ignition might help with the acceleration, but not with replenishing the vacuum assistance.
Breaks and steering both work reasonably well when the engine stops running. Breaking will function just fine until you exhaust the vacuum stored in the canister, you will be god for one or two full peddle depressions before there will be noticeable increase in stopping distance. Even then, stopping just takes a bit more pressure which in panic situation shouldn't be too much of an issue for just about anybody. So I'm not so ready to just let these lame brain drivers off the hook. Taking your food off the peddle will likely fix the problem (because you are on the wrong one) and if that doesn't work, turn off the car. You will stop.
Yep, but if they try to use the evidence in court, two things will happen. 1. They will have to prove the evidence was legally collected (i.e. they had a warrant) and 2.They will have to disclose to the defendant what the evidence actually is before the trial. Pesky little constitution...
Recursion is lazy, stupid, and above all, DANGEROUS.
Only in the hands of a novice..
It is an elegant solution for certain kinds of problems that can work magic in the hands of one who has mastered the technique. But when applied to the wrong problem, it's what you describe.
As in all things, the right tool for the job is always best. Masters of the trade know their tools well.
Even easier is to just TURN IT OFF using the key and get on the breaks. Trust me, the car WILL stop running and come to a full stop fairly quick. Don't worry when the key won't come out, the steering wheel will work with a bit of effort, just turn the key as far as you can. Coast to a safe place, stop, put the car in park and remove the key. THEN check your floor mats.... If you see nothing wrong, start the car and if everything is normal again, continue on your way.
What do they teach people in drivers education these days..
Until someone actually reproduces the bug I'd say the loose floor mat explanation is just as credible.
I'm actually going for "operator error" but hey...
Two cases come to mind. First, was short term unintended acceleration. Probable cause for that is hitting the wrong or both peddles.
Long term acceleration on the highway? Nobody thought to just turn off the ignition switch? Turns off the fuel pump, care stops running, eventually you come to full stop.
Slashdot Mirror
On an aside.. I thought the original article discussion was about banning handsets by ESN. All that is required to do this is to have a centralized ESN registry of stolen handsets and an agreement from carriers to refuse service to stolen ESN's. It wold be more effective than software on the phone, mainly because it works with ALL handsets, regardless of their type and cannot be undone by anything short of changing the ESN, which is not generally something just anybody can do beyond the manufacturer.
You're looking at the wrong level. The proposal was for software embedded in the phone (not the HLR) so that it would brick if it received the right command. So no need to corrupt the HLR at all, just send the brick yourself command to the phones.
This.
Why do all that work, just tell the phone to do the work for you! If this gets implemented, that is...
I don't think that is what they where discussing. I thought it was about banning the ESN at the carrier level. This would effectively render the handset unserviceable by any carrier that refused to service the ESN. No need to put software on the phone.
You're looking at the wrong level. The proposal was for software embedded in the phone (not the HLR) so that it would brick if it received the right command. So no need to corrupt the HLR at all, just send the brick yourself command to the phones.
I was responding to the previous post.
... until someone hacks into a carriers network, and deactivates and wipes EVERY PHONE on the carriers registry.
This registry in the carrier's network is the HLR infrastructure. Nothing else fits the description the previous author was discussing. Now if the previous author was at the wrong level, take it up with them.
Shifting to neutral with the throttle wide open WOULD blow the engine complete with thick blue smoke everywhere and possibly fire.
I'm no expert in engine control units, but.... I'm told that they have rev limiters built in to avoid having the engine come apart under the conditions you describe. Manufacturers generally don't like replacing engines, and if it was that easy to blow one up, you can bet there would be a rash of "Oh my gosh, it's 1,000 miles before my drive train warranty dies" engine blow ups.
The push button start thingy does complicate things, but neutral is still an option when faced with freeway traffic and uncontrolled acceleration. Personally, I'd rather buy an engine than crash my car going in excess of 60 MPH, but I doubt it would come to that.
If I'm a carrier, why would I NOT want to sell service to whomever stole your phone?
Since the carriers have no culpability in the theft of your device, the legal fiduciary obligation to the shareholders trumps any perceived moral obligation to you.
But they WILL refuse to service a phone that is on a delinquent account. That's what BAD ESN means. If they think you still owe them money on the "contract" you can bet they will refuse to allow the phone to be used on their network.
... until someone hacks into a carriers network, and deactivates and wipes EVERY PHONE on the carriers registry.
Not going to happen for two reasons.
1. There are multiple HLR's (Home Location Registers) in almost every carrier's network. This is where the subscriber information is kept and they are fully redundant (i.e. have multiple copies in the network). In order to kill everybody in a carrier's network, you are going to have to disrupt multiple HLR's and all of the redundancy built into the network.
2. The configuration interface of an HLR is very isolated and allowed transactions are limited to a single handset at a time. There is no way to bulk erase the database from the public interface of the HLR, you are going to have to get access INSIDE of the HLR. Trying to disrupt a network one handset at a time will take a LONG time and I'd bet they'd figure out what was happening and shut down the public HLR interface before you get very far.
But even if you did manage to break into multiple HLR's and their redundant backups and bulk erase their subscriber data, you have the problem of the VLR (Visitor Location Register) which is what the network *actually* uses when dealing with your handset. The local MSC (Mobil Switch Center) which runs the cell your phone is in only consults the HLR when it first sees your handset or you receive a call, loads the data from the HLR into the VLR. MSC's usually cover fairly large geographic areas, so even if the HLR's are trashed, most people's handsets will still work great for making calls. Receiving calls and voice mail might be more of an issue but how do you know you didn't receive a call or a voice mail didn't get collected?
Then there is the problem with backups. You KNOW that they keep backups of the HLR data. I've seen an HLR that used Oracle as it's back end. They kept *hourly* snapshots to disk and *daily* complete backups. Plus they copied off the transaction logs as soon as they where written by Oracle. If you managed to corrupt their on disk data in the HLR, they could get the HLR restored to within an hour of your attack in less than an hour, then recover the HLR to exactly what it should be by inspecting the transaction logs and just taking out the bogus deletes. It would be a pain, but the bulk of the disruption would be short lived.
Good luck, you are going to need it.
Shudder.... Man How did you KNOW I used to have a Beatles like haircut?
Sorry about my usage failure. I'll do better next time..
So yes it's about fracking....idiot...
If his lawsuit is about fracking, then SlashDot is about rocket science because it sometimes has articles about NASA.
His primary complaint is about how the water tower will ruin the view from his deck, the rest of the lawsuit is every other reason he can come up including the kitchen sink for not building the tower in a specific place. It's common in lawsuits to come up with *every* possible reason you can think of, no matter how unlikely, just in the slight chance one of these reasons stick or perhaps scare the defendant into a settlement by the shear volume of the lawsuit and the costs of defending themselves on every single point you bring up.
I'm guessing he's going to loose, so why not let him opine with abandon? After it's all said and done, and the tower goes up, he won't be able to complain he was unfairly treated or not listened to. That he squandered his chance, is all the better..
Seriously?... Forbes throws up a headline like that and if you RTFA it's all about a freaking municipal water tower... only a single throw-away line about the tower providing water to a nearby drilling operation. That's quite a stretch... What a troll!
Welcome to Environmentalist Wack-o's view of the world. Any angle that might snag some unsuspecting soul and help further their cause. They do this kind of thing ALL the time.
which water towers provide.
Just a nit pick here.. But Water Towers don't "provide" water, they are part of the distribution system. The water must be obtained from some kind of source like a well or lake.
Problem here is that the height of a water tower is related to the working pressure of the distribution system. So a low rise tower would cause the distribution system to be redesigned to work at lower pressures.
But I'm not clear how THIS tower has any direct impact on the fracking activity. Water for fracking is usually delivered to the well head by tanker truck and not the water mains.
Driving car 101 should teach this. Where is Driver's Education these days?
Full Stop
Turning off the ignition might help with the acceleration, but not with replenishing the vacuum assistance.
Breaks and steering both work reasonably well when the engine stops running. Breaking will function just fine until you exhaust the vacuum stored in the canister, you will be god for one or two full peddle depressions before there will be noticeable increase in stopping distance. Even then, stopping just takes a bit more pressure which in panic situation shouldn't be too much of an issue for just about anybody. So I'm not so ready to just let these lame brain drivers off the hook. Taking your food off the peddle will likely fix the problem (because you are on the wrong one) and if that doesn't work, turn off the car. You will stop.
full stop
Yep, but if they try to use the evidence in court, two things will happen. 1. They will have to prove the evidence was legally collected (i.e. they had a warrant) and 2.They will have to disclose to the defendant what the evidence actually is before the trial. Pesky little constitution...
The one with the scorched paint that caught fire when I was driving it? Wow, I thought that went to the junk heap back in the 80's
Recursion is lazy, stupid, and above all, DANGEROUS.
Only in the hands of a novice..
It is an elegant solution for certain kinds of problems that can work magic in the hands of one who has mastered the technique. But when applied to the wrong problem, it's what you describe.
As in all things, the right tool for the job is always best. Masters of the trade know their tools well.
The death penalty for programmers that write such code will bring an end to this OUTRAGE !
I'm shocked, SHOCKED that our software has bugs!
Your bug reports sir!
Carry on...
No software. No seat belts. No automatic..anything.
In Chicago in a snow storm during rush hour? No thanks!
Even easier is to just TURN IT OFF using the key and get on the breaks. Trust me, the car WILL stop running and come to a full stop fairly quick. Don't worry when the key won't come out, the steering wheel will work with a bit of effort, just turn the key as far as you can. Coast to a safe place, stop, put the car in park and remove the key. THEN check your floor mats.... If you see nothing wrong, start the car and if everything is normal again, continue on your way.
What do they teach people in drivers education these days..
Until someone actually reproduces the bug I'd say the loose floor mat explanation is just as credible.
I'm actually going for "operator error" but hey...
Two cases come to mind. First, was short term unintended acceleration. Probable cause for that is hitting the wrong or both peddles.
Long term acceleration on the highway? Nobody thought to just turn off the ignition switch? Turns off the fuel pump, care stops running, eventually you come to full stop.
BOTH where operator error..
He definitely wasn't in charge of network security.
Systems that generate passwords like that - that you can't change - pretty much demand users write them down on a post-it note under their keyboard :(
Yea. Stupid rules end up with stupid results, and having passwords that are too complex is nuts.
To late, I stole your wallet this morning and already logged into your bank and drained your accounts.
That's quite a trick, because before you can figure out the account name I used for the passwords you have, you are going to have to know the code.
So, I have passwords on paper, but I'm going to guess you won't come up with the *real* password any time soon.
Here, give it a try... My managed switch at home: "09"
Let me know what the password is...
I'm a preposterous penis pumping extremist! Bow before me, Slashdot!
Dude, you are hard core..
Why bother with SCO? In China you just compile Linux and distribute it in binary form calling it your own. = PROFIT
If you are smart you remove all the license references, but that actually involves reading English (and other languages) so why bother?