In theory, writing a Linux device driver shouldn’t be that hard, but it is harder than it looks. However, using libusb, you can easily deal with USB devices from user space, which, for many purposes, is fine. [Crescentrose] didn’t know anything about writing user-space USB drivers until they wrote one and documented it for us. Oh, the code is in Rust, for which there aren’t as many examples.

The device in question was a USB hub with some extra lights and gadgets. So the real issue, it seems to us, wasn’t the code, but figuring out the protocol and the USB stack. The post covers that, too, explaining configurations, interfaces, and endpoints.

There are other ancillary topics, too, like setting up udev. This lets you load things when a USB device (or something else) plugs in.

Of course, you came for the main code. The Rust program is fairly straightforward once you have the preliminaries out of the way. The libusb library helps a lot. By the end, the code kicks off some threads, handles interrupts, and does other device-driver-like things.

So if you like Rust and you ever thought about a user space device driver for a USB device, this is your chance to see it done. It didn’t take years. However, you can do a lot in user space.

hackaday.com/2025/06/26/rust-d…

It’s about time! Or maybe it’s about time’s reciprocal: frequency. Whichever way you see it, Hackaday is pleased to announce, just this very second, the 2025 One Hertz Challenge over on Hackaday.io. If you’ve got a device that does something once per second, we’ve got the contest for you. And don’t delay, because the top three winners will each receive a $150 gift certificate from this contest’s sponsor: DigiKey.

What will you do once per second? And how will you do it? Therein lies the contest! We brainstormed up a few honorable mention categories to get your creative juices flowing.

• Timelords: How precisely can you get that heartbeat? This category is for those who prefer to see a lot of zeroes after the decimal point.
• Ridiculous: This category is for the least likely thing to do once per second. Accuracy is great, but absurdity is king here. Have Rube Goldberg dreams? Now you get to live them out.
• Clockwork: It’s hard to mention time without thinking of timepieces. This category is for the clockmakers among you. If your clock ticks at a rate of one hertz, and you’re willing to show us the mechanism, you’re in.
• Could Have Used a 555: We knew you were going to say it anyway, so we made it an honorable mention category. If your One Hertz project gets its timing from the venerable triple-five, it belongs here.

We love contests with silly constraints, because you all tend to rise to the challenge. At the same time, the door is wide open to your creativity. To enter, all you have to do is document your project over on Hackaday.io and pull down the “Contests” tab to One Hertz to enter. New projects are awesome, but if you’ve got an oldie-but-goodie, you can enter it as well. (Heck, maybe use this contest as your inspiration to spruce it up a bit?)

Time waits for no one, and you have until August 19th at 9:00 AM Pacific time to get your entry in. We can’t wait to see what you come up with.

hackaday.com/2025/06/26/announ…

La Pirate Academy online, organizzata dall’eurodeputata Markéta Gregorová e dal gruppo politico Verdi/ALE, si terrà nell’autunno del 2025. David, dicci, cosa tratterà esattamente il corso? Si articolerà in cinque sessioni online interattive, più un incontro in diretta a Bruxelles, presso il Parlamento europeo, per i migliori partecipanti. Il corso ti preparerà a lavorare come consulente…

Source

Here’s a fun build. Over on their YouTube channel our hacker [Atasoy] shows us how to make a custom floral keyboard keycap using resin.

We begin by using an existing keycap as a pattern to make a mold. We plug the keycap with all-purpose adhesive paste so that we can attach it to a small sheet of Plexiglas, which ensures the floor of our mold is flat. Then a side frame is fashioned from 100 micron thick acetate which is held together by sticky tape. Hot glue is used to secure the acetate side frame to the Plexiglas floor, keeping the keycap centered. RTV2 molding silicone is used to make the keycap mold. After 24 hours the silicone mold is ready.

Then we go through a similar process to make the mold for the back of the keycap. Modeling clay is pushed into the back of the keycap. Then silicone is carefully pushed into the keycap, and 24 hours later the back silicone mold is also ready.

The back mold is then glued to a fresh sheet of Plexiglas and cut to shape with a craft knife. Holes are drilled into the Plexiglas. A mix of artificial grass and UV resin is made to create the floor. Then small dried flowers are cut down to size for placement in the top of the keycap. Throughout the process UV light is used to cure the UV resin as we go along.

Finally we are ready to prepare and pour our epoxy resin, using our two molds. Once the mold sets our new keycap is cut out with a utility knife, then sanded and polished, before being plugged into its keyboard. This was a very labor intensive keycap, but it’s a beautiful result.

If you’re interested in making things with UV resin, we’ve covered that here before. Check out 3D Printering: Print Smoothing Tests With UV Resin and UV Resin Perfects 3D Print, But Not How You Think. Or if you’re interested in epoxy resin, we’ve covered that too! See Epoxy Resin Night Light Is An Amazing Ocean-Themed Build and Degassing Epoxy Resin On The (Very) Cheap.

Thanks to [George Graves] for sending us this one via the tipsline!

youtube.com/embed/07K_nX6TEoE?…

hackaday.com/2025/06/26/how-to…

Gli sviluppatori di WinRAR hanno risolto una vulnerabilità relativa all’override della directory, che ha ricevuto l’identificatore CVE-2025-6218. In determinate circostanze, questo bug permetteva l’esecuzione di malware dopo l’estrazione dell’archivio.

La vulnerabilità ha ricevuto un punteggio di 7,8 punti sulla scala CVSS ed è stata scoperta da un ricercatore con il nickname whs3-detonator, che ha segnalato il problema attraverso Zero Day Initiative all’inizio di giugno 2025. Il problema riguarda solo la versione Windows di WinRAR, a partire dalla versione 7.11 e successive, mentre la correzione è stata introdotta nella versione WinRAR 7.12 beta 1, uscita questa settimana.

“Quando si estrae un file nelle vecchie versioni di WinRAR, RAR per Windows, UnRAR e UnRAR.dll, incluso il codice sorgente UnRAR portatile, è possibile utilizzare il percorso specificato in un archivio appositamente predisposto, anziché il percorso specificato dall’utente”, spiegano gli sviluppatori.

In altre parole, un archivio dannoso può contenere file con un percorso relativo modificato, che costringe WinRAR a estrarli in posizioni potenzialmente pericolose, inclusi directory di sistema e cartelle di avvio automatico.

Se il contenuto di tale archivio è dannoso, i file estratti possono essere eseguiti automaticamente, provocando l’esecuzione di codice pericoloso al successivo accesso dell’utente a Windows. Anche se tali programmi vengono eseguiti con diritti di livello utente e non hanno privilegi di amministratore o SYSTEM, sono comunque in grado di rubare dati sensibili, inclusi cookie del browser e password salvate, stabilirsi nel sistema della vittima o fornire accesso remoto ai propri operatori.

Oltre a CVE-2025-6218, nella versione WinRAR 7.12 beta 1 è stata anche risolta una problematica di iniezione HTML, che si verificava durante la generazione di rapporti. Questo bug è stato segnalato dal ricercatore di sicurezza Marcin Bobryk (Marcin Bobryk). Egli spiega che i nomi dei file di archivio contenenti potevano essere incorporati nel rapporto HTML come tag HTML non elaborati. Di conseguenza, ciò poteva portare a iniezioni HTML e JS se i rapporti venivano aperti in un browser.

L'articolo Attenzione! WinRAR: Vulnerabilità Critica che Potrebbe Eseguire Malware proviene da il blog della sicurezza informatica.