We’ve asked Microsoft for comment, although it already said it was “investigating the matter.” The Vergeclaimed the code was legitimate, with Ronin Dey and others also supporting those beliefs (via Windows Central).
One version of the code leak also includes code for MS DOS, Windows CE, Windows Embedded and Windows NT, although those aren’t believed to be new leaks. Experts talking to ZDNet believed the new leaks came from academia, which has long had access to Windows source code to help bolster its security.
This won’t necessarily lead to security issues on par with the WannaCry ransomware attack. While WannaCry exploited Windows XP flaws, the campaign succeeded in part due to poor security policies. No amount of source code will change that, especially if it doesn’t include later XP releases. Microsoft also ended regular support for Windows XP in 2014, limiting any help to organizations with special contracts. Windows XP has been vulnerable for years, and this isn’t likely to make the situation worse.
The Windows XP SP1 source code leak looks pretty legit
For all the emergency training I went through as an astronaut, I never expected to be holed up in the Russian segment of the ISS, the hatch to the US segment sealed, with my crew waiting and wondering—would the space station be destroyed? Was this the end? As we floated there and pondered our predicament, I felt a bit like the guy in the Alanis Morissette song “Ironic,” who was going down in an airplane crash, thinking to himself, “Now isn’t this ironic?” This is how we ended up in that situation.
Every space station crew trains for all types of emergencies—computer failures, electrical shorts, equipment malfunctions, and more serious fire and air leak scenarios. However, on the International Space Station, the most dangerous of all is an ammonia leak. In fact, our NASA trainers used to tell us, “If you smell ammonia, don’t worry about running the procedure, because you’re going to die anyway.” That sure instilled confidence.
A few months after arriving in space, we were having a typical day. My crewmate Samantha Cristoforetti and I were each in our own crew quarters, going through email and catching up with administrative work, when the alarm went off. The sound of the ISS alarm is exactly what you would think a proper space alarm should sound like—a cross between a Star Trek alarm and a sci-fi B-movie klaxon. When it goes off, there is no doubt that something significant is happening. Sam and I both popped our heads out of our respective quarters and glanced at the alarm panel.
When I saw the ATM alarm lit up, my first thought was, “Atmosphere— there must be an atmosphere leak.” The ISS had occasionally had an air leak false alarm over its fifteen-year history, and I thought it must be one of those. However, that is not what ATM means—it stands for toxic atmosphere, most probably from an ammonia leak. Significantly, this alarm was going off for the first time in ISS history. My brain couldn’t believe it, so I said to Samantha, “This is an air leak, right?” To which she immediately responded “NO—ammonia leak!”
Jolted back to reality, we jumped into action. Gas masks on. Account for everyone; we didn’t want anyone left behind. Float down to the Russian segment ASAP and close the hatch between the US and Russian segments. The US segment uses ammonia as a coolant, but the Russian segment doesn’t, so the air should be safe there. Remove all clothes in case they’re contaminated. Nobody smelled ammonia, so we skipped this step! Close a second hatch to
keep any residual ammonia vapors on the American segment. Get out the ammonia “sniffer” device to make sure there isn’t any of that deadly chemical in the atmosphere on the Russian segment. All clear. Then, await word from Houston. . . .
Fifteen long, suspense-filled minutes later, we got the news—it was a false alarm. We let out a collective sigh of relief; the station wouldn’t be dying today! Whew. Similar to frequent fire alarms and rare air leaks, ammonia leak was just added to the collection of ISS false alarms. We put away the ammonia detector, floated back to the US segment, and started to clean up the mess that we had left floating in midair when that alarm went off.
Then we received an urgent call. “Station, Houston, execute ammonia leak emergency response, I say again, execute emergency response, ammonia leak, this is not a drill!” Pretty unambiguous. Only this time the warning had come via a radio call, not via electronic alarm. After the false alarm I knew that an army of NASA engineers were in mission control, poring over every piece of data they had, trying to determine if this had been a false alarm or the real thing. Now that mission control had confirmed that it was an actual leak, there was no doubt in my mind that this thing was real. No way all those NASA engineers got this call wrong. Having worked in mission control for nearly a decade myself, I had complete confidence in our flight director and flight control team. When they said, “Execute ammonia response,” I put the mask on, shut the hatch, and asked questions later.
It was like a scene out of European Vacation—“Look kids! Big Ben!”—or maybe Groundhog Day. Oxygen masks activated—check. US segment evacuated with nobody left behind—check. Hatch between US and Russian segments closed and sealed—check. Get naked—nope. No ammonia in the Russian atmosphere—check.
By this point, we had run the ISS ammonia leak procedures twice within an hour of each other. We had a quick debrief as a crew to discuss how we handled the emergency, what checklist steps were missed, what could have been done better, and what we needed to report to Houston. By this point, it was very obvious that there would be a lot of meetings happening in Houston and Moscow and that everybody in the NASA chain of command would be aware of our predicament.
Very quickly the gravity (pun intended) of the situation hit us. Using ammonia as the coolant for the American half of the ISS had worked well for decades, but we were acutely aware of its danger. Thankfully, the engineers who designed the station did a great job making a leak extremely unlikely, but the possibility was always there. On the other hand, the Russian glycol-based coolant is not dangerous, which is why the whole station crew would safe haven there in the event of an ammonia leak.
Besides the danger of the crew breathing in toxic fumes, there was a risk to equipment. The ISS has two ammonia loops, a series of tanks and pipes that carry heat from the station’s internal water loops to the external radiators. If one leaked out to space, there would still be a second available to cool equipment. It would be a serious loss of redundancy for the station, especially given that there is no longer a space shuttle to restock the station with the massive ammonia tanks needed to fill a loop. It would be ugly, but survivable.
What is not survivable, however, is having that ammonia leak to the inside of the American segment. First of all, if the entire contents of an ammonia loop came inside the station, it would probably overpressurize and pop the aluminum structure of one or more of the modules, like a balloon being overfilled with air. Mission control could avert this problem by venting the ammonia to space—we would lose the cooling loop, but it would prevent the station from popping. Months after returning to Earth, I learned that Houston had been seriously considering that option during our emergency, and it was only averted because of a tough—and ultimately correct—call by our flight director. That’s why those guys get paid the big bucks—they are some of the smartest and most competent people I have ever worked with. However, even if you averted a catastrophic “popping” of structure, there would still be the problem of ammonia in the US segment.
If even a small amount of ammonia were present in the atmosphere, it would be difficult, if not impossible, to remove. The only scrubber we had was our ammonia masks, so theoretically you could have an astronaut sit in a contaminated module, breathing the contaminant out of the air and into the mask filter, and over time enough of this scrubbing would lower the ammonia concentration, but as the poor astronaut sat there cleaning the air he would also be covered in ammonia, and convincing his fellow crewmates on the Russian segment to allow him back to their clean air would be problematic, to say the least. There would need to be some sort of shower and cleaning system to completely clean him up, which of course doesn’t exist in space. It would be a similar situation to soldiers in a chemical warfare environment, or the Soviet soldiers in the recent miniseries Chernobyl. Dealing with a toxic environment on Earth is difficult enough, but in space it would be nearly impossible. The reality is that an actual leak into the American segment would make a significant portion of the ISS uninhabitable, and if there were no crew there when the equipment broke down, there would be nobody to fix it.
A real ammonia leak would eventually lead to the slow death of the US half of the ISS, which would then lead to the end of the entire station. We knew this and spent our afternoon staring at each other, wondering out loud how long it would be before they sent us home, leaving the space station uninhabited and awaiting an untimely death.
Later that evening, we received a call from Houston. “Just kidding, it was a false alarm.” That was a huge false alarm. It turned out that some cosmic radiation had hit a computer, causing it to kick out bad data regarding the cooling system, and it took Houston hours to sort out what was really happening. Because that call from Houston had told us that it was a real leak, we all believed it—we knew that the folks in mission control were some of the best engineers in the world and that they would be 100 percent sure before making a call like that. So we were very relieved to get that call.
The Department didn’t directly comment on SMIC, but told Reuters it was “constantly monitoring and assessing” possible threats to US security and foreign policy.
SMIC, meanwhile, appeared to have been caught by surprise. A spokesperson said the chip giant hadn’t received any official word of restrictions and reiterated denials of any military link. The company offers chips and services “solely for civilian and commercial end-users and end-uses,” according to the representative.
The semiconductor producer is just the second top-tier company added to the entity list after Huawei. While the effect of the ban won’t be clear until the Commerce Department decides who (if anyone) gets a license, it could represent a significant blow to Chinese tech as a whole. SMIC may have to turn to non-US technology whenever it wants to upgrade its manufacturing or maintain hardware, and there’s no guarantee it will find what it needs. It could find itself trailing behind rivals that have access to a wider range of equipment.
This could have a knock-on effect for companies that depend on SMIC. Huawei needs SMIC to make some of the Kirin chips in its phones, especially after losing access to partners like TSMC — it might have further trouble if SMIC can’t meet demands under the new restrictions. It won’t be surprising if the Chinese government retaliates with comparable restrictions on American companies.
Am I having a nightmare or did Amazon really announce a security camera that flies around inside your house? I can’t quite get over this being a thing that exists, but with the way things go, we’ll probably have a roundup of twenty similar devices in a couple of months.
If you prefer your flights relaxing instead of unsettling, then Flight Simulator is still your best bet. Before you flip through the key stories from Friday and earlier this week, read Devindra Hardawar’s interview that explores how cloud servers are helping make it a “living game.”
— Richard
Our Apple Watch SE review and Microsoft buys Bethesda
iPadOS 14 is missing the iOS App Gallery, but the Pencil experience is much better now.
Apple’s tablet hasn’t changed much from last year, except that it charges and runs a bit faster. The improvements are small but notable, and combine with tweaks in iPadOS 14 to make for an extremely flexible, powerful device, even if the base model’s 32GB of storage is looking a little small these days. Continue reading.
And a 10,000mAh battery with a kickstand for $30.
The Apple Watch Series 6 saw its first discount at Amazon (only on a few models, but it’s better than nothing) and the 512GB model of the latest 13-inch MacBook Pro dropped by $200. Amazon’s also running a good sale on its newest Fire HD tablets, shaving up to $40 off their normal prices.
Here are all the best deals from the week that you can still snag today, and remember to follow @EngadgetDeals on Twitter for more updates. Continue reading.
The new Apple Watch says my lungs may be sick. Or perfect. It can’t decide.Geoffrey A. Fowler, The Washington PostOne of the key features of the new Apple Watch Series 6 is the built-in oximeter. In theory, the component should give you an idea of yo…
Then Elon Musk opened up pre-orders for the triple-motor ‘Plaid’ Model S sedan, and said it would do a quarter mile in less than 9.9 seconds when it goes on sale next year. Just to keep pushing the bar, CNET Roadshow points out a tweet from Lucid showing an Air run that took just 9.245 seconds, well under the record for a production car. It’s an impressive time to be sure, but as they note, while the car shown is wearing street-legal Pirelli Trofeo tires, it is a triple-motor development mule without a full interior. We’ll have to wait and see what more realistic versions of the sedan are more capable of, but according to Motor Trend, Lucid has already prepared a version that might go faster.
The Edge team is also continuing to work on reducing the amount of memory and CPU power the browser needs. The Windows 10 May 2020 Update, for instance, reduces the browser’s memory usage by up to 27 percent based on the tech giant’s internal tests. Finally, Microsoft shrunk Edge’s size by half over the past year so that it doesn’t take up too much storage on your device.
Microsoft’s Edge browser recently overtook Firefox as the most popular Chrome alternative, according to NetMarketshare stats. Chrome still has the lion’s share of the market with over a 70 percent share, and Firefox isn’t that far behind, but Microsoft’s contender has been slowly gaining popularity.
If you have to see the Ring Always Home Cam in action to believe that Amazon made a flying security drone for your house, then check out the video of its hardware event. The live stream wasn’t available publicly yesterday, but now you can click through the highlights on a YouTube stream (or just check out a 30-second ad for the Ring drone that’s also embedded below).
NBC’s Peacock streaming service will start streaming its entire back catalog of Saturday Night Live episodes on October 1st, according to DeadlineandVariety. Once all 45 seasons of SNL make their way to Peacock, it will mark the first time the entire run of the sketch comedy show has been available to watch in one place.
Peacock currently has some of Saturday Night Live’s most famous episodes, particularly ones involving notable past guests like Chris Farley. You can also watch seasons one through five and seasons 30 through to 45 on Hulu, but that means you miss on the show’s 80s run with Eddie Murphy.
Let’s face it, when you start building out a fleet of synths, cable management can quickly become an issue, with all those wires connecting everything creating an inescapable rat’s nest. Enter Roland with its new WM-1 Wireless MIDI adapter. It’s a combination 2.4GHz and Bluetooth dongle you plug into your MIDI-compatible instrument that allows it to wirelessly communicate with other MIDI hardware (provided that instrument has a wireless connection as well) and your computer or iOS device. No wires needed. Besides note data, the WM-1 can transfer MIDI sync for tempo, effects, LFOs and loops.
If you have access to a macOS computer or an iOS device, you can connect to the WM-1 over Bluetooth. With Windows computers, you’ll need to buy the $80 WM-1D USB dongle. You can also use the WM-1D to ensure you get the lowest possible latency when playing your instruments. Using the included Fast mode, Roland claims there is a 3ms delay transferring data between devices. That’s better than the internal speed of many hardware devices, according to the company.