Well, I can say for a fact that even if such authentication is in place, Sprint's network doesn't care.
And I've even got an ESN device cloned to a MEID device's pESN, so this one should be even easier to detect. (Although, I am careful to never have both phones powered on at the same time.)
(Just in case this is needed... both phones are legally owned by me, and this is not being used to steal service or intercept calls or text messages. I suspect that there may be more checks put in place if someone complains about calls being made that they never made. And, I don't know how the system responds to multiple phones with the same MEID/ESN/pESN on the network at once, and don't care to find out. The reason why I have this cloned is because I have an old pre-E911 device that cannot legally be activated on any network due to FCC mandate, and cloning is the only way to use it. If it were E911 compliant, I could just MEID/ESN swap on Sprint's website and be done with it, when I want to use it. (Although, it is nice to have a backup phone that I don't have to call Sprint or have internet access to use.))
Knowing the general gist of how cellular protocols work, I don't think there is anything they're not telling us. It's just that most phones don't have reprogrammable IMEIs, for very obvious reasons.
Although, I didn't think GSM phones even authenticated via the IMEI normally, just via the info on the SIM, so cloning the SIM would be enough. Guess I was wrong.
CDMA phones do authenticate via the MEID or ESN (or pESN, an encoded form of the MEID, for backwards compatibility with equipment that can't handle MEIDs,) meaning such an attack would be VERY effective on CDMA. And, a lot of older CDMA equipment has the ESN such that it's not too hard to reprogram with the right software.
Or, to do it perfectly, clean-room it. Have one team create an internal ODF spec based on the OpenOffice source. Give that spec along with the OpenOffice source to the lawyers, have them approve it. Give the spec to your Office devs.
What about Korea? Also, quite a few "European" and "Asian" cars are built right here in the US by non-union labor.
And, the American automotive industry didn't have to try to convince people here that they "needed" to drive a tank to work - people were all too willing to buy tanks, so they reacted by building more tanks. Which happened to be high profit margin.
Granted, they should've put more funds into engineering efficient cars, to plan for the contingency of tanks no longer making sense.
What happened was not that unions failed to take hold, but rather that unions took hold too well, to the point that they started choking the industries that they really deeply took hold in (automotive manufacturing and public education, mainly.)
Whether that's true or not (I'm leaning towards not, but it's irrelevant to my reply,) the people in question have no fucking clue what Windows, or Mac OS, or Linux is. They may not even know what a computer is. They've got much more immediate needs, and they aren't poor because of Windows.
Abort tells it to abort the operation - for example, if you're copying files, and there's a disk error, Abort will stop the copy altogether.
Fail tells it to fail just that stage of the operation - for the copying files example, that sector or that file won't copy, but the rest of the copy operation will continue.
And, you missed Ignore, which is a special version of fail - it tells it to use the erroneous data anyway.
Better yet, look in this PDF for 4:3 models or this one for widescreens, for the part and FRU numbers. Google both. You may be able to even get an upgrade out of this, compare part numbers on the hinges, cables, and inverter.
Well, the Crusoe did enable x86 to push into the handheld computing market. Although, MIDs and UMPCs haven't exactly taken off, but the Crusoe got the market open for long enough for Intel to bring their entries into the market (the Intel A100 and A110 (underclocked Dothan Pentium Ms,) and later the Atom.)
Although Anonymous probably would rather stuff the box with marblecake or something instead. (And I'd say to stuff it with Xenu or body thetans, but Scienos would agree that that's bad.)
If you had said the Nokia 1100, I might have not said you were insane.
But the Jitterbug? Seriously? For starters, it has a color screen - something that the Slashdot favorite "basic phone" doesn't have at all. And, second, it costs more than some modern smartphones. Yes, I know, it's not on contract... but the prepaid prices are ridiculous, so if you actually use this "basic phone," you're paying OUT THE ASS.
Apple also participated in the design of the initial ARM processors. That seems to be going pretty well. (Direct descendants of the design are in iPhone).
Nitpick: Acorn, not Apple, solely did the design of the initial ARM1, ARM2, and ARM3. They then spun the ARM CPU (which originally stood for Acorn RISC Machine) off into another company, Advanced RISC Machines, which was a joint venture between themselves (40%,) VLSI (who did most manufacturing of ARM CPUs and chipsets at that point - 40%,) and Apple (20%,) as Apple had expressed interest in using the chip, but didn't want to use a competitor's chip (Acorn directly competed with Apple in the personal computer market, especially in schools.)
Only the ARM6 (there was no ARM4 or ARM5) and newer had any Apple involvement, and I doubt anything newer than the DEC StrongARM had much of any Apple influence. (The ARM6, ARM7, and StrongARM were all used in the Newton.)
And, the ARM6 and ARM7 are essentially tweaked versions of the ARM3 with 32-bit addressing (as opposed to 26-bit on the previous ARMs,) and more cache and a slightly faster clock in the case of the ARM7. As for the StrongARM, it wasn't even designed by ARM, it was designed by Digital, to meet the ARMv4 ISA.
Slashdot Mirror
Eh, turning a cam position sensor works nicely, too. That's how you adjust the ignition timing on my car.
Well, I can say for a fact that even if such authentication is in place, Sprint's network doesn't care.
And I've even got an ESN device cloned to a MEID device's pESN, so this one should be even easier to detect. (Although, I am careful to never have both phones powered on at the same time.)
(Just in case this is needed... both phones are legally owned by me, and this is not being used to steal service or intercept calls or text messages. I suspect that there may be more checks put in place if someone complains about calls being made that they never made. And, I don't know how the system responds to multiple phones with the same MEID/ESN/pESN on the network at once, and don't care to find out. The reason why I have this cloned is because I have an old pre-E911 device that cannot legally be activated on any network due to FCC mandate, and cloning is the only way to use it. If it were E911 compliant, I could just MEID/ESN swap on Sprint's website and be done with it, when I want to use it. (Although, it is nice to have a backup phone that I don't have to call Sprint or have internet access to use.))
Knowing the general gist of how cellular protocols work, I don't think there is anything they're not telling us. It's just that most phones don't have reprogrammable IMEIs, for very obvious reasons.
Although, I didn't think GSM phones even authenticated via the IMEI normally, just via the info on the SIM, so cloning the SIM would be enough. Guess I was wrong.
CDMA phones do authenticate via the MEID or ESN (or pESN, an encoded form of the MEID, for backwards compatibility with equipment that can't handle MEIDs,) meaning such an attack would be VERY effective on CDMA. And, a lot of older CDMA equipment has the ESN such that it's not too hard to reprogram with the right software.
Or, to do it perfectly, clean-room it. Have one team create an internal ODF spec based on the OpenOffice source. Give that spec along with the OpenOffice source to the lawyers, have them approve it. Give the spec to your Office devs.
But, that assumes that they WANT compatibility.
What about Korea? Also, quite a few "European" and "Asian" cars are built right here in the US by non-union labor.
And, the American automotive industry didn't have to try to convince people here that they "needed" to drive a tank to work - people were all too willing to buy tanks, so they reacted by building more tanks. Which happened to be high profit margin.
Granted, they should've put more funds into engineering efficient cars, to plan for the contingency of tanks no longer making sense.
What happened was not that unions failed to take hold, but rather that unions took hold too well, to the point that they started choking the industries that they really deeply took hold in (automotive manufacturing and public education, mainly.)
Whether that's true or not (I'm leaning towards not, but it's irrelevant to my reply,) the people in question have no fucking clue what Windows, or Mac OS, or Linux is. They may not even know what a computer is. They've got much more immediate needs, and they aren't poor because of Windows.
I do.
It's called F12->Edit Site Preferences->Content->Uncheck Enable plug-ins.
(Actually, I globally disable Java and plug-ins, and then re-enable them on an as-needed basis for trusted sites.)
Because if they just pay off the fine, the media companies get the money.
If they do this, the media companies have to PAY almost the entire judgement in bank fees, and don't get anything.
The Model 100 definitely counts as the first "net"book, IMO.
Onboard hardware to connect to the main method of networking personal computers at the time, low cost, low power, very portable.
Although the Psion Series 7/netBook was rather expensive, especially compared to low-end mainstream laptops of the time.
Patent the business model of barratry of frivolous patents.
But this could screw over amateur radio... a bunch of very desirable spectrum combined with the people actually using it dying off.
The real meaning...
Retry is obvious. It trys again.
Abort tells it to abort the operation - for example, if you're copying files, and there's a disk error, Abort will stop the copy altogether.
Fail tells it to fail just that stage of the operation - for the copying files example, that sector or that file won't copy, but the rest of the copy operation will continue.
And, you missed Ignore, which is a special version of fail - it tells it to use the erroneous data anyway.
But the C64 was discontinued in April 1994. So, if it were that late... new C64 vs. old 8088 PC...
Moore's Law (more like Moore's Observation) refers to transistor count, not clock frequency... and multicore does nothing to slow that down.
What size and resolution is it?
Better yet, look in this PDF for 4:3 models or this one for widescreens, for the part and FRU numbers. Google both. You may be able to even get an upgrade out of this, compare part numbers on the hinges, cables, and inverter.
Nitpick: Hyposexuality means you're the opposite of a nympho - you don't desire sex AT ALL.
I think "hypersexuality" is the word you were going for. :)
Well, the Crusoe did enable x86 to push into the handheld computing market. Although, MIDs and UMPCs haven't exactly taken off, but the Crusoe got the market open for long enough for Intel to bring their entries into the market (the Intel A100 and A110 (underclocked Dothan Pentium Ms,) and later the Atom.)
How about the Scientologist flu?
Although Anonymous probably would rather stuff the box with marblecake or something instead. (And I'd say to stuff it with Xenu or body thetans, but Scienos would agree that that's bad.)
If you had said the Nokia 1100, I might have not said you were insane.
But the Jitterbug? Seriously? For starters, it has a color screen - something that the Slashdot favorite "basic phone" doesn't have at all. And, second, it costs more than some modern smartphones. Yes, I know, it's not on contract... but the prepaid prices are ridiculous, so if you actually use this "basic phone," you're paying OUT THE ASS.
Apple also participated in the design of the initial ARM processors. That seems to be going pretty well. (Direct descendants of the design are in iPhone).
Nitpick: Acorn, not Apple, solely did the design of the initial ARM1, ARM2, and ARM3. They then spun the ARM CPU (which originally stood for Acorn RISC Machine) off into another company, Advanced RISC Machines, which was a joint venture between themselves (40%,) VLSI (who did most manufacturing of ARM CPUs and chipsets at that point - 40%,) and Apple (20%,) as Apple had expressed interest in using the chip, but didn't want to use a competitor's chip (Acorn directly competed with Apple in the personal computer market, especially in schools.)
Only the ARM6 (there was no ARM4 or ARM5) and newer had any Apple involvement, and I doubt anything newer than the DEC StrongARM had much of any Apple influence. (The ARM6, ARM7, and StrongARM were all used in the Newton.)
And, the ARM6 and ARM7 are essentially tweaked versions of the ARM3 with 32-bit addressing (as opposed to 26-bit on the previous ARMs,) and more cache and a slightly faster clock in the case of the ARM7. As for the StrongARM, it wasn't even designed by ARM, it was designed by Digital, to meet the ARMv4 ISA.
Autorun on read-only media is still an infection vector.
(Hell, even if the "read-only media" in question is a pressed CD, not a CD-R. *cough*Sony BMG*cough*)
Well, hanneloreEC already existed - she's a character in Questionable Content.
But, Jeph made the tweet after Randall posted XKCD, I think.
The problem with forking is all the child processes, though.