Indeed. When I'm abroad, I swap my home SIM in whenever I need to update the call forwarding settings (I often cycle around to different DIDs on different VoIP providers depending on who gets the best connection quality or price forwarding my calls though) and I swap different local SIMs depending on where I am. It's very rare that I would want more than one active on the network at a time, especially since if you're on the network when your forwarding kicks in (as opposed to offline), YOU PAY for it (both the incoming and outgoing parts at intl roaming rates).
Indeed, my first thought was WHY?!
It's already way too easy to drop/lose/damage your SIM cards switching them in and out. The last thing we need is to make them smaller. I'd rather seem them bigger if anything.
In the US we only pay for airtime when we're calling non-mobile numbers (like, in your example, 800 numbers). We also pay for airtime for incoming calls from non-mobile numbers (like, in your example, spammers, but at least we can hang up on them immediately and only get charged for one minute, or send them straight to voicemail before answering).
I think it's many European countries. The nastiest part is the cost of calling *to* a mobile phone. I've never used phone services in Europe, but whenever I call UK mobile numbers from VoIP services, it's about 5 to 10 times as expensive as calling a land line...
I was assuming you wouldn't use any minutes (since mobile-to-mobile is not charged to minutes) and thus you just split the bill evenly down the middle. When I have to call land lines, I do it from a land line (if it's local and I'm at work where I have a land line) or (if I'm at home or somewhere else with network access) via VoIP at about $0.016 USD/min (can be even cheaper if you don't care about quality or don't mind switching providers all the time chasing bargains).
In China and India there are few/no carrier subsidy options, and the quality/lifetime of phones is comparable to (often better, I would argue, since they have more Nokias and less Sony/Erickson, LG, and Samsung crap) the quality of the low-end subsidized phones in the US. I don't buy your argument that quality would go down without subsidies. In fact I think it might go up, since people would realize they're not going to get a new "free" phone in 18 months if they buy one that's poorly made, and thus might actually bother to look at reviews of which ones are well-made.
In sane countries (like India) it's just dirt cheap whether you're calling mobile or land lines. I can usually get by on $5-10 USD for a whole month of prepaid calling in India, and it's billed per-second, not per-minute (Rs 0.01/sec, which is approximately 0.00022 USD per second). As bad as the US system is, I think the European system is the most overpriced and insane phone price structure in the world, with prices up to and sometimes exceeding 10 US cents per minute to make a domestic call!
No, here in the US, nobody pays for minutes anymore unless you call dinosaurs (land line users) or DID numbers. Mobile-to-mobile is completely free on all major carriers. The lowest-minutes plan might as well be unlimited these days. And if you have a 3 or 4 people you trust to open a "family" plan together, it's dirt cheap.
I'm not going to write this thing off yet, but the demos I've seen so far don't seem to match the claims of how "light field photography" is supposed to work. In fact all the demos are pretty much what you'd get if you put a camera on a tripod and took 2 or 3 photos of the same subject with the focus adjusted, and then linear-interpolated between them to make an animation...
This all sounds pretty far-fetched, considering that we're probably at most a decade or two away from making organ transplants completely obsolete (replaced by growing the patient's own replacement organ with their own DNA or slightly modified to correct for the genetic disease that caused the original organ to fail).
It's not kept in ram. It's kept in virtual memory. Which might or might not be present in ram at any given time. Pretty much the same as data on the filesystem, which also might or might not be kept in ram at any given time.
This is a C issue, not an IEEE 754 one; C allows extra precision for intermediate results. If however you put a cast on every intermediate result back to the correct nominal type, and if your compiler respects these casts as required by the C standard (unfortunately, gcc does not...), then results are completely well-defined for arithmetic and non-transcendental functions.
In any case where there's a bug that causes modification to the stack in ways that could affect the return address, in the absence of proof that it cannot happen, you must consider this a full code execution vulnerability.
This is completely wrong. Corrupting the stack pointer is not a "crash bug". It's a code execution vulnerability. If there's a pattern to the corruption that happens and an attacker can control contents elsewhere on the stack, it's likely to turn into arbitrary code execution.
This is not insightful; it's wrong. Floating point on any modern system conforms, or at least is intended and assumed to conform, to IEEE 754. There are exact answers specified for every basic arithmetic operation and non-transcendental functions. Of course there are decimals that have no representation in binary, but 4.0 is not one of them.
The Cheerio analogy is bogus. You don't have to trust that hundreds of people did their jobs. You just have to understand statistics and the infinitesimal probability that your one Cheerio has arsenic in it but that none of the other billions (trillions?) of Cheerios produced in the same manufacturing run and already eaten by other consumers has arsenic in it.
Same thing goes for driving across a bridge. Your information is (1) the fact that it's been safe up until now, and (2) the fact that if there is a sudden catastrophic failure, the probability of it happening at the exact moment you're in the position to be injured or die from it is ridiculously small in comparison to other road hazards like bad drivers.
Am I the first one to notice they chose the goatse man as their mascot for this release? WTF is with that? Are they trying to hurt their credibility even more, or get "street cred" with the skript kiddie crowd? Please...
It's very easy to avoid if you don't use carrier-branded phones. I always buy phones from overseas (usually Nokia in the past, but now...) with no crapware, no carrier lock-in, etc.
This sounds pretty easy actually. First serve the user the malicious file named "pkcs11.txt" or whatever it needs to be, with a binary content-type so it gets saved (presumably in the default download directory) rather than displayed, and then go from there. Am I missing something?
Except in a very small business where the owner can afford to carry and deposit cash personally, handling cash costs a business A LOT MORE than handling credit cards. You can't exactly have your minimum-wage employees carry $20k to the bank every day...
Slashdot Mirror
Indeed. When I'm abroad, I swap my home SIM in whenever I need to update the call forwarding settings (I often cycle around to different DIDs on different VoIP providers depending on who gets the best connection quality or price forwarding my calls though) and I swap different local SIMs depending on where I am. It's very rare that I would want more than one active on the network at a time, especially since if you're on the network when your forwarding kicks in (as opposed to offline), YOU PAY for it (both the incoming and outgoing parts at intl roaming rates).
Indeed, my first thought was WHY?! It's already way too easy to drop/lose/damage your SIM cards switching them in and out. The last thing we need is to make them smaller. I'd rather seem them bigger if anything.
In the US we only pay for airtime when we're calling non-mobile numbers (like, in your example, 800 numbers). We also pay for airtime for incoming calls from non-mobile numbers (like, in your example, spammers, but at least we can hang up on them immediately and only get charged for one minute, or send them straight to voicemail before answering).
I think it's many European countries. The nastiest part is the cost of calling *to* a mobile phone. I've never used phone services in Europe, but whenever I call UK mobile numbers from VoIP services, it's about 5 to 10 times as expensive as calling a land line...
I was assuming you wouldn't use any minutes (since mobile-to-mobile is not charged to minutes) and thus you just split the bill evenly down the middle. When I have to call land lines, I do it from a land line (if it's local and I'm at work where I have a land line) or (if I'm at home or somewhere else with network access) via VoIP at about $0.016 USD/min (can be even cheaper if you don't care about quality or don't mind switching providers all the time chasing bargains).
In China and India there are few/no carrier subsidy options, and the quality/lifetime of phones is comparable to (often better, I would argue, since they have more Nokias and less Sony/Erickson, LG, and Samsung crap) the quality of the low-end subsidized phones in the US. I don't buy your argument that quality would go down without subsidies. In fact I think it might go up, since people would realize they're not going to get a new "free" phone in 18 months if they buy one that's poorly made, and thus might actually bother to look at reviews of which ones are well-made.
In sane countries (like India) it's just dirt cheap whether you're calling mobile or land lines. I can usually get by on $5-10 USD for a whole month of prepaid calling in India, and it's billed per-second, not per-minute (Rs 0.01/sec, which is approximately 0.00022 USD per second). As bad as the US system is, I think the European system is the most overpriced and insane phone price structure in the world, with prices up to and sometimes exceeding 10 US cents per minute to make a domestic call!
No, here in the US, nobody pays for minutes anymore unless you call dinosaurs (land line users) or DID numbers. Mobile-to-mobile is completely free on all major carriers. The lowest-minutes plan might as well be unlimited these days. And if you have a 3 or 4 people you trust to open a "family" plan together, it's dirt cheap.
I'm not going to write this thing off yet, but the demos I've seen so far don't seem to match the claims of how "light field photography" is supposed to work. In fact all the demos are pretty much what you'd get if you put a camera on a tripod and took 2 or 3 photos of the same subject with the focus adjusted, and then linear-interpolated between them to make an animation...
This all sounds pretty far-fetched, considering that we're probably at most a decade or two away from making organ transplants completely obsolete (replaced by growing the patient's own replacement organ with their own DNA or slightly modified to correct for the genetic disease that caused the original organ to fail).
Yes the incest jokes are mildly amusing, but for those of you unaware, "cousin sister" is Indian English for "female cousin".
It's not kept in ram. It's kept in virtual memory. Which might or might not be present in ram at any given time. Pretty much the same as data on the filesystem, which also might or might not be kept in ram at any given time.
This is a C issue, not an IEEE 754 one; C allows extra precision for intermediate results. If however you put a cast on every intermediate result back to the correct nominal type, and if your compiler respects these casts as required by the C standard (unfortunately, gcc does not...), then results are completely well-defined for arithmetic and non-transcendental functions.
In any case where there's a bug that causes modification to the stack in ways that could affect the return address, in the absence of proof that it cannot happen, you must consider this a full code execution vulnerability.
Even cold fusion has climate effects. Any conversion of potential energy to kinetic energy outputs heat.
This is completely wrong. Corrupting the stack pointer is not a "crash bug". It's a code execution vulnerability. If there's a pattern to the corruption that happens and an attacker can control contents elsewhere on the stack, it's likely to turn into arbitrary code execution.
This is not insightful; it's wrong. Floating point on any modern system conforms, or at least is intended and assumed to conform, to IEEE 754. There are exact answers specified for every basic arithmetic operation and non-transcendental functions. Of course there are decimals that have no representation in binary, but 4.0 is not one of them.
Yes, please feel free to do this. Get your dumbass self fired so somebody with a clue can have your job.
The Cheerio analogy is bogus. You don't have to trust that hundreds of people did their jobs. You just have to understand statistics and the infinitesimal probability that your one Cheerio has arsenic in it but that none of the other billions (trillions?) of Cheerios produced in the same manufacturing run and already eaten by other consumers has arsenic in it. Same thing goes for driving across a bridge. Your information is (1) the fact that it's been safe up until now, and (2) the fact that if there is a sudden catastrophic failure, the probability of it happening at the exact moment you're in the position to be injured or die from it is ridiculously small in comparison to other road hazards like bad drivers.
Am I the first one to notice they chose the goatse man as their mascot for this release? WTF is with that? Are they trying to hurt their credibility even more, or get "street cred" with the skript kiddie crowd? Please...
It's very easy to avoid if you don't use carrier-branded phones. I always buy phones from overseas (usually Nokia in the past, but now...) with no crapware, no carrier lock-in, etc.
It's tiny and seems to do exactly what you want. Comes with one year of free service, no idea what the monthly cost is after that.
This sounds pretty easy actually. First serve the user the malicious file named "pkcs11.txt" or whatever it needs to be, with a binary content-type so it gets saved (presumably in the default download directory) rather than displayed, and then go from there. Am I missing something?
Except in a very small business where the owner can afford to carry and deposit cash personally, handling cash costs a business A LOT MORE than handling credit cards. You can't exactly have your minimum-wage employees carry $20k to the bank every day...
s/guanji/tingji/