and I'm sure there are common USB-to-ATC radar adapters you can just get on Amazon.
Many times the reason you see an antiquated OS still being used is because there was some very specific software written to talk to an incredibly unique (and expensive) piece of hardware, and that software just won't work in any other configuration. Also, they just can't shut the system down for a few hours in order to fuck around with it, so there's that.
On OS X, there are two places (by convention) where it is always safe for an application to write anything, because of the file permissions system. Those are:
~/Library/Application Support
~/Library/Preferences
The first location is meant for user-specific plugins and metadata per application (e.g. ~/Library/Application Support/Firefox/Bookmarks). The second is the place that user-specific preferences and settings get written, in a reverse-DNS style filename for the app so that it doesn't get stomped by other apps: ~/Library/Preferences/com.apple.iTunes.plist for example.
Neither of these things are deleted if you delete the app, which is stored under/Applications/MyCoolApp.app. It's been this way since NeXTSTEP, and it sure didn't change at the launch of the App Store.
Let's be clear - I didn't say that it's fine, and I'd appreciate you not insinuating that I did. It's absolutely not. But you're not powerless to stop it. Shitcan their phone home bullshit where they can't do anything about it, because anything you do on the box that is running their OS can is a temporary measure at best if they are intent on delivering your information.
Pure, Unabashed, FUD. Millions of people use their iPhone / iPad / Mac to play games or listen to music on airlines without a network connection EVERY DAY.
You can always black hole route the IPs themselves. Yes, this is a pain in the ass, but no desktop OS can dictate to my router what it does with packets.
Yeah, because there are tons of large enterprise customers that depend only on the awesome software firewall in various states of configuration on thousands of machines strewn across the landscape.
No, I'm pretty sure that if they're serious about it, they'll use authenticated proxy servers and firewall appliances at the egress which also filter outbound traffic. Any properly engineered corporate network would shitcan this traffic long before it ever made it out.
In my experience, WinXP 64 wouldn't run *. It was as much of a general purpose OS as Windows NT 4 was.
Vista was shit, but at least could run most commercial software without vomiting (after it was patched a bazillion times).
Windows 7 worked pretty good. 8 was basically 7 with a shit UI. 10 isn't bad if you blackhole all the spyware shit. I've yet to run across something I can't get to work on it, once I got it over it's fear of the Intel X99 chipset microcode.
You can install anything you want on OS X, right down to downloading source code and compiling yourself. There are whole package managers that port Linux utilities to run on OS X, and a complete X11 system for compatibility with those ports. Get a clue before spouting false statements.
And the bigger it is, the harder it will be to overcome it's inertia.
The Apollo 11 CSM had a launch mass of 28,801 kg, and took the most powerful non-nuclear device mankind has ever created to get it to the moon.
The asteroid "99942 Apophis" is ~325m, which is close to your hypothetical 350m asteroid, and has a mass of 4x10^10 kg. That's 40,000,000,000 kg. It also has an average velocity of 30.728 km/s.
It would take a pretty fucking big accident to get that one to crash into the Earth, even with it passing fairly close by. Like, an "accident" that involved the purposeful mounting of rocket engines and fueling over many tanker launches (or refining of materials collected in space) to the asteroid to turn it into a kinetic weapon on purpose, to say nothing of having to do a massive survey of the thing to make sure you get the rockets thrusting against the exact center of gravity so you don't just enhance it's natural spin, and then calculate the proper transfer maneuver to actually hit Earth, because it turns out that it's pretty easy to miss a planet.
If it's big enough to mine, it's big enough to secure yourself to without altering it's trajectory in any meaningful way. Newton's laws still work.
Yeah, except any asteroid big enough to not just break up in the atmosphere and make a fairly impressive light show would require an amazing amount of fuel to be burned to get enough delta-V to alter it's solar orbit in any meaningful way. As it turns out, the more mass something has, the harder it is to move out of it's current trajectory.
Why would anyone waste the resources engineering and executing such an effort unless they were a Bond villain in one of those bad late 70s movies? Also, if they are there to mine that fucker, why wouldn't they just drill out whatever they're there for and leave? Also, even if they were to dig out enough mass to make it easier to move, it's in orbit around the sun; it would be much easier to deorbit into the sun than execute what is essentially an interplanetary transfer to orbit Earth, much less intersect with it...
There never was any dispute. However, sometimes it's necessary to codify common sense, in order to preemptively ward off greedy assholes who suffer from an astonishing lack of common sense.
Is it just me, or did you not even think about this for 5 seconds? The US Government just said that they are treating space mining exactly the same as any other mining operation - those that dig the shit out, keep it. This equally applies to a Euro / Russian / Chinese / Indian company if they decide to go space mining, though it doesn't appear to be an issue in any of those jurisdictions as there are not private enterprises actively performing space activities outside of government contracts.
And if you read the article, you'll see that the Air Force knew of a flaw in the upper stage motor, but wanted to launch anyway to get data from the first stage.
Why would they load it up with shitloads of satellites when they know it will never leave the atmosphere? Answer: they wouldn't, and didn't.
The problem is that this article (or at least TFS) is talking about enterprise customers, who have likely deployed an MDM solution and gone through the process to be able to side-load apps onto their enrolled devices bypassing the App Store. So you've got incompetent developers that are using hacked versions of Xcode (or, pre-hacked libraries, as you postulate), combined with bypassing the checkpoint that keeps most of Apple's users free of this crap.
And the reason why this article is specific to talking about enterprise, is because those businesses are doing two things that the average user won't be:
1. Downloading a hacked version of Xcode from a non-Apple website, and using it to develop applications, which then get trojaned by the crap version of Xcode 2. Sideloading these applications by way of their developer agreement / MDM solution, bypassing the App Store and it's approval / curation.
Please show me how I'm restricted from installing anything I want on my Mac.
Go ahead, we'll wait.
In case you missed it, this article is about people running hacked versions of Xcode on OS X, and iPhone and iPad are only involved distantly as the platform that people are writing code for in Xcode... on their Mac.
Slashdot Mirror
The good thing is that we've had PCI to ISA bridge chips for at least a decade: https://www.altera.com/product...
So unless they are doing some seriously weird low-level signal nonsense, you would be able to get past that with some hardware hackery.
and I'm sure there are common USB-to-ATC radar adapters you can just get on Amazon.
Many times the reason you see an antiquated OS still being used is because there was some very specific software written to talk to an incredibly unique (and expensive) piece of hardware, and that software just won't work in any other configuration. Also, they just can't shut the system down for a few hours in order to fuck around with it, so there's that.
Now only if there was some kind of alternative OS to UNIX/BSD/Linux that doesn't act that way with F-key scan codes...
On OS X, there are two places (by convention) where it is always safe for an application to write anything, because of the file permissions system. Those are:
~/Library/Application Support
~/Library/Preferences
The first location is meant for user-specific plugins and metadata per application (e.g. ~/Library/Application Support/Firefox/Bookmarks). The second is the place that user-specific preferences and settings get written, in a reverse-DNS style filename for the app so that it doesn't get stomped by other apps: ~/Library/Preferences/com.apple.iTunes.plist for example.
Neither of these things are deleted if you delete the app, which is stored under /Applications/MyCoolApp.app. It's been this way since NeXTSTEP, and it sure didn't change at the launch of the App Store.
Has to be a troll. Reasoning:
... real operating systems such as GNU/Hurd...
Spoken like someone trapped in an elevator.
Let's be clear - I didn't say that it's fine, and I'd appreciate you not insinuating that I did. It's absolutely not. But you're not powerless to stop it. Shitcan their phone home bullshit where they can't do anything about it, because anything you do on the box that is running their OS can is a temporary measure at best if they are intent on delivering your information.
Pure, Unabashed, FUD. Millions of people use their iPhone / iPad / Mac to play games or listen to music on airlines without a network connection EVERY DAY.
Stop lying.
You can always black hole route the IPs themselves. Yes, this is a pain in the ass, but no desktop OS can dictate to my router what it does with packets.
Yeah, because there are tons of large enterprise customers that depend only on the awesome software firewall in various states of configuration on thousands of machines strewn across the landscape.
No, I'm pretty sure that if they're serious about it, they'll use authenticated proxy servers and firewall appliances at the egress which also filter outbound traffic. Any properly engineered corporate network would shitcan this traffic long before it ever made it out.
In my experience, WinXP 64 wouldn't run *. It was as much of a general purpose OS as Windows NT 4 was.
Vista was shit, but at least could run most commercial software without vomiting (after it was patched a bazillion times).
Windows 7 worked pretty good. 8 was basically 7 with a shit UI. 10 isn't bad if you blackhole all the spyware shit. I've yet to run across something I can't get to work on it, once I got it over it's fear of the Intel X99 chipset microcode.
You ask for a citation of evidence for Windows 10 users being spied on, and then make a completely baseless claim that Apple is doing the same.
I'll now ask you for evidence of that, and refrain from name calling while I wait for the answer that will never come.
And when it still doesn't block it, as has been proven by sniffing the actual network traffic?
Hint: OS X != iOS.
You can install anything you want on OS X, right down to downloading source code and compiling yourself. There are whole package managers that port Linux utilities to run on OS X, and a complete X11 system for compatibility with those ports. Get a clue before spouting false statements.
And the bigger it is, the harder it will be to overcome it's inertia.
The Apollo 11 CSM had a launch mass of 28,801 kg, and took the most powerful non-nuclear device mankind has ever created to get it to the moon.
The asteroid "99942 Apophis" is ~325m, which is close to your hypothetical 350m asteroid, and has a mass of 4x10^10 kg. That's 40,000,000,000 kg. It also has an average velocity of 30.728 km/s.
It would take a pretty fucking big accident to get that one to crash into the Earth, even with it passing fairly close by. Like, an "accident" that involved the purposeful mounting of rocket engines and fueling over many tanker launches (or refining of materials collected in space) to the asteroid to turn it into a kinetic weapon on purpose, to say nothing of having to do a massive survey of the thing to make sure you get the rockets thrusting against the exact center of gravity so you don't just enhance it's natural spin, and then calculate the proper transfer maneuver to actually hit Earth, because it turns out that it's pretty easy to miss a planet.
If it's big enough to mine, it's big enough to secure yourself to without altering it's trajectory in any meaningful way. Newton's laws still work.
Yeah, except any asteroid big enough to not just break up in the atmosphere and make a fairly impressive light show would require an amazing amount of fuel to be burned to get enough delta-V to alter it's solar orbit in any meaningful way. As it turns out, the more mass something has, the harder it is to move out of it's current trajectory.
Why would anyone waste the resources engineering and executing such an effort unless they were a Bond villain in one of those bad late 70s movies? Also, if they are there to mine that fucker, why wouldn't they just drill out whatever they're there for and leave? Also, even if they were to dig out enough mass to make it easier to move, it's in orbit around the sun; it would be much easier to deorbit into the sun than execute what is essentially an interplanetary transfer to orbit Earth, much less intersect with it...
There never was any dispute. However, sometimes it's necessary to codify common sense, in order to preemptively ward off greedy assholes who suffer from an astonishing lack of common sense.
Is it just me, or did you not even think about this for 5 seconds? The US Government just said that they are treating space mining exactly the same as any other mining operation - those that dig the shit out, keep it. This equally applies to a Euro / Russian / Chinese / Indian company if they decide to go space mining, though it doesn't appear to be an issue in any of those jurisdictions as there are not private enterprises actively performing space activities outside of government contracts.
Most grade school kids could figure this out:
man openssl
Combine OpenSSL with a little AppleScript, and voila, you have the same "proof of concept" that TFA is basically showing. What a fucking joke.
Hey look! I have a "proof of concept" too!
#!/bin/bash
openssl aes-256-cbc -in ~/Documents/* -out ~/ransom.aes -d -pass $up3r$ecretPassw0rd!
Pay me or you'll never see your documents again!
And if you read the article, you'll see that the Air Force knew of a flaw in the upper stage motor, but wanted to launch anyway to get data from the first stage.
Why would they load it up with shitloads of satellites when they know it will never leave the atmosphere? Answer: they wouldn't, and didn't.
The problem is that this article (or at least TFS) is talking about enterprise customers, who have likely deployed an MDM solution and gone through the process to be able to side-load apps onto their enrolled devices bypassing the App Store. So you've got incompetent developers that are using hacked versions of Xcode (or, pre-hacked libraries, as you postulate), combined with bypassing the checkpoint that keeps most of Apple's users free of this crap.
And the reason why this article is specific to talking about enterprise, is because those businesses are doing two things that the average user won't be:
1. Downloading a hacked version of Xcode from a non-Apple website, and using it to develop applications, which then get trojaned by the crap version of Xcode
2. Sideloading these applications by way of their developer agreement / MDM solution, bypassing the App Store and it's approval / curation.
Please show me how I'm restricted from installing anything I want on my Mac.
Go ahead, we'll wait.
In case you missed it, this article is about people running hacked versions of Xcode on OS X, and iPhone and iPad are only involved distantly as the platform that people are writing code for in Xcode... on their Mac.
Yeah, it's totally Apple's fault that these asshats downloaded a hacked version Apple's Xcode IDE from a website not hosted by Apple.