The White House’s proposed budget for 2020 is out, and with it comes cuts to NASA. The most important item of note in the proposed budget is a delay of the Space Launch System, the SLS, a super-heavy lifting launch vehicle designed for single use. The proposed delay would defer work on the enhanced version of the SLS, the Block 1B with the Exploration Upper Stage.
The current plans for the Space Launch System include a flight using NASA’s Orion spacecraft in June 2020 for a flight around the moon. This uncrewed flight, Exploration Mission 1, or EM-1, would use the SLS Block 1 Crew rocket. A later flight, EM-2, would fly a crewed Orion capsule around the moon in 2022. A third proposed flight in 2023 would send the Europa Clipper to Jupiter. The proposed 2020 budget puts these flights in jeopardy.
Continue reading “Proposed NASA Budget Signals Changes To Space Launch System”
The wheels of government move slowly, far slower than the pace at which modern technology is evolving. So it’s not uncommon for laws and regulations to significantly lag behind the technology they’re aimed at reigning in. This can lead to something of a “Wild West” situation, which could either be seen as a good or bad thing depending on what side of the fence you’re on.
In the United States, it’s fair to say that we’ve officially moved past the “Wild West” stage when it comes to drone regulations. Which is not to say that remotely controlled (RC) aircraft were unregulated previously, but that the rules which governed them simply couldn’t keep up with the rapid evolution of the technology we’ve seen over the last few years. The previous FAA regulations for remotely operated aircraft were written in an era where RC flights were lower and slower, and long before remote video technology moved the operator out of the line of sight of their craft.
To address the spike in not only the capability of RC aircraft but their popularity, the Federal Aviation Administration was finally given the authority to oversee what are officially known as Unmanned Aerial Systems (UAS) with the repeal of Section 336 in the FAA Reauthorization Act of 2018. Section 336, known as the “Special Rule for Model Aircraft” was previously put in place to ensure the FAA’s authority was limited to “real” aircraft, and that small hobby RC aircraft would not be subject to the same scrutiny as their full-size counterparts. With Section 336 gone, one could interpret the new FAA directives as holding manned and unmanned aircraft and their operators to the same standards; an unreasonable position that many in the hobby strongly rejected.
At the time, the FAA argued that the repealing Section 336 would allow them to create new UAS regulations from a position of strength. In other words, start with harsh limits and regulations, and begin to whittle them down until a balance is found that everyone is happy with. U.S. Secretary of Transportation Elaine L. Chao has revealed the first of these refined rules are being worked on, and while they aren’t yet official, it seems like the FAA is keeping to their word of trying to find a reasonable middle ground for hobby fliers.
Continue reading “FAA Proposes Refined Drone Regulations”
On November 10th, [Theodore Rappaport] sent the FCC an ex parte filing regarding a proposed rule change that would remove the limit on baud rate of high frequency (HF) digital transmissions. According to [Rappaport] there are already encoded messages that can’t be read on the ham radio airwaves and this would make the problem worse.
[Rappaport] is a professor at NYU and the founding director of NYU Wireless. His concern seems to relate mostly to SCS who have some proprietary schemes for compressing PACTOR as part of Winlink — used in some cases to send e-mail from onboard ships.
Continue reading “FCC Gets Complaint: Proposed Ham Radio Rules Hurt National Security”
It sometimes seems as though barely a week can go by without yet another major software-related hardware vulnerability story. As manufacturers grapple with the demands of no longer building simple appliances but instead supplying them containing software that may expose itself to the world over the Internet, we see devices shipped with insecure firmware and little care for its support or updating after the sale.
The French government have a proposal to address this problem that may be of interest to our community, to make manufacturers liable for the security of a product while it is on the market, and with the possibility of requiring its software to be made open-source at end-of-life. In the first instance it can only be a good thing for device security to be put at the top of a manufacturer’s agenda, and in the second the ready availability of source code would present reverse engineers with a bonanza.
It’s worth making the point that this is a strategy document, what it contains are only proposals and not laws. As a 166 page French-language PDF it’s a long read for any Francophones among you and contains many other aspects of the French take on cybersecurity. But it’s important, because it shows the likely direction that France intends to take on this issue within the EU. At an EU level this could then represent a globally significant move that would affect products sold far and wide.
What do we expect to happen in reality though? It would be nice to think that security holes in consumer devices would be neutralised overnight and then we’d have source code for a load of devices, but we’d reluctantly have to say we’ll believe it when we see it. It is more likely that manufacturers will fight it tooth and nail, and given some recent stories about devices being bricked by software updates at the end of support we could even see many of them willingly consigning their products to the e-waste bins rather than complying. We’d love to be proven wrong, but perhaps we’re too used to such stories. Either way this will be an interesting story to watch, and we’ll keep you posted.
Merci beaucoup [Sebastien] for the invaluable French-language help.
French flag: Wox-globe-trotter [Public domain].
We’ve all seen the stories about IoT devices with laughably poor security. Both within our community as fresh vulnerabilities are exposed and ridiculed, and more recently in the wider world as stories of easily compromised baby monitors have surfaced in mass media outlets. It’s a problem with its roots in IoT device manufacturers treating their products as appliances rather than software, and in a drive to produce them at the lowest possible price.
The Australian government have announced that IoT security is now firmly in their sights, announcing a possible certification scheme with a logo that manufacturers would be able to use if their products meet a set of requirements. Such basic security features as changeable, non-guessable, and non-default passwords are being mentioned, though we’re guessing that would also include a requirement not to expose ports to the wider Internet. Most importantly it is said to include a requirement for software updates to fix known vulnerabilities. It is reported that they are also in talks with other countries to harmonize some of these standards internationally.
It is difficult to see how any government could enforce such a scheme by technical means such as disallowing Internet connection to non-compliant devices, and if that was what was being proposed it would certainly cause us some significant worry. Therefore it’s likely that this will be a consumer certification scheme similar to for example the safety standards for toys, administered as devices are imported and through enforcement of trading standards legislation. The tone in which it’s being sold to the public is one of “Think of the children” in terms of compromised baby monitors, but as long-time followers of Hackaday will know, that’s only a small part of the wider problem.
Thanks [Bill Smith] for the tip.
Baby monitor picture: Binatoneglobal [CC BY-SA 3.0].
[Sefi Attias] just sent us a heartwarming little video of how he proposed to his girlfriend [Tania] — using a little help from technology and other makers.
As a maker, [Sefi] was always building things which impressed [Tania], so he thought it was only fitting to make the proposal a one-of-a-kind maker experience.
He started by designing the engagement ring himself, to be 3D printed. It’s an amazingly complex little thing made up of the repeating words of the quote “I will betroth you to me forever”. It was almost too complex in order to print — but they managed to do it in wax, which allowed them to create a mold and then cast the final part in white gold. Once complete, they set a diamond in place to cap it all off.
The second step was the proposal, which was made possible using a quadrotor, a strip of RGB LEDs, and a long camera exposure. To show it off in real-time to [Tania] they setup a projector and screen on the side of the street, providing a surreal window into the park behind them. It was all made possible with the help from over 20 people from the XLN Makerspace and SkyLens (the quadrotor people).
Oh yeah, and she said yes.
Continue reading “How A Maker Proposes”
Thinking long and hard about how to propose to his girlfriend, [Ed] hit upon a great idea: use an arc reactor as the ring box, with enough LED lights to outshine all but their love, and servos to present the ring and tug at the heartstrings.
[Ed] set about giving his now-fiancé from his arc reactor heart by building a simple circular arrangement of adafruit RGB LED strip and an Arduino. There are two modes for this arc reactor: a light up mode that simply looks awesome, and a ‘ring mode’ that uses two servos to open the front cover and bring the engagement ring into view.
After [Ed]’s fiancé said yes, the cover in the center of the arc reactor closes for its continued use as a desk ornament. You can check out [Ed]’s proposal contraption in action after the break.
Continue reading “Man Proposes To Girlfriend With An Arc Reactor”