This is semi-maximum damage and disruption. The users PC's would still work, albeit with no personal data. Given the way SCCM formats and dumps, there is a change of data recovery with any of the post-format recovery tools like EZRecovery, Recuva etc.
Max disruption would be to deploy a DoD-level hard disk wipe utility configured for 20 passes.
This isn't the update server section of System Center (WSUS), it's the machine deployment system (Configuration Manager), and it can quite easily do this if left as-is out of the box with multiple technicians on it. And it can be done accidentally.
Here's the scenario as it likely happened.
Technician finished a master PC install task sequence and tested with one PC. Now he is ready to deploy to his computer lab.
There are two options for failure here. SCCM allows for collections of machines to be built for all purposes (data gathering, deployments etc), so he probably puts a quick group together and gets that step wrong and the collection includes all computers in the AD tree. One of our technicians did this after two years of using SCCM regularly.
Or he goes hunting for an existing collection and ends up selecting the default All Systems collection which includes everything. If there are a lot of collections or his is named too similarly.
After another hundred odd clicks, he hits deploy and SCCM sends a message to the client service on all computers in the selected collection to run the new deployment task sequence. Including the SCCM server because it also has a client and is in All Systems collection or gathered in an incorrectly specified collection.
Each PC then downloads the image, reboots and wipes itself with the image. The server, also in the collection, will do the same at some point.
We've had two near-misses with misconfigured collections and one hit with a different problem* which cannot have happened in this case. SCCM isn't the most intuitive user interface and if you're being pressured by users or trying to get out of the door for the weekend, you can stuff it up easily.
Our solution was to restrict access to the built-in collections and to build collections per computer lab which are presented as read-only to the technicians. And then gave them a day of lectures. It sort of works.
* The other problem was caused by image dumping with Ghost of an image that was sysprepped, but had the SCCM client still installed on the image. Because of that, several dozen PCs had clients with the same client ID, like the Windows GUID, but separate and not cleared by a sysprep. The technician later built a SCCM image and deployed it correctly to one PC in a personal collection. Unfortunately SCCM populated the deployment list based on the client ID of the PC in the list and hit quite a few overnight. Luckily a lot of the machines in the batch were off overnight. I don't think this is the case because it hit the server too and that would have received a new client install during the SCCM installation.
Just had a look at my local online camera shop. None of the Canon home, prosumer or pro-broadcast cameras have FW anymore and only the Sony pro-broadcast cameras have it, not their prosumer or home devices. Sad.
Except according to the government, they are NOT bypassing the law. Transport for London says that Uber is legal, then Uber is legal no matter what the LTDA thinks.
Why not let SpaceX try and find out for themselves. They know their engines and have tested them for reuse long before they started building Grasshopper and the test protocols for Falcon 9.
The Merlins are designed to stop and start, and have done it successfully on the launch pad with the launch aborts experienced during their test flights. And SpaceX probably has a set that they've run on a static test pad for a full flight profile, then dusted them off, checked the bearings and seals and ran them again. And again. And again.
The SSMEs are excessively complex systems that have a much greater thrust than the Merlins. They need a full strip and rebuild because of their complexity.
There was an article a couple of weeks back around the time the pings were supposedly detected where the Malaysian government wanted to start the process of declaring the passengers dead so the compensation process could start and the families threw their toys out of the cot.
The decision to declare the passengers dead is independent of finding the wreckage and can be done without proof of death, although having the passengers show up alive later can be embarrassing and difficult to correct. There is an agreed upon seven year maximum waiting window, but that can be shortened.
Given the number of peers I see on fresh UFC and WWE torrents, 1000 people is probably around 10% of the actual downloaders. Even though he assumed 100% uptake, his numbers work with a 10% uptake which I would happily argue is a fair count of downloaded-instead-of-purchased viewers.
I'll take a bet right now that three to six months from now, Presley or her husband, or both, will be arrested for running a money laundering scheme. I sense an attempt to generate outrage in the public against the DoJ as a defence tactic.
I'm thinking of the days before MAD. By the start of the Korean war, the Soviets had tested one device only. Some might have entered service by the time of the war, but the Americans still had the upper hand with nuclear weapons at that time.
There was arguments to use them, and Truman did go so far as to release them to the theater, but he never dropped them. Nor did Ike when he won the election. There seemed to be a reluctance to use them even before the whole arms race and MAD became what it did.
Now generals and admirals would probably have tossed the things around like fire-crackers, and they definitely had plans for first-strike use, but the civilian bosses are the ones who were reluctant when it came to their use.
After dropping those two bombs, nobody on Earth has ever dropped one since. Think about that for a second. Yes, they have been tested, but never once dropped in anger since the first two. And all nuclear-capable countries between the 50s and the 80s have had was at some point to consider using them. All of them treated them as retaliation weapons, only to be used if they were shot at first.
So let us treat Hiroshima and Nagasaki as the ignorant first use of an unknown technology that it was and accept that the world went through a massive, rapid learning curve and HAVE NOT USED THEM SINCE.
I suspect that would be the case. One good war where you lose because your computer controlled weapons system got zero-dayed and the enemy was launching your own missiles at you via TeamViewer while your mouse refused to respond and I suspect your replacement ships would require you to manually program the coordinates and launch the missile by pulling a piece of string from behind a blast screen.
Yet these same people ignore the parts they don't like (Christians choose to eat pork even though their book tells them not to),
Acts 10 9-16 repeals the unclean animal laws that the Mosaic Law brought in to keep nasty diseases out of the population. Both the prohibition and the repealing are couched in "Orders from God" terms, but are actually based on prevailing understanding of health and hygiene at the time of each event. And which got unfortunately ritualized.
In a primitive civilization, pork and other meats can be severe risks if they don't know how to cook it properly. A lot of early civilizations had pork prohibitions, but as soon as they realized that a long, hot cooking process rendered the meat harmless, they were dropped. Long before the early Roman Empire times, it was common knowledge and only those adhering to the old Mosaic laws kept up the prohibition as tradition.
The repealing was done as a direct instruction from God because that was probably the only way to get the traditionalists to accept the change and was likely initiated as the early Jewish Christians interacted more with the Romans and Greeks and the knowledge that pork and related "unclean" meats were now safe to eat. And that the gentiles who were becoming more and more of the Christian base weren't going to accept archaic traditions.
If he is retried, he can bring into evidence footnote 5 on page 12 of the judgement where the judges advanced the opinion that he was innocent of the accessing without authorization or in excess of authorization charge because there was no password or code barrier and the program accessed a publicly facing interface and retrieved information that AT&T unintentionally published. It reads that even if they found the venue as correct, they would have vacated the guilty verdict because of that.
Actually, it is a paradox. He can't fix stuff if it is never accepted.
The fix needed is in the systemd code, not the kernel. He can fix it, in less than a minute of editing probably two constants. (from "debug" and "quiet" to "systemd.debug" and "systemd.quiet")
The problem is systemd is a johnny-come-lately and is violating the standard way of doing things, even if the standard way isn't the most optimal. Think of it like a court of law, no court is going to accept a junior lawyer changing terminology that has been in use for centuries just because the lawyer has read a thesaurus. The impact is just too large.
To take it further, apparently all but two parameters (debug and quiet) that systemd recognizes are prefixed by systemd.xxxxxx, so they know how to work within the kernel standard.
The kernel has for a long time had a protocol of parameter naming. Direct kernel parameters are plain, module-specific parameters have mod.xxxx format and that was designed to pass driver-specific parameters in. SystemD, being a child process and not even part of the kernel should respect the existing protocol and ignore any parameters not passed without a leading systemd.
The balaclava isn't for you to wear to hide yourself, it's to pull over the head of the glasshole to cover the camera up. And get them in trouble with the fuzz.
The problem with producing a car that can only do the highway speed limit, is that it can then still exceed the town limits which is where you have the greater risk of hitting people and other cars.
Imagine an area on the plane where the screaming kids will sit, able to hear what's going on, but not being heard. Or to separate first class from cattle class even better than it already is. Not the most necessary of solutions, but might gain them some extra pax.
They are documented in the regulations linked by the GP and there are clearly documented compliance and appeals processes in there as well. It's a hell of a read though.
Slashdot Mirror
This is semi-maximum damage and disruption. The users PC's would still work, albeit with no personal data. Given the way SCCM formats and dumps, there is a change of data recovery with any of the post-format recovery tools like EZRecovery, Recuva etc.
Max disruption would be to deploy a DoD-level hard disk wipe utility configured for 20 passes.
This isn't the update server section of System Center (WSUS), it's the machine deployment system (Configuration Manager), and it can quite easily do this if left as-is out of the box with multiple technicians on it. And it can be done accidentally.
Here's the scenario as it likely happened.
We've had two near-misses with misconfigured collections and one hit with a different problem* which cannot have happened in this case. SCCM isn't the most intuitive user interface and if you're being pressured by users or trying to get out of the door for the weekend, you can stuff it up easily.
Our solution was to restrict access to the built-in collections and to build collections per computer lab which are presented as read-only to the technicians. And then gave them a day of lectures. It sort of works.
* The other problem was caused by image dumping with Ghost of an image that was sysprepped, but had the SCCM client still installed on the image. Because of that, several dozen PCs had clients with the same client ID, like the Windows GUID, but separate and not cleared by a sysprep. The technician later built a SCCM image and deployed it correctly to one PC in a personal collection. Unfortunately SCCM populated the deployment list based on the client ID of the PC in the list and hit quite a few overnight. Luckily a lot of the machines in the batch were off overnight. I don't think this is the case because it hit the server too and that would have received a new client install during the SCCM installation.
Just had a look at my local online camera shop. None of the Canon home, prosumer or pro-broadcast cameras have FW anymore and only the Sony pro-broadcast cameras have it, not their prosumer or home devices. Sad.
Except according to the government, they are NOT bypassing the law. Transport for London says that Uber is legal, then Uber is legal no matter what the LTDA thinks.
Why not let SpaceX try and find out for themselves. They know their engines and have tested them for reuse long before they started building Grasshopper and the test protocols for Falcon 9.
The Merlins are designed to stop and start, and have done it successfully on the launch pad with the launch aborts experienced during their test flights. And SpaceX probably has a set that they've run on a static test pad for a full flight profile, then dusted them off, checked the bearings and seals and ran them again. And again. And again.
The SSMEs are excessively complex systems that have a much greater thrust than the Merlins. They need a full strip and rebuild because of their complexity.
More likely PRC will be Hong Kong in 30 years.
There was an article a couple of weeks back around the time the pings were supposedly detected where the Malaysian government wanted to start the process of declaring the passengers dead so the compensation process could start and the families threw their toys out of the cot.
The decision to declare the passengers dead is independent of finding the wreckage and can be done without proof of death, although having the passengers show up alive later can be embarrassing and difficult to correct. There is an agreed upon seven year maximum waiting window, but that can be shortened.
Wreckage or not, compensation will be paid.
Word 2013 does open and save ODT files.
Given the number of peers I see on fresh UFC and WWE torrents, 1000 people is probably around 10% of the actual downloaders. Even though he assumed 100% uptake, his numbers work with a 10% uptake which I would happily argue is a fair count of downloaded-instead-of-purchased viewers.
I'll take a bet right now that three to six months from now, Presley or her husband, or both, will be arrested for running a money laundering scheme. I sense an attempt to generate outrage in the public against the DoJ as a defence tactic.
I'm thinking of the days before MAD. By the start of the Korean war, the Soviets had tested one device only. Some might have entered service by the time of the war, but the Americans still had the upper hand with nuclear weapons at that time.
There was arguments to use them, and Truman did go so far as to release them to the theater, but he never dropped them. Nor did Ike when he won the election. There seemed to be a reluctance to use them even before the whole arms race and MAD became what it did.
Now generals and admirals would probably have tossed the things around like fire-crackers, and they definitely had plans for first-strike use, but the civilian bosses are the ones who were reluctant when it came to their use.
I add the following for your consideration.
After dropping those two bombs, nobody on Earth has ever dropped one since. Think about that for a second. Yes, they have been tested, but never once dropped in anger since the first two. And all nuclear-capable countries between the 50s and the 80s have had was at some point to consider using them. All of them treated them as retaliation weapons, only to be used if they were shot at first.
So let us treat Hiroshima and Nagasaki as the ignorant first use of an unknown technology that it was and accept that the world went through a massive, rapid learning curve and HAVE NOT USED THEM SINCE.
I suspect that would be the case. One good war where you lose because your computer controlled weapons system got zero-dayed and the enemy was launching your own missiles at you via TeamViewer while your mouse refused to respond and I suspect your replacement ships would require you to manually program the coordinates and launch the missile by pulling a piece of string from behind a blast screen.
Yet these same people ignore the parts they don't like (Christians choose to eat pork even though their book tells them not to),
Acts 10 9-16 repeals the unclean animal laws that the Mosaic Law brought in to keep nasty diseases out of the population. Both the prohibition and the repealing are couched in "Orders from God" terms, but are actually based on prevailing understanding of health and hygiene at the time of each event. And which got unfortunately ritualized.
In a primitive civilization, pork and other meats can be severe risks if they don't know how to cook it properly. A lot of early civilizations had pork prohibitions, but as soon as they realized that a long, hot cooking process rendered the meat harmless, they were dropped. Long before the early Roman Empire times, it was common knowledge and only those adhering to the old Mosaic laws kept up the prohibition as tradition.
The repealing was done as a direct instruction from God because that was probably the only way to get the traditionalists to accept the change and was likely initiated as the early Jewish Christians interacted more with the Romans and Greeks and the knowledge that pork and related "unclean" meats were now safe to eat. And that the gentiles who were becoming more and more of the Christian base weren't going to accept archaic traditions.
Well, they are being fined $11 mil for this missing of the deadline.
An opinion on the law being violated was given in footnote 5 on page 12 of the judgement. It suggests he is not guilty of the charge.
If he is retried, he can bring into evidence footnote 5 on page 12 of the judgement where the judges advanced the opinion that he was innocent of the accessing without authorization or in excess of authorization charge because there was no password or code barrier and the program accessed a publicly facing interface and retrieved information that AT&T unintentionally published. It reads that even if they found the venue as correct, they would have vacated the guilty verdict because of that.
Actually, it is a paradox. He can't fix stuff if it is never accepted.
The fix needed is in the systemd code, not the kernel. He can fix it, in less than a minute of editing probably two constants. (from "debug" and "quiet" to "systemd.debug" and "systemd.quiet")
The problem is systemd is a johnny-come-lately and is violating the standard way of doing things, even if the standard way isn't the most optimal. Think of it like a court of law, no court is going to accept a junior lawyer changing terminology that has been in use for centuries just because the lawyer has read a thesaurus. The impact is just too large.
To take it further, apparently all but two parameters (debug and quiet) that systemd recognizes are prefixed by systemd.xxxxxx, so they know how to work within the kernel standard.
The kernel has for a long time had a protocol of parameter naming. Direct kernel parameters are plain, module-specific parameters have mod.xxxx format and that was designed to pass driver-specific parameters in. SystemD, being a child process and not even part of the kernel should respect the existing protocol and ignore any parameters not passed without a leading systemd.
The balaclava isn't for you to wear to hide yourself, it's to pull over the head of the glasshole to cover the camera up. And get them in trouble with the fuzz.
Disable the DNS Client service in Services MMC stops this as well. You'll have a few more DNS queries, but who cares.
Begone and good riddence to your vandalizing of channels.
The problem with producing a car that can only do the highway speed limit, is that it can then still exceed the town limits which is where you have the greater risk of hitting people and other cars.
Imagine an area on the plane where the screaming kids will sit, able to hear what's going on, but not being heard. Or to separate first class from cattle class even better than it already is. Not the most necessary of solutions, but might gain them some extra pax.
They are documented in the regulations linked by the GP and there are clearly documented compliance and appeals processes in there as well. It's a hell of a read though.