In "almost everyone that cares about online transaction authentication" the central party is fully trusted and transactions are not anonymous. In online voting the central party is only partially trusted, all transactions must be anonymous, and each voter can vote at most once. This, not user authentication, is what makes the problem hard.
Online voting requires satisfying a set of unsatisfiable constraints. If you think its trivial you either aren't seeing the whole problem or haven't thought about it enough.
The original idea isn't bad. Corporations are supposed to exist to shield investors in a company from liability created by its officers. In other words, if I give you money to create car batteries and you make batteries that explode and kill people. You should be liable for the damages but I shouldn't. We have, unfortunately, accepted a much broader idea of what this liability shield is all about.
It isn't WebResource.axd... its ScriptResource.axd that has the file download vulnerability.
The purposes of this (mis)feature is to allow the ScriptManager to prevent clients from using stale versions of a script from cache. The problem is that ScriptResource.axd doesn't sanity check what kind of files it is serving up. Furthermore, since this behavior is out in the field it is impossible for MS to know if anyone is using it, so "fixing" it might break some unknown customers' sites in a way that is non trivial to fix. This will obviously piss people off.
I wrote a module that uses a user configurable white list of file types that are permitted for download through the ScriptManager which is more rational behavior IMO. Of course, depending on what MS pushes tomorrow this may or may not still be relevant.
You mean milliseconds... 25 microseconds is less than one sample at 44khz. Somewhere around 100ms is the lower edge of where its "noticeable" in the flow of the conversion.
With UDP the typical loss scenario is dropped packets but with radio single bit errors are more likely. This difference means that FEC strategies for one scenario are not directly applicable to the other.
for UDP in packet FEC data is useless and your error correction scheme needs to be prepared to deal with losing a whole packets worth of data to be useful. For voice this is going to introduce too much latency so instead a typical codec might just try to interpolate the lost data. With radio on the other hand there is value to in packet error correction bits within the stream and in the event of an error you are going to have more data with which to guess what the audio should be like, especially if you know which bits are errored (or possibly errored)
What the exploit actually allows you to do is to read arbitrary files inside of the virtual root directory that the IIS application. Every thing else you see is from a third party CMS (DotNetNuke) and a shitty configuration. No doubt this is bad but its a far cry from remote root.
isn't IBM a big open source contributer and isn't $80B not nearly enough to buy them? They can buy up some projects, but so what? If they maintain them in the spirit of open source nothing changes if they don't then they will be forked or abandoned. In any case I don't think they can change the ecosystem as a whole much.
Actually its really easy to explain. iphone has been out long enough that people who still have them are on at least their second device. People, like me, who were dissatisfied with their first iphone or AT&T's shitty coverage switched to Android (or w/e) while the people who were satisfied bought another one.
So IMO it isn't much of a surprise that most people who still have iphones.
That wasn't really a choice since those one or two accounts had no relationship with burst. They could have suggested that the FBI talk to Blogetery who did have some relationships with those one or two accounts and as far as I can tell we have no information about if they did that or not.
TBQH I would be much more pissed of at my hosting provider if they were altering the content on my site (which is what you are suggesting) than if they just shut me off. But then I also have backups, a (tested) disaster recovery plan, and a warm standby on the other side of the country and could have things back up and running as quickly as DNS propagated the change.
Location has been taken into consideration for ads for a long time (probably since the beginning) using them to alter search results is something different.
to play the devils advocate. The point could be to reduce their costs for new infrastructure going forward, which is a huge line item for all telcos, instead of a quick jump in profitability.
My opinion is based on implementing software around OGG and I stand by it. That the original developer says something different 10 years after the fact is interesting but not definitive.
Vorbis is better than MP3 and Ogg was more or less designed to contain Vorbis so it does it isn't surprising that it works well together where it fails is trying to use it as general purpose container format.
Slashdot Mirror
Either that or Photoshop him out and replace him with a different astronaut, assuming they haven't already done this.
In "almost everyone that cares about online transaction authentication" the central party is fully trusted and transactions are not anonymous. In online voting the central party is only partially trusted, all transactions must be anonymous, and each voter can vote at most once. This, not user authentication, is what makes the problem hard.
Online voting requires satisfying a set of unsatisfiable constraints. If you think its trivial you either aren't seeing the whole problem or haven't thought about it enough.
FDR or the West Side Highway if you are insane or a Cab Driver.
The original idea isn't bad. Corporations are supposed to exist to shield investors in a company from liability created by its officers. In other words, if I give you money to create car batteries and you make batteries that explode and kill people. You should be liable for the damages but I shouldn't. We have, unfortunately, accepted a much broader idea of what this liability shield is all about.
It isn't WebResource.axd... its ScriptResource.axd that has the file download vulnerability.
The purposes of this (mis)feature is to allow the ScriptManager to prevent clients from using stale versions of a script from cache. The problem is that ScriptResource.axd doesn't sanity check what kind of files it is serving up. Furthermore, since this behavior is out in the field it is impossible for MS to know if anyone is using it, so "fixing" it might break some unknown customers' sites in a way that is non trivial to fix. This will obviously piss people off.
I wrote a module that uses a user configurable white list of file types that are permitted for download through the ScriptManager which is more rational behavior IMO. Of course, depending on what MS pushes tomorrow this may or may not still be relevant.
You mean milliseconds... 25 microseconds is less than one sample at 44khz. Somewhere around 100ms is the lower edge of where its "noticeable" in the flow of the conversion.
With UDP the typical loss scenario is dropped packets but with radio single bit errors are more likely. This difference means that FEC strategies for one scenario are not directly applicable to the other.
for UDP in packet FEC data is useless and your error correction scheme needs to be prepared to deal with losing a whole packets worth of data to be useful. For voice this is going to introduce too much latency so instead a typical codec might just try to interpolate the lost data. With radio on the other hand there is value to in packet error correction bits within the stream and in the event of an error you are going to have more data with which to guess what the audio should be like, especially if you know which bits are errored (or possibly errored)
What the exploit actually allows you to do is to read arbitrary files inside of the virtual root directory that the IIS application. Every thing else you see is from a third party CMS (DotNetNuke) and a shitty configuration. No doubt this is bad but its a far cry from remote root.
that ones headed to a stack overflow not a segfault.
Silverlight runs on Windows and Mac. Moonlight runs on Linux... no need to shell out cash for a new OS.
Pretty much everyone who does business with the government at that level rips them off.
isn't IBM a big open source contributer and isn't $80B not nearly enough to buy them? They can buy up some projects, but so what? If they maintain them in the spirit of open source nothing changes if they don't then they will be forked or abandoned. In any case I don't think they can change the ecosystem as a whole much.
Actually its really easy to explain. iphone has been out long enough that people who still have them are on at least their second device. People, like me, who were dissatisfied with their first iphone or AT&T's shitty coverage switched to Android (or w/e) while the people who were satisfied bought another one. So IMO it isn't much of a surprise that most people who still have iphones.
That wasn't really a choice since those one or two accounts had no relationship with burst. They could have suggested that the FBI talk to Blogetery who did have some relationships with those one or two accounts and as far as I can tell we have no information about if they did that or not.
TBQH I would be much more pissed of at my hosting provider if they were altering the content on my site (which is what you are suggesting) than if they just shut me off. But then I also have backups, a (tested) disaster recovery plan, and a warm standby on the other side of the country and could have things back up and running as quickly as DNS propagated the change.
Location has been taken into consideration for ads for a long time (probably since the beginning) using them to alter search results is something different.
Apps written by third parties are apple property? I didn't think we were quite to that stage of the game yet.
I remember seeing it on you can't do that on television back in the day.
The article is pure speculation by someone that doesn't even understand the basics of what it would take to bring something like this to market.
to play the devils advocate. The point could be to reduce their costs for new infrastructure going forward, which is a huge line item for all telcos, instead of a quick jump in profitability.
rubbing alcohol == isopropyl alcohol
denatured alcohol == ethanol + a denaturing agent (e.g. acetone)
Obviously neither should be consumed
I think the problem comes down to being able to flip the state at one end with out breaking entanglement. Which may not be as impossible as it sounds.
My opinion is based on implementing software around OGG and I stand by it. That the original developer says something different 10 years after the fact is interesting but not definitive.
Vorbis is better than MP3 and Ogg was more or less designed to contain Vorbis so it does it isn't surprising that it works well together where it fails is trying to use it as general purpose container format.