It sounds like a much more professional attack than previously considered.
Varying speed by itself should have just sent yield to hell. Varying speed properly with the full knowledge of the centrifuge design and construction allows to select resonating frequencies (which each centrifuge has) and keep it at those until it disintegrates. In my "previous life" doing biotech I have seen what happens when a rotor goes off balance at 50000 rpm. The effect is more or less similar to that of a hand grenade in a closed space.
Add to that the fact that a broken uranium enrichment centrifuge will leak UF6 all over the place which is highly toxic and corrosive and you have your perfect sabotage method.
There is one more question to be answered here which puts the final dots over Is and crosses the last Ts. The people who have analysed the source so far in AV companies were malware professionals, not chemists or industrial automation experts. So they left one question open - does it try to determine the frequencies or it knows them already. If it is the latter, this means that the attacker has managed to obtain the exact design of a centrifuge with the actual improvements used by Iran so Iran's nuclear programme is way leakier than we thought and everyone and their dog has that centrifuge design now (with the actual improvements done by Iran after they got it from our "allies" in Pakistan). If it is the former, the same attack can be applied to all kind's of industrial automation equipment and Siemens kit provides enough telemetry to run the attack. That is probably even scarier than the first possibility. Resonance is lovely stuff... Nothing can withstand it for a sufficiently long time.
They cannot and it is the _SAME_ reason why the handsets will continue to be locked down.
The economic model and the expectation towards return on investment by networks is not based on data. It WAS based on pointless crap nobody gives a shit about where data is merely a conduit.
There, FTFY.;-)
Almost spot on - Needed just one minor correction. They now have realised that. Looking at OpeNet's DPI charging software is an open admission of that as well as that IMS has failed. Now they want to see what you REALLY use and charge you for THAT and they want to apply Walmart-like price management to maximise revenue on this.
It is simply a matter of choice. Most C/Perl people I know chose to have autocompletion off as it is not particularly useful (aside from getting braces right). C++ is on the fence. Most of Ruby developers I have worked with are definitely in the "my IDE types 2/3rds of the code for me" camp.
IMHO if your IDE is typing 2/3rds of what needs to be typed without getting it wrong then there is something fundamentally wrong with the language. The autogenerated verbosity simply does not need to be there in that case.
They cannot and it is the _SAME_ reason why the handsets will continue to be locked down.
The economic model and the expectation towards return on investment by networks is not based on data. It is based on value added services where data is merely a conduit.
By design, 3G and LTE should have had that imlemented via IMS - all applications were supposed to use it for all of the following: requesting resources, authorisation and billing. All the LTE (and 3G from rel 5 onwards) architecture is a mere slave to that idea. However that _FAILED_. No applications materialised and no revenue was coming from there. The data was idle so mobile networks let us have some of it. However unless they find a way to charge us by application and by transaction and make a premium out of it they cannot break even on data alone.
So here come plan B and plan C:
B: Charging based on application by wrapping it around and controlling what it does even if it is not with the resolution of IMS. In order to do that the operators need to ensure that phones are not rooted and we do not get into the habit of doing it.
C: Charing based on DPI as proposed by the likes of OpeNet.
Both are coming and the sole reason for them not to be here now is that the billing part is just not there yet. The moment Mobile Cos get their billing and revenue assurance together to bill for plan B and plan C they will do so and no consumer watchdogs, no protests and no legislation will stop them. If they do not they will not break even on their investment into 3G and LTE.
Coming back to google, google does _NOT_ have that model. It cannot pay for spectrum the same amount of money like let's say Verizon because its model does not provide suffient revenue to break even. The fact that the mobile model has already _FAILED_ massively on IMS and IMS based VAS and will probably struggle very badly on both Plan B (per app charging by operator) and Plan C (DPI) is of little relevance. As long as the mobile companies believe that they can have ROI this way they can and will outinvest the likes of Google which have more conservative revenue models.
As per this logic antivirus preventing a virus accessing a command and control network is illegal provided that the network "owner" has correctly formulated its copyright clauses.
As per this logic virus, scareware, spyware, etc all can fall under DMCA besides the existing legislation on unauthorised access and hacking.
That is some real stretching of the law way beyond what it was originally intended for.
MPEG LA theoretically already dealt with it and Alcatel/Lucent has formally agreed to surrender all patents to them.
I am surprised that the lawsuit regarding these patents has been filed. In fact, I suspect that a "contempt of court" ICBM is already somewhere around the highest point of its trajectory and is dispensing suitable size warheads.
Even if it did not, such hiding of patents while participating in standard bodies is as per US law an antitrust matter. There is a significant body of precedent and most of it is not in favour of the companies which hid patents while participating in a standard body.
The point is to give a pink slip to the (usually senior) qualified nurse or junior radiographer who are sitting at the manual controls now and doing exactly the same function on surgeon request.
C'est la vie. Such are the inevitable results of technological progress...
Not necessarily. Multiple injection steam pusher is a concept old as the world. Most submarine launchers are like that - as the missile goes up more nozzles come into play on the sides giving it a good enough kick to clear the submarine and the water above it without breaking it in the process.
The article misses the biggest advantage of electric vs steam. Electric has a much lower chance of failures in sub-zero temperatures. Steam is a nasty business at -5 or less. It condenses and freezes at all the inevitable leaks along the catapult pusher path. A couple of launches and the pusher is bound to get stuck damaging the aircraft in the process.
IMHO, A ship with an electric catapult (or a ramp) has "Arctic/Antarctic war" stickered all over it. On the positive side this means that we are done with the Gulf and its surroundings. On the negative side this is one place which has seen very little war (except the North Atlantic portion of the Arctic in 1941-44).
Every commit needs to be signed off by at least several more people as far as I know and a lot of commits to key parts need to be signed off by Mr Ego himself till this day.
Obfuscated? Shoddy? Forget that.
The same is the story with all BSDs. They can be used as a textbook on how to write code and in a lot of places you do not even need the (otherwise excellent) documentation to determine what is going on. It is just readable (TM).
Having it right in your face in the canteen, on public transport and everywhere around definitely isn't opt-in.
In the days when I was standing in for IT manager in my previous company I had a fantastic conversation with our new HR manager which tried to make our company look the same as her previous job at a telecom operator. So she insisted that I put netnanny software, filters, censorware, limit staff access to the internet, account how much time they browse and so on. I told her that I have _NO_ objection, but she _WILL_ prohibit download from the newsagent first and make any appearance of Sun, Daily Express and other similar material on company premises a sackable offence. I also told her that if she has any objections I am happy to discuss it with the CEO in her presense (I had roughly the same conversation with the CEO 2 years prior to that).
You can take your guesses how it went from there onwards...
The problem is elsewhere. Admins upon security advice upload settings which make the device unusable. In that case "reporting compliance" while it is not from the user viewpoint is actually a useful feature.
Example - I have a Nokia E71. I was seriously stupid at some point to configure my company exchange server on it. As a result it started autolocking itself in 2 mins requiring a security code. So far so good, however it autolocked and put screensaver on in applications which _MUST_ run in foreground - GPS navigation and the media player. It also autolocked itself when docked on a car craddle, etc.
After a couple of near misses on the motorway trying to get myself from A-Z or trying to dig out the name someone from contacts I tried to turn it off. Guess what, settings uploaded via these APIs _CANNOT_ be turned off. Even if you wipe out the mail for exchange application, disconnect, etc the settings are either not allowed to be changed any more or come back after a change. At the end I had to factory reset the phone and reset the settings partially from backup to recover the phone to a useable state.
Thankfully I do not have to read my company mail on my phone for a living. If I had to, I would have paid for one of those HTCs without giving it a second thought.
Similarly, I am not surprised about Apple starting to take away powers away from the security software (and the people who use it). Apple's key selling point is user experience. The way some corporate security people use these APIs sends the user experience into "Mordok, denier of information services" territory. Knowing Apple, they are guaranteed to do something about it and in the land of "i" noone will hear the security people scream.
That one was supposedly a defect. Though frankly, in a hindsight, I would not be so sure about it.
Nvidia Quadro NVS290 temperature with NV or with no NVidia drivers loaded - >85C Nvidia Quadro NVS290 temperature with Nvidia binary driver at what used to be default (top performance): >85C Nvidia Quadro NVS290 temperature with Nvidia binary driver set to dynamic clock management - 65C
Sooner or later you pay for the 20C. I do not know the default windows settings nowdays, but I would not be surprised that the driver used to default to the higher performance ones in the older versions. In any case, that is a video card for which I would not consider running it with the open source driver until it develops at least some power management.
All of it is simply in the linux-firmware-nonfree package now.
Typing this on a Lenny Mac mini G4 with a backported kernel package and with the radeon happily loading its non-free firmware out of the similarly backported non-free firmware package. Ditto for my G4 Powerbook (TiBook), ditto for my spare laptop which is a HP NC4000 in need for a non-free wireless card driver, firmware (non-free) for the onboard radeon and so on.
The only missing bit last time I checked was however something which is quite important - the nvidia packages. By the way the NV drviver is absolutely not an answer here and not for performance reasons. NV does not have working power management. On half of the hardware currently shipping out there it is a sure way to fry your card. It may not be fried immediately. It may take months or even a year or two for it to die, but die it will and it will die prematurely. That has been actually been the case for 5+ years now.
So unless Debian wants to take the responsibility for something that can actually damage people PCs they will have to swallow the bitter pill and find a way to ship nvidia drivers (and have them properly configured powerwise which by the way no Linux distro does at present). It is not that difficult: http://foswiki.sigsegv.cx/bin/view/Net/LinuxNvidia
Besides that it is also a "trivial geometry" case. If you assume the collector constant the more obtuse the angle of reflection requires a bigger mirror. If the receiver is low, you end up with an obtuse angle out of necessity. The higher it is, the easier to obtain that magic 90 degrees that minimises the mirror size and from there cost and everything else.
Bulgarian (transliterated into latin alphabet because Slashdot eats non-latin characters):
Tap: 1. blunt; 2. stupid, thick person (form of insult) Tapanar: 1. Very stupid person
You add "is" and make it sound like greek.
Macedonian is definitely the same. It is just a dialect of Bulgarian, regardless of what Macedonian nationalists proclaim. I am not fluent in Serbian, but IIRC tap is tap in all balkan languages.
He may. Especially if you consider that "Tapanaris" means more or less Village Idiot in two languages spoken on the north side of the greek border.
So I strongly suspect that he has very little in common with Anonymous. A case of mixing "mistaken identity" and "cruel "Balkan neigbourly relations" joke.
Especially considering the fact that Tapanaris means more or less "Thick as a Brick" in more than one language in countries neighbouring Greece to the north.
This smacks of a rather unintentional Bulgarian or Serbian practical joke. Whoever did it did not expect that there may be a real person whose name in Bulgarian or Serbian translates more or less as "Alex The Village Idiot". The most hilarious case of mistaken identity I have heard of for a long time (for everyone but the poor greek).
In that case at least one of the commits actually reduces such leaks by removing a couple of locks and allowing task switches there which will throw off this type of data collection.
I did not look at all of them. The first one however from this perspective looked like an improvement, not the opposite (as expected).
Check GCC docs - there is a number of systems where the stage2-3 test is skipped because for whatever reason their asm generates functionally identical, but binary different object files every time.
Example: IIRC One of all of the ways of using Alpha (it can be booted into both little and big endian so it has more than one distinct arch in gcc) was one of these, there are probably a few others.
I live in the UK and with my phone provider (VOIP one) it costs me about the same to call USA or German or any EU number including a UK fixed one. In fact it costs me way more to call a UK mobile than to call a USA fixed number.
That is exactly the problem here. The old concepts of usefulness, applicability and level of impact by "volunteer", "volunteer from abroad" and the like will have to be reassessed by everyone who does security (and not just information variety) for a living.
There are some pertinent questions to be asked here of International Law vs Universal Jurisdiction and the like because in the current setting there are very few options to deal with all this. It will be very very very interesting how this pans out at the end.
This is news to anyone who gets the first iteration of a new 3GPPproduct?
Corrected this for ya.
It is not entirely unexpected when standartisation madness runs supreme. FFS, the world has long become Ethernet based. It takes less effort to originate IP from the terminal and NAT or route IPv6 than to translate to PPP and/or something similarly obsolete and Layer 2 in something that pretends to be a "modem". WTF is a "modem" and why it is a "modem"
If the "modem" is actually doing IP what is it running on is utterly irrelevant. It also makes the entire hand-over malarkey similarly irrelevant because in that case you can the mobile IPv6 stack as used in LTE into the BLOODY DONGLE so it simply continues onto 3G as an "unlicensed mobile access" instead of true handover. In fact it can jump to WiFi, WiMax, RFC1149 pigeons as needed. As there is _NO_ true handover on the network side and network does virtually bugger all it takes seconds, not minutes. Similarly, the network can use custom APNs for 3G and GPRS for these and turn off most of the mobility support on these as it is now the _TERMINAL_ doing it.
Most importantly - implementing all of this in the dongle takes _LESS_ resource than implementing all the fine points of 3G handover (especially the soft handover part).
Sigh... Higher brain functions and 3GPP architecture clearly do not mix well... It is a classic example of Braindead Architecture (TM)...
Slashdot Mirror
Not really.
It sounds like a much more professional attack than previously considered.
Varying speed by itself should have just sent yield to hell. Varying speed properly with the full knowledge of the centrifuge design and construction allows to select resonating frequencies (which each centrifuge has) and keep it at those until it disintegrates. In my "previous life" doing biotech I have seen what happens when a rotor goes off balance at 50000 rpm. The effect is more or less similar to that of a hand grenade in a closed space.
Add to that the fact that a broken uranium enrichment centrifuge will leak UF6 all over the place which is highly toxic and corrosive and you have your perfect sabotage method.
There is one more question to be answered here which puts the final dots over Is and crosses the last Ts. The people who have analysed the source so far in AV companies were malware professionals, not chemists or industrial automation experts. So they left one question open - does it try to determine the frequencies or it knows them already. If it is the latter, this means that the attacker has managed to obtain the exact design of a centrifuge with the actual improvements used by Iran so Iran's nuclear programme is way leakier than we thought and everyone and their dog has that centrifuge design now (with the actual improvements done by Iran after they got it from our "allies" in Pakistan). If it is the former, the same attack can be applied to all kind's of industrial automation equipment and Siemens kit provides enough telemetry to run the attack. That is probably even scarier than the first possibility. Resonance is lovely stuff... Nothing can withstand it for a sufficiently long time.
They cannot and it is the _SAME_ reason why the handsets will continue to be locked down.
The economic model and the expectation towards return on investment by networks is not based on data. It WAS based on pointless crap nobody gives a shit about where data is merely a conduit.
There, FTFY. ;-)
Almost spot on - Needed just one minor correction. They now have realised that. Looking at OpeNet's DPI charging software is an open admission of that as well as that IMS has failed. Now they want to see what you REALLY use and charge you for THAT and they want to apply Walmart-like price management to maximise revenue on this.
You can have that in any language.
It is simply a matter of choice. Most C/Perl people I know chose to have autocompletion off as it is not particularly useful (aside from getting braces right). C++ is on the fence. Most of Ruby developers I have worked with are definitely in the "my IDE types 2/3rds of the code for me" camp.
IMHO if your IDE is typing 2/3rds of what needs to be typed without getting it wrong then there is something fundamentally wrong with the language. The autogenerated verbosity simply does not need to be there in that case.
They cannot and it is the _SAME_ reason why the handsets will continue to be locked down.
The economic model and the expectation towards return on investment by networks is not based on data. It is based on value added services where data is merely a conduit.
By design, 3G and LTE should have had that imlemented via IMS - all applications were supposed to use it for all of the following: requesting resources, authorisation and billing. All the LTE (and 3G from rel 5 onwards) architecture is a mere slave to that idea. However that _FAILED_. No applications materialised and no revenue was coming from there. The data was idle so mobile networks let us have some of it. However unless they find a way to charge us by application and by transaction and make a premium out of it they cannot break even on data alone.
So here come plan B and plan C:
B: Charging based on application by wrapping it around and controlling what it does even if it is not with the resolution of IMS. In order to do that the operators need to ensure that phones are not rooted and we do not get into the habit of doing it.
C: Charing based on DPI as proposed by the likes of OpeNet.
Both are coming and the sole reason for them not to be here now is that the billing part is just not there yet. The moment Mobile Cos get their billing and revenue assurance together to bill for plan B and plan C they will do so and no consumer watchdogs, no protests and no legislation will stop them. If they do not they will not break even on their investment into 3G and LTE.
Coming back to google, google does _NOT_ have that model. It cannot pay for spectrum the same amount of money like let's say Verizon because its model does not provide suffient revenue to break even. The fact that the mobile model has already _FAILED_ massively on IMS and IMS based VAS and will probably struggle very badly on both Plan B (per app charging by operator) and Plan C (DPI) is of little relevance. As long as the mobile companies believe that they can have ROI this way they can and will outinvest the likes of Google which have more conservative revenue models.
My exact thought.
As per this logic antivirus preventing a virus accessing a command and control network is illegal provided that the network "owner" has correctly formulated its copyright clauses.
As per this logic virus, scareware, spyware, etc all can fall under DMCA besides the existing legislation on unauthorised access and hacking.
That is some real stretching of the law way beyond what it was originally intended for.
Well, Alcatel is still licencing lots of MPEG-LA patents.
Hmm... I wonder how will its bottom line will be affected if MPEG-LA revoked all of them out of the blue... Food for thought you know...
Unfortunately the MPEG-LA is what it is - a standards body. All talk, no teeth.
It is not original either.
Designs like the Domespace have been around for ages. It is a pity they are not used especially in places like Florida where you really need them.
http://www.betanews.com/article/MPEG-LA-wins-major-MPEG2-settlement-from-AlcatelLucent/1269898704
MPEG LA theoretically already dealt with it and Alcatel/Lucent has formally agreed to surrender all patents to them.
I am surprised that the lawsuit regarding these patents has been filed. In fact, I suspect that a "contempt of court" ICBM is already somewhere around the highest point of its trajectory and is dispensing suitable size warheads.
Even if it did not, such hiding of patents while participating in standard bodies is as per US law an antitrust matter. There is a significant body of precedent and most of it is not in favour of the companies which hid patents while participating in a standard body.
Simultaneous answer from Princess Apple and Sir Google: No Donkey, we are not.
Kind'a
The point is to give a pink slip to the (usually senior) qualified nurse or junior radiographer who are sitting at the manual controls now and doing exactly the same function on surgeon request.
C'est la vie. Such are the inevitable results of technological progress...
Not necessarily. Multiple injection steam pusher is a concept old as the world. Most submarine launchers are like that - as the missile goes up more nozzles come into play on the sides giving it a good enough kick to clear the submarine and the water above it without breaking it in the process.
The article misses the biggest advantage of electric vs steam. Electric has a much lower chance of failures in sub-zero temperatures. Steam is a nasty business at -5 or less. It condenses and freezes at all the inevitable leaks along the catapult pusher path. A couple of launches and the pusher is bound to get stuck damaging the aircraft in the process.
IMHO, A ship with an electric catapult (or a ramp) has "Arctic/Antarctic war" stickered all over it. On the positive side this means that we are done with the Gulf and its surroundings. On the negative side this is one place which has seen very little war (except the North Atlantic portion of the Arctic in 1941-44).
Every commit needs to be signed off by at least several more people as far as I know and a lot of commits to key parts need to be signed off by Mr Ego himself till this day.
Obfuscated? Shoddy? Forget that.
The same is the story with all BSDs. They can be used as a textbook on how to write code and in a lot of places you do not even need the (otherwise excellent) documentation to determine what is going on. It is just readable (TM).
This is Slashdot, remember?
What exactly do you think will be the problem if a slashdotter will get playful with his computer?
Having it right in your face in the canteen, on public transport and everywhere around definitely isn't opt-in.
In the days when I was standing in for IT manager in my previous company I had a fantastic conversation with our new HR manager which tried to make our company look the same as her previous job at a telecom operator. So she insisted that I put netnanny software, filters, censorware, limit staff access to the internet, account how much time they browse and so on. I told her that I have _NO_ objection, but she _WILL_ prohibit download from the newsagent first and make any appearance of Sun, Daily Express and other similar material on company premises a sackable offence. I also told her that if she has any objections I am happy to discuss it with the CEO in her presense (I had roughly the same conversation with the CEO 2 years prior to that).
You can take your guesses how it went from there onwards...
That is the case anyway. At least to some extent.
The problem is elsewhere. Admins upon security advice upload settings which make the device unusable. In that case "reporting compliance" while it is not from the user viewpoint is actually a useful feature.
Example - I have a Nokia E71. I was seriously stupid at some point to configure my company exchange server on it. As a result it started autolocking itself in 2 mins requiring a security code. So far so good, however it autolocked and put screensaver on in applications which _MUST_ run in foreground - GPS navigation and the media player. It also autolocked itself when docked on a car craddle, etc.
After a couple of near misses on the motorway trying to get myself from A-Z or trying to dig out the name someone from contacts I tried to turn it off. Guess what, settings uploaded via these APIs _CANNOT_ be turned off. Even if you wipe out the mail for exchange application, disconnect, etc the settings are either not allowed to be changed any more or come back after a change. At the end I had to factory reset the phone and reset the settings partially from backup to recover the phone to a useable state.
Thankfully I do not have to read my company mail on my phone for a living. If I had to, I would have paid for one of those HTCs without giving it a second thought.
Similarly, I am not surprised about Apple starting to take away powers away from the security software (and the people who use it). Apple's key selling point is user experience. The way some corporate security people use these APIs sends the user experience into "Mordok, denier of information services" territory. Knowing Apple, they are guaranteed to do something about it and in the land of "i" noone will hear the security people scream.
That one was supposedly a defect. Though frankly, in a hindsight, I would not be so sure about it.
Nvidia Quadro NVS290 temperature with NV or with no NVidia drivers loaded - >85C
Nvidia Quadro NVS290 temperature with Nvidia binary driver at what used to be default (top performance): >85C
Nvidia Quadro NVS290 temperature with Nvidia binary driver set to dynamic clock management - 65C
Sooner or later you pay for the 20C. I do not know the default windows settings nowdays, but I would not be surprised that the driver used to default to the higher performance ones in the older versions. In any case, that is a video card for which I would not consider running it with the open source driver until it develops at least some power management.
Not really.
All of it is simply in the linux-firmware-nonfree package now.
Typing this on a Lenny Mac mini G4 with a backported kernel package and with the radeon happily loading its non-free firmware out of the similarly backported non-free firmware package. Ditto for my G4 Powerbook (TiBook), ditto for my spare laptop which is a HP NC4000 in need for a non-free wireless card driver, firmware (non-free) for the onboard radeon and so on.
The only missing bit last time I checked was however something which is quite important - the nvidia packages. By the way the NV drviver is absolutely not an answer here and not for performance reasons. NV does not have working power management. On half of the hardware currently shipping out there it is a sure way to fry your card. It may not be fried immediately. It may take months or even a year or two for it to die, but die it will and it will die prematurely. That has been actually been the case for 5+ years now.
So unless Debian wants to take the responsibility for something that can actually damage people PCs they will have to swallow the bitter pill and find a way to ship nvidia drivers (and have them properly configured powerwise which by the way no Linux distro does at present). It is not that difficult: http://foswiki.sigsegv.cx/bin/view/Net/LinuxNvidia
Besides that it is also a "trivial geometry" case. If you assume the collector constant the more obtuse the angle of reflection requires a bigger mirror. If the receiver is low, you end up with an obtuse angle out of necessity. The higher it is, the easier to obtain that magic 90 degrees that minimises the mirror size and from there cost and everything else.
Bulgarian (transliterated into latin alphabet because Slashdot eats non-latin characters):
Tap: 1. blunt; 2. stupid, thick person (form of insult)
Tapanar: 1. Very stupid person
You add "is" and make it sound like greek.
Macedonian is definitely the same. It is just a dialect of Bulgarian, regardless of what Macedonian nationalists proclaim. I am not fluent in Serbian, but IIRC tap is tap in all balkan languages.
He may. Especially if you consider that "Tapanaris" means more or less Village Idiot in two languages spoken on the north side of the greek border.
So I strongly suspect that he has very little in common with Anonymous. A case of mixing "mistaken identity" and "cruel "Balkan neigbourly relations" joke.
Especially considering the fact that Tapanaris means more or less "Thick as a Brick" in more than one language in countries neighbouring Greece to the north.
This smacks of a rather unintentional Bulgarian or Serbian practical joke. Whoever did it did not expect that there may be a real person whose name in Bulgarian or Serbian translates more or less as "Alex The Village Idiot". The most hilarious case of mistaken identity I have heard of for a long time (for everyone but the poor greek).
In that case at least one of the commits actually reduces such leaks by removing a couple of locks and allowing task switches there which will throw off this type of data collection.
I did not look at all of them. The first one however from this perspective looked like an improvement, not the opposite (as expected).
Not on every system.
Check GCC docs - there is a number of systems where the stage2-3 test is skipped because for whatever reason their asm generates functionally identical, but binary different object files every time.
Example: IIRC One of all of the ways of using Alpha (it can be booted into both little and big endian so it has more than one distinct arch in gcc) was one of these, there are probably a few others.
Really? Who told you so?
I live in the UK and with my phone provider (VOIP one) it costs me about the same to call USA or German or any EU number including a UK fixed one. In fact it costs me way more to call a UK mobile than to call a USA fixed number.
That is exactly the problem here. The old concepts of usefulness, applicability and level of impact by "volunteer", "volunteer from abroad" and the like will have to be reassessed by everyone who does security (and not just information variety) for a living.
There are some pertinent questions to be asked here of International Law vs Universal Jurisdiction and the like because in the current setting there are very few options to deal with all this. It will be very very very interesting how this pans out at the end.
This is news to anyone who gets the first iteration of a new 3GPPproduct?
Corrected this for ya.
It is not entirely unexpected when standartisation madness runs supreme. FFS, the world has long become Ethernet based. It takes less effort to originate IP from the terminal and NAT or route IPv6 than to translate to PPP and/or something similarly obsolete and Layer 2 in something that pretends to be a "modem". WTF is a "modem" and why it is a "modem"
If the "modem" is actually doing IP what is it running on is utterly irrelevant. It also makes the entire hand-over malarkey similarly irrelevant because in that case you can the mobile IPv6 stack as used in LTE into the BLOODY DONGLE so it simply continues onto 3G as an "unlicensed mobile access" instead of true handover. In fact it can jump to WiFi, WiMax, RFC1149 pigeons as needed. As there is _NO_ true handover on the network side and network does virtually bugger all it takes seconds, not minutes. Similarly, the network can use custom APNs for 3G and GPRS for these and turn off most of the mobility support on these as it is now the _TERMINAL_ doing it.
Most importantly - implementing all of this in the dongle takes _LESS_ resource than implementing all the fine points of 3G handover (especially the soft handover part).
Sigh... Higher brain functions and 3GPP architecture clearly do not mix well... It is a classic example of Braindead Architecture (TM)...