This is a great post. Wish I could mode it up. Can you confirm or refudiate this part of Wikipedia
>Because the ACARS network is modeled after the point-to-point telex network, all messages come to a central processing location to be routed
Even though it's not satellite, it still seems to be shared infrastructure that should affect everybody equally unless it is the final ground link.
I hope that somebody who has worked on these systems will comment here. ACARS is a satellite-based system and I don't think that each airline has their own satellite. So how is it that this only affected United and not everybody? Something doesn't add up here. There are a lot of snarky comments here but on-board aircraft software doesn't get updated en mass. The only thing I can really think of is that the ground-based IT systems were unable to process ACARS data. But that wouldn't be for bandwidth-related issues!
Fair enough, but I'm still pretty sure that the driver didn't turn on the Harry Potter movie *after* being beheaded so it's a fair assertion that the movie was on at the time of the beheading!
I would say that if the movie is playing a few seconds after the person just died a fiery death, it's pretty reasonable that it was playing before the person died!
And if somebody opens up an amusement park ride where you jump ten stories onto an awning and people start dying, we would shut down that 'attraction!' More common, I've seen plenty of hotels have to install barriers to prevent people from jumping from the balconies into the pool! If those hotels instead started marking the pools in a way that encouraged people to jump into it from the third floor, it would also be objectionable.
Embassies and diplomatic convoys have different levels of protection. Plus as has already been pointed out the embassy is in a multi-tenant building and there's no way to get from the embassy to a vehicle. Maybe a diplomatic helicopter and a long rope to climb up if you want to be fanciful. But this isn't a realistic option either.
This does look like a stunt. But as always, by the time the news gets to us ordinary people it has been mis-translated and mis-transcribed so many times that you can't make sense of it. Sentence commutations and pardons are two different things. The timing of the release seems minor compared to this being a commutation rather than a pardon. Of course I also doubt that this played into Obama's decision
http://xpungechicago.com/lawye...
Hoarding passwords for revenge might actually work. You could claim that you forgot the password especially since it was quite some time between when he was fired and when he was asked for the password. But to then "offer to help" in exchange for money, it's no longer revenge but rather extortion. He's lucky not to go to jail.
I'm pretty sure that his mortgage contract would forbid this. So he should call his bank and ask them to initiate the foreclosure procedure right away before the house burns down.
>> Sanders simply took advantage of the passion and naivety of young voters and told them what they wanted to hear.
Trump simply took advantage of the passion and naivety of uneducated, grey-haired voters and told them what they wanted to hear. Fixed that for you.
Control Flow Guard (CFG) is a highly-optimized platform security feature that was created to combat memory corruption vulnerabilities. By placing tight restrictions on where an application can execute code from, it makes it much harder for exploits to execute arbitrary code through vulnerabilities such as buffer overflows. CFG extends previous exploit mitigation technologies such as/GS, DEP, and ASLR.
This feature is available in Microsoft Visual Studio 2015, and runs on "CFG-Aware" versions of Windows—the x86 and x64 releases for Desktop and Server of Windows 10 and Windows 8.1 Update (KB3000850).
We strongly encourage developers to enable CFG for their applications. You don't have to enable CFG for every part of your code, as a mixture of CFG enabled and non-CFG enabled code will execute fine. But failing to enable CFG for all code can open gaps in the protection. Furthermore, CFG enabled code works fine on "CFG-Unaware" versions of Windows and is therefore fully compatible with them.
https://msdn.microsoft.com/en-...
Which would also be true if you ran Ubuntu LTS. Except at some point you are going to have an unpatched security issue on Win/7 and then you're painted in a corner. Even with all inbound ports closed, that is no guarantee of exploit avoidance. How about somebody finds a bug in the Win/7 DNS client and it's unsupported so M$ doesn't issue a patch. You could then extend the example to you would never connect to a network where the firewall doesn't protect you from this. So no coffee shops and, more importantly, no airplanes. At some point you could entirely disconnect from any networks. But at that same point Windows/7 and Windows/10 look about the same. At some point vendors will drop Windows/7 support. At that point are you just going to run with no support even if it's a flagship application? Given the amount of down mods I've received for very neutral-tone postings, I have little hope of adding much reason here. Even if Win/7 was the best thing ever, you can't stay on it forever. As you have pointed out, telemetry isn't going anywhere, so everybody needs an upgrade plan. I'm clearly a minority. I actually went out and bought new hardware just to get Windows/10. But no matter what our philosophical opinions, the vast majority of people will not be able to continue to run Win/7 and, even if they could, shouldn't. I'm sure a few/. users will be able to do this and be smug about it. The rest of the world, should be looking at supported OSes. Many of the Win/10 features are also in Ubuntu and MacOS so clearly there is consensus that these are necessary.
I think the hope is that if enough people boycott Win/10, MSFT will relent on telemetry. I wish the/. crowd luck in that thinking. But Win/10 is being deployed left and right and is here to stay and a better plan would be how to figure out how to live in a Windows/10 world.
The general gist of this thread is that Windows/10 telemetry is such an awful evil that, even if the operating system were otherwise perfect, it's a crime against humanity to use it. I don't necessarily agree with that assertion. But the interesting part is the "you people" no longer seem to think that Linux is a good alternative. Instead, what we see is a clinging to Windows/7 like it is the chef d'ouvre of operating systems. So I don't think this is a "Linux People" place anymore. If you look at my posting history, I've never been modded down before. But every single one of my comments has been moderated -1 Disagree.
Also do you have any idea how hard it is to find an ASLR leak? These are the same or similar features to those found in gcc / Ubuntu. You can read about the Ubuntu implementations here.
https://wiki.ubuntu.com/Securi... These are features implemented by all modern operating systems / compilers. But they weren't common in the Windows 7 era. Again we could all *prefer* that MSFT back port features to Win/7 and or give up on Windows/10 telemetry. But to instead expose ourselves and/or customers in order to support an ideology achieves nothing and just makes us look silly. Here's another chance for somebody to mod me down. Have fun.
I can't make a statement about any *individual's* state of mind. I can, however, make a statement about the general attitude. I've tried to be fairly objective in my comments here. I've never been modded down before but I've had posts pushed down to zero in this thread even though I've made the case in a very non-alarmist way. If Windows/10 were to cure all diseases, end poverty, and give everybody a pony, people would respond "but it has telemetry" and the post would get modded to -1. That's a problem because it means this isn't an adult discussion.
The reality is that the computing environment has evolved. It used to be that Win/7 with EMET could survive on the internet. Now, not so much. The attacks have gotten more sophisticated. If adversaries weren't evolving we could stick with older OSes much longer. But that's not the case. MSFT could have backported some of the new technologies to Win/7 but that doesn't fit their business model. This may be a good time to switch to Linux.
Plus the nag screens in Windows/10 are insane. They even put up an icon encouraging you to switch from Firefox to Edge. And when you buy a new machine, they add apps to your profile and push them down on your existing machines. I can think of a thousand things wrong with Windows 10 that should make people consider moving to Ubuntu, MacOS, or other. Those things are not a good reason to stick with Windows/7 and open yourself to some much more serious problems, but I'm resigned to getting modded into oblivion for saying so.
My preference is an LTS flavor of Ubuntu. But if you're going to run Windows, you need to run a supported version. Outdated, unpatched operating systems should be a non-starter. There was a time on/. that everybody claimed to run Linux (although most now admit that they posted from Windows computers in their mothers' basements). Now it seems we have Windows 7 fanbois. That's really a shame. There are lots of good, competing options out there. But Win/7 is not a competitor to Windows 10 going forward.
Windows/95 most certainly had pre-emptive multi-tasking. It was only for 32-bit processes. 16-bit processes shared a single thread and use cooperative multi-tasking like Windows 3.1.
The underlying thought here on/. seems to be that we should talk down Windows 10 so that MSFT repents and gives us a Windows/10 without telemetry. This isn't a good strategy. I can't support staying on an older OS as a means of social protest. I'm getting modded into oblivion but don't really care. If you don't like Windows/10, look at a migration to Ubuntu or even MacOS, but staying on Windows/7 is a losing battle.
Slashdot Mirror
This is a great post. Wish I could mode it up. Can you confirm or refudiate this part of Wikipedia >Because the ACARS network is modeled after the point-to-point telex network, all messages come to a central processing location to be routed Even though it's not satellite, it still seems to be shared infrastructure that should affect everybody equally unless it is the final ground link.
I hope that somebody who has worked on these systems will comment here. ACARS is a satellite-based system and I don't think that each airline has their own satellite. So how is it that this only affected United and not everybody? Something doesn't add up here. There are a lot of snarky comments here but on-board aircraft software doesn't get updated en mass. The only thing I can really think of is that the ground-based IT systems were unable to process ACARS data. But that wouldn't be for bandwidth-related issues!
Fair enough, but I'm still pretty sure that the driver didn't turn on the Harry Potter movie *after* being beheaded so it's a fair assertion that the movie was on at the time of the beheading!
I would say that if the movie is playing a few seconds after the person just died a fiery death, it's pretty reasonable that it was playing before the person died!
And if somebody opens up an amusement park ride where you jump ten stories onto an awning and people start dying, we would shut down that 'attraction!' More common, I've seen plenty of hotels have to install barriers to prevent people from jumping from the balconies into the pool! If those hotels instead started marking the pools in a way that encouraged people to jump into it from the third floor, it would also be objectionable.
Embassies and diplomatic convoys have different levels of protection. Plus as has already been pointed out the embassy is in a multi-tenant building and there's no way to get from the embassy to a vehicle. Maybe a diplomatic helicopter and a long rope to climb up if you want to be fanciful. But this isn't a realistic option either.
This does look like a stunt. But as always, by the time the news gets to us ordinary people it has been mis-translated and mis-transcribed so many times that you can't make sense of it. Sentence commutations and pardons are two different things. The timing of the release seems minor compared to this being a commutation rather than a pardon. Of course I also doubt that this played into Obama's decision http://xpungechicago.com/lawye...
The S7 Edge is a pretty good device and it doesn't spontaneously combust!
UberPool?
I wish I had mod points
Hoarding passwords for revenge might actually work. You could claim that you forgot the password especially since it was quite some time between when he was fired and when he was asked for the password. But to then "offer to help" in exchange for money, it's no longer revenge but rather extortion. He's lucky not to go to jail.
I'm pretty sure that his mortgage contract would forbid this. So he should call his bank and ask them to initiate the foreclosure procedure right away before the house burns down.
They will give him a comparable, alternate device!
The problem is that his stupid risk will harm and possibly kill others. A free society does not allow reckless endangerment of others.
>> Sanders simply took advantage of the passion and naivety of young voters and told them what they wanted to hear. Trump simply took advantage of the passion and naivety of uneducated, grey-haired voters and told them what they wanted to hear. Fixed that for you.
Control Flow Guard (CFG) is a highly-optimized platform security feature that was created to combat memory corruption vulnerabilities. By placing tight restrictions on where an application can execute code from, it makes it much harder for exploits to execute arbitrary code through vulnerabilities such as buffer overflows. CFG extends previous exploit mitigation technologies such as /GS, DEP, and ASLR.
This feature is available in Microsoft Visual Studio 2015, and runs on "CFG-Aware" versions of Windows—the x86 and x64 releases for Desktop and Server of Windows 10 and Windows 8.1 Update (KB3000850).
We strongly encourage developers to enable CFG for their applications. You don't have to enable CFG for every part of your code, as a mixture of CFG enabled and non-CFG enabled code will execute fine. But failing to enable CFG for all code can open gaps in the protection. Furthermore, CFG enabled code works fine on "CFG-Unaware" versions of Windows and is therefore fully compatible with them.
https://msdn.microsoft.com/en-...
Which would also be true if you ran Ubuntu LTS. Except at some point you are going to have an unpatched security issue on Win/7 and then you're painted in a corner. Even with all inbound ports closed, that is no guarantee of exploit avoidance. How about somebody finds a bug in the Win/7 DNS client and it's unsupported so M$ doesn't issue a patch. You could then extend the example to you would never connect to a network where the firewall doesn't protect you from this. So no coffee shops and, more importantly, no airplanes. At some point you could entirely disconnect from any networks. But at that same point Windows/7 and Windows/10 look about the same. At some point vendors will drop Windows/7 support. At that point are you just going to run with no support even if it's a flagship application? Given the amount of down mods I've received for very neutral-tone postings, I have little hope of adding much reason here. Even if Win/7 was the best thing ever, you can't stay on it forever. As you have pointed out, telemetry isn't going anywhere, so everybody needs an upgrade plan. I'm clearly a minority. I actually went out and bought new hardware just to get Windows/10. But no matter what our philosophical opinions, the vast majority of people will not be able to continue to run Win/7 and, even if they could, shouldn't. I'm sure a few /. users will be able to do this and be smug about it. The rest of the world, should be looking at supported OSes. Many of the Win/10 features are also in Ubuntu and MacOS so clearly there is consensus that these are necessary.
I think the hope is that if enough people boycott Win/10, MSFT will relent on telemetry. I wish the /. crowd luck in that thinking. But Win/10 is being deployed left and right and is here to stay and a better plan would be how to figure out how to live in a Windows/10 world.
The general gist of this thread is that Windows/10 telemetry is such an awful evil that, even if the operating system were otherwise perfect, it's a crime against humanity to use it. I don't necessarily agree with that assertion. But the interesting part is the "you people" no longer seem to think that Linux is a good alternative. Instead, what we see is a clinging to Windows/7 like it is the chef d'ouvre of operating systems. So I don't think this is a "Linux People" place anymore. If you look at my posting history, I've never been modded down before. But every single one of my comments has been moderated -1 Disagree.
Also do you have any idea how hard it is to find an ASLR leak? These are the same or similar features to those found in gcc / Ubuntu. You can read about the Ubuntu implementations here. https://wiki.ubuntu.com/Securi... These are features implemented by all modern operating systems / compilers. But they weren't common in the Windows 7 era. Again we could all *prefer* that MSFT back port features to Win/7 and or give up on Windows/10 telemetry. But to instead expose ourselves and/or customers in order to support an ideology achieves nothing and just makes us look silly. Here's another chance for somebody to mod me down. Have fun.
I can't make a statement about any *individual's* state of mind. I can, however, make a statement about the general attitude. I've tried to be fairly objective in my comments here. I've never been modded down before but I've had posts pushed down to zero in this thread even though I've made the case in a very non-alarmist way. If Windows/10 were to cure all diseases, end poverty, and give everybody a pony, people would respond "but it has telemetry" and the post would get modded to -1. That's a problem because it means this isn't an adult discussion.
The reality is that the computing environment has evolved. It used to be that Win/7 with EMET could survive on the internet. Now, not so much. The attacks have gotten more sophisticated. If adversaries weren't evolving we could stick with older OSes much longer. But that's not the case. MSFT could have backported some of the new technologies to Win/7 but that doesn't fit their business model. This may be a good time to switch to Linux.
Plus the nag screens in Windows/10 are insane. They even put up an icon encouraging you to switch from Firefox to Edge. And when you buy a new machine, they add apps to your profile and push them down on your existing machines. I can think of a thousand things wrong with Windows 10 that should make people consider moving to Ubuntu, MacOS, or other. Those things are not a good reason to stick with Windows/7 and open yourself to some much more serious problems, but I'm resigned to getting modded into oblivion for saying so.
My preference is an LTS flavor of Ubuntu. But if you're going to run Windows, you need to run a supported version. Outdated, unpatched operating systems should be a non-starter. There was a time on /. that everybody claimed to run Linux (although most now admit that they posted from Windows computers in their mothers' basements). Now it seems we have Windows 7 fanbois. That's really a shame. There are lots of good, competing options out there. But Win/7 is not a competitor to Windows 10 going forward.
Windows/95 most certainly had pre-emptive multi-tasking. It was only for 32-bit processes. 16-bit processes shared a single thread and use cooperative multi-tasking like Windows 3.1.
The underlying thought here on /. seems to be that we should talk down Windows 10 so that MSFT repents and gives us a Windows/10 without telemetry. This isn't a good strategy. I can't support staying on an older OS as a means of social protest. I'm getting modded into oblivion but don't really care. If you don't like Windows/10, look at a migration to Ubuntu or even MacOS, but staying on Windows/7 is a losing battle.