This excellent content from the Hackaday writing crew highlights recurring topics and popular series like Linux-Fu, 3D-Printering, Hackaday Links, This Week in Security, Inputs of Interest, Profiles in Science, Retrotechtacular, Ask Hackaday, Teardowns, Reviews, and many more.
Git released an update on Tuesday, fixing an issue that could result in leaking credentials. The vulnerability was in how Git handles an HTTP URL containing a newline. Looking at the commits in 2.26.1, we can find an example of an attack: url = "https://one.example.com?%0ahost=two.example.com/foo.git"
For those addicted to automotive thrills, there’s always an underlying lust for more power. For those chasing a bigger number, forced induction is one of the most effective ways to achieve it. In addition to more grunt, you get a whole bunch of fun new noises, too. For those with a naturally aspirated car, here’s how you go about converting to forced induction.
Superchargers and Turbos
When we talk about forced induction, we’re talking about forcing more air into the engine under pressure. With more air available, it’s possible to fully combust more fuel, creating more power. The two most common ways of doing this are supercharging and turbocharging. We’ll be using the common automotive vernacular here, so those eager to bicker about terminology from the early 20th century aircraft industry best do it in the comments. Continue reading “How To Get Into Cars: Forced Induction”→
Under the current Administration, NASA has been tasked with returning American astronauts to the Moon as quickly as possible. The Artemis program would launch a crewed mission to our nearest celestial neighbor as soon as 2024, and establish a system for sustainable exploration and habitation by 2028. It’s an extremely aggressive timeline, to put it mildly.
To have any chance of meeting these goals, NASA will have to enlist the help of not only its international partners, but private industry. There simply isn’t enough time for the agency to design, build, and test all of the hardware that will eventually be required for any sort of sustained presence on or around the Moon. By awarding a series of contracts, NASA plans to offload some of the logistical components of the Artemis program to qualified companies and agencies.
For anyone who’s been following the New Space race these last few years, it should come as no surprise to hear that SpaceX has already been awarded one of these lucrative logistics contracts. They’ve been selected as the first commercial provider for cargo deliveries to Gateway, a small space station that NASA intendeds to operate in lunar orbit. Considering SpaceX already has a contract to resupply the International Space Station, they were the ideal candidate to offer similar services for a future lunar outpost.
But that certainly doesn’t mean it will be easy. The so-called “Gateway Logistics Services” contract stipulates that providers must be able to deliver at least 3,400 kilograms (7,500 pounds) of pressurized cargo and 1,000 kilograms (2,200 pounds) of unpressurized cargo to lunar orbit. That’s beyond the capabilities of SpaceX’s Dragon spacecraft, which was only designed to service low Earth orbit.
To complete this new mission, the company is proposing a new vehicle they’re calling the Dragon XL that would ride to orbit on the Falcon Heavy booster. But even for this New Space darling, there’s not a lot of time to design, test, and build a brand-new spacecraft. To get the Dragon XL flying as quickly as possible, SpaceX is going to need to strip the craft down to the bare minimum.
Many of the SDR projects we see use a cheap USB dongle. They are great, but sometimes you want more and — especially — sometimes you want to transmit. The Analog Devices ADALM-Pluto SDR is easily available for $200 and sometimes as low as $100 and it both transmits and receives using an Analog AD9363 and a Zynq FPGA. Although you normally use the device to pipe IQ signals to a host computer, you can run SDR applications on the device itself. That requires you to dig into the Zynq tools, which is fun but a topic for another time. In this post, I’m going to show you how you can use GNU Radio to make a simple Morse code beacon in the 2m ham band.
I’ve had one on my bench for quite a while and I’ve played with it a bit. There are several ways to use it with GNU Radio and it seems to work very well. You have to hack it to get the frequency range down a bit. Sure, it might not be “to spec” once you broaden the frequency range, but it seems to work fine. Instead of working from 325 MHz to 3,800 MHz with a 20 MHz bandwidth, the hacked device transceives 70 MHz to 6,000 MHz with 56 MHz bandwidth. It is a simple hack you only have to do once. It tells the device that it has a slightly better chip onboard and our guess is the chips are the same but sorted by performance. So while the specs might be a little off, you probably won’t notice.
The printed circuit design process is pretty unique among manufacturing processes. Chances are pretty good that except for possibly a breadboard prototype, the circuit that sits before you after coming back from assembly has only ever existed in EDA software or perhaps a circuit simulator. Sure, it’s supposed to work, but will it?
You can — and should — do some power-off testing of new boards, but at some point you’re going to have to flip the switch and see what happens. The PCB bring-up process needs to be approached carefully, lest debugging any problems that crop up become more difficult than need be. Mihir and Liam from inspectAR will discuss the bring-up process in depth, offering tips and tricks to make things go as smoothly as possible, as well as demonstrating how the inspectAR platform can fit into that process, especially with teams that are distributed across remote sites. If your board releases the Magic Smoke, you’ll want to know if it’s your design or an assembly issue, and an organized bring-up plan can be a big help.
Click that speech bubble to the right, and you’ll be taken directly to the Hack Chat group on Hackaday.io. You don’t have to wait until Wednesday; join whenever you want and you can see what the community is talking about.
In the recent frenzy of stocking up with provisions as the populace prepare for their COVID-19 lockdown, there have been some widely-publicised examples of products that have become scarce commodities. Toilet paper, pasta, rice, tinned vegetables, and long-life milk are the ones that come to mind, but there’s another one that’s a little unexpected.
As everyone dusts off the breadmaker that’s lain unused for years since that time a loaf came out like a housebrick, or contemplates three months without beer and rediscovers their inner home brewer, it seems yeast can’t be had for love nor money. No matter, because the world is full of yeasts and thus social media is full of guides for capturing your own from dried fruit, or from the natural environment. A few days tending a pot of flour and water, taking away bacterial cultures and nurturing the one you want, and you can defy the shortage and have as much yeast as you need.
Anyone who worked in the tech field and lived through the Y2K bug era will no doubt recall it as a time seasoned with a confusing mix of fear and optimism and tempered with a healthy dose of panic, as companies rushed to validate that systems would pass the rollover of the millennium without crashing, and to remediate systems that would. The era could well have been called “the COBOL programmers full-employment bug,” as the coders who had built these legacy systems were pulled out of retirement to fix them. Twenty years on and a different bug — the one that causes COVID-19 — is having a similarly stimulative effect on the COBOL programmer market. New Jersey is one state seeking COBOL coders, to deal with the crush of unemployment insurance claims, which are killing the 40-year-old mainframe systems the state’s programs run on. Interestingly, Governor Phil Murphy has only put out a call for volunteers, and will apparently not compensate COBOL coders for their time. I mean, I know people are bored at home and all, but good luck with that.
In another throwback to an earlier time, “The Worm” is back. NASA has decided to revive its “worm” logo, the simple block letter logo that replaced the 50s-era “Meatball” logo, the one with the red chevron bracketing a starfield with an orbiting satellite. NASA switched to the worm, named for the sinuous shape of the letters and which honestly looks like a graphic design student’s last-minute homework assignment, in the 1970s, keeping it in service through the early 1990s when the meatball was favored again. Now it looks like both logos will see service as NASA prepares to return Americans to space on their own launch vehicles.
Looking for a little help advancing the state of your pandemic-related project? A lot of manufacturers are trying to help out as best they can, and many are offering freebies to keep you in the game. Aisler, for one, is offering free PCBs and stencils for COVID-19 prototypes. It looks like their rules are pretty liberal; any free and open-source project that can help with the pandemic in any way qualifies. Hats off to Aisler for doing their part.
And finally, history appears to have been made this week in the amateur radio world with the first direct transatlantic contact on the 70-cm band was made. It seems strange to think that it would take 120 years since transatlantic radio became reduced to practice by the likes of Marconi for this accomplishment to occur, but the 70-cm band is usually limited to line of sight, and transatlantic contacts at 430 MHz are usually done using a satellite as a relay. The contact was between stations FG8OJ on Guadaloupe Island in the Caribbean — who was involved in an earlier, similar record on the 2-meter band — and D4VHF on the Cape Verde Islands off the coast of Africa, and used the digital mode FT8. The 3,867-km contact was likely due to tropospheric ducting, where layers in the atmosphere form a refractive tunnel that can carry VHF and UHF signals much, much further than they usually go. While we’d love to see that record stretched a little more on each end, to make a truly transcontinental contact, it’s still quite an accomplishment, and we congratulate the hams involved.