USB drives are incredibly useful, both storing files for transport between different computers and for creating bootable drives that let us use or install other operating systems on our computers. While online file storage systems like Dropbox and Google Drive have taken over a large percentage of the former task from USB drives, they have not been able to act as bootable media, ensuring that each of us have a few jump drives lying around. That might not be the case anymore, though, as this guide is the first we know of to be able to use Google Drive to boot to a Linux system.

Unlike the tried-and-true jump drive methods, however, this process is not straightforward at all. It relies on two keys, the first of which is FUSE which allows a filesystem to be created in userspace. The second is exploiting a step in boot process of Linux systems where the kernel unpacks a temporary filesystem, called initramfs, in order to load the real filesystem. Normally a user doesn’t interact much with this step, but that doesn’t mean it’s impossible. A tool called dracut allows using an existing Linux installation to build a custom initramfs and in this case, the custom initramfs is built to include the proper support for both networking and FUSE.

The proof of concept in this demonstration originally ran in a container, using an existing project called google-drive-ocamlfuse to interact with Google Drive itself. From there, after sorting out some issues with root access, networking, malfunctioning symlinks, and various timeouts on the (perhaps predictably) slow system, the whole contraption was moved over to a laptop so it could be tested on real hardware. Everything runs, and although the original creator of this behemoth admits it is a bit “silly” they note that there may be some real-world use cases for something like this. We still won’t expect everyone to throw out their jump drives anytime soon, though. If you’re not feeling like your Linux skills are up to the challenge of something like this, we’d recommend you start with our own [Al Williams]’s Linux Fu series.

Most 3D printer filament soaks up water from the air, and when it does, the water passing through the extruder nozzle can expand, bubble, and pop, causing all kinds of mayhem and unwanted effects in the print. This is why reels come vacuum sealed. Some people 3D print so much that they consume a full roll before it can soak up water and start to display these effects. Others live in dry climates and don’t have to worry about humidity. But the rest of us require a solution. To date, that solution has been filament driers, which are heated elements in a small reel-sized box, or for the adventurous an oven put at a very specific temperature until the reel melts and coats the inside of the oven. The downside to this method is that it’s a broad stroke that takes many hours to accomplish, and it’s inefficient because one may not use the whole roll before it gets soaked again.

In much the same way that instant water heaters exist to eliminate the need for a water heater, [3DPI67] has a solution to this problem, and it involves passing the filament through a small chamber with a heating element and fan circulating air. The length of the chamber is important, as is the printing speed, since the filament needs to have enough time in the improvised sauna to sweat out all its water weight. The temperature of the chamber can’t get above the glass transition temperature of the filament, either, which is another limiting factor for the dryer. [3DPI67] wrote up a small article on his improvised instant filament heater in addition to the video.

So far, only TPU has been tested with this method, but it looks promising. Some have suggested a larger chamber with loops of filament so that more can be exposed for longer. There’s lots of room for innovation, and it seems some math might be in order to determine the limits and optimizations of this method, but we’re excited to see the results.

youtube.com/embed/9ldRN2B4iJY?…

Una significativa violazione dei dati ha coinvolto il Ministero della Giustizia e dei Diritti Umani (Kemenkumham) in Indonesia.

Secondo un post su un forum di hacker, un attore di minacce sotto lo pseudonimo “Guzmanloeraxxx” ha presumibilmente divulgato le credenziali di accesso email dei dipendenti di Kemenkumham. Questa violazione se confermata comporterebbe seri rischi per la sicurezza nazionale e la fiducia pubblica.

Attualmente, non siamo in grado di confermare con precisione l’accuratezza delle informazioni riportate, poiché non è stato rilasciato alcun comunicato stampa ufficiale sul sito web riguardante l’incidente.

Kemenkumham

Kemenkumham, abbreviazione di Kementerian Hukum dan Hak Asasi Manusia, è il Ministero della Giustizia e dei Diritti Umani della Repubblica dell’Indonesia. Questo ministero è responsabile della gestione degli affari legali e dei diritti umani nel paese.

Dettagli della possibile Violazione

Entità Coinvolta:

• Ministero della Giustizia e dei Diritti Umani (Kemenkumham)

Dati Compromessi:

• Credenziali di accesso email, inclusi nomi utente e password

Rischi Potenziali:

• Accesso non autorizzato a comunicazioni sensibili
• Manipolazione dei dati
• Furto di identità
• Potenziale abuso per attività dannose di vario tipo

L’Impatto

I dati divulgati consentono l’accesso agli account email ufficiali utilizzati dai dipendenti di Kemenkumham, potenzialmente compromettendo informazioni sensibili del governo. Individui non autorizzati potrebbero sfruttare queste informazioni per accedere a comunicazioni riservate e manipolare dati, portando al furto di identità e altre attività dannose.

La violazione evidenzia gravi vulnerabilità di sicurezza nei sistemi del ministero, sottolineando la necessità di misure immediate e robuste di cybersicurezza. I rischi associati a questa violazione sono ampi, incluso il potenziale per gli attaccanti di accedere a comunicazioni interne e ad altri dati sensibili, che potrebbero impattare la sicurezza nazionale e minare la fiducia pubblica nelle istituzioni governative.

Cosa Significa

Le implicazioni di questa violazione sono significative. L’accesso non autorizzato agli account email ufficiali potrebbe portare a:

• Fughe di informazioni sensibili
• Potenziale spionaggio
• Manipolazione dei dati governativi
• Furto di identità che coinvolge dipendenti governativi e persone associate

In risposta a questa violazione, è cruciale che Kemenkumham conduca un’indagine approfondita e implementi protocolli di sicurezza stringenti per prevenire futuri incidenti. Le azioni immediate dovrebbero includere il cambiamento di tutte le password compromesse, il miglioramento delle misure di sicurezza delle email e il monitoraggio di eventuali tentativi di accesso non autorizzati.

Questo incidente se confermato mostra ancora una volta ll’importanza della cybersicurezza nella protezione delle informazioni sensibili del governo e nel mantenimento dell’integrità delle istituzioni pubbliche.

Come nostra consuetudine, lasciamo sempre spazio ad una dichiarazione da parte dell’azienda qualora voglia darci degli aggiornamenti sulla vicenda. Saremo lieti di pubblicare tali informazioni con uno specifico articolo dando risalto alla questione.

RHC Dark Lab monitorerà l’evoluzione della vicenda in modo da pubblicare ulteriori news sul blog, qualora ci fossero novità sostanziali. Qualora ci siano persone informate sui fatti che volessero fornire informazioni in modo anonimo possono utilizzare la mail crittografata del whistleblower.

L'articolo Possibile compromissione di Dati: Credenziali appartenenti a Kemenkumham sul darkweb proviene da il blog della sicurezza informatica.

It’s official: [Engineer Bo] wins the internet with a video titled “Finding NEMA 17,” wherein he builds a dynamometer to find the best stepper motor in the popular NEMA 17 frame size.

Like a lot of subjective questions, the only correct answer to which stepper is best is, “It depends,” and [Bo] certainly has that in mind while gathering the data needed to construct torque-speed curves for five samples of NEMA 17 motors using his homebrew dyno. The dyno itself is pretty cool, with a bicycle disc brake to provide drag, a load cell to measure braking force, and an optical encoder to measure the rotation of the motor under test. The selected motors represent a cross-section of what’s commonly available today, some of which appear in big-name 3D printers and other common applications.

[Bo] tested each motor with two different drivers: the TMC2209 silent driver to start with, and because he released the Magic Smoke from those, the higher current TB6600 module. The difference between the two drivers was striking, with lower torque and top speeds for the same settings on each motor using the TB6600, as well as more variability in the data. Motors did better across the board with the TBC6600 at 24 volts, showing improved torque at higher speeds, and slightly higher top speeds. He also tested the effect of microstepping on torque using the TBC6600 and found that using full steps resulted in higher torque across a greater speed range.

At the end of the day, it seems as if these tests say more about the driver than they do about any of the motors tested. Perhaps the lesson here is to match the motor to the driver in light of what the application will be. Regardless, it’s a nice piece of work, and we really appreciate the dyno design to boot — reminds us of a scaled-down version of the one [Jeremey Fielding] demonstrated a few years back.

youtube.com/embed/MNTuMiNC2TU?…

The Parkside range of tools as sold in European Lidl stores may be reasonably priced, but it contains some products of far better quality than their modest cost would suggest. This means that Parkside hacking has become as much of a cottage industry as IKEA hacking, and they’re a firm favorite for modifications. [Gabriel-LG] has taken a Parkside robot mower, and converted it from a relatively mundane device to a fully-connected smart robot, with the aid of an ESP32.

The hardware is surprisingly simple, as all that’s really needed is a stop/go command. This can be readily found by hooking up to the input from the mower’s rain sensor, allowing the ESP to control its operation. Then there’s an accelerometer to allow it to count motion, and a hookup tot he battery to measure voltage. The firmware uses ESPHome, resulting in a mower now connected to home automation.

This isn’t the first time we’ve shown you someone upgrading the smarts on robot mover, and of course we’ve also taken a tour through the history of lawn mowers in general.

Eccoci qui. Dopo aver trascorso gli ultimi anni leggendo tra il fediverso e il web alternativo, ho deciso di creare il mio posto dove le persone orientate alla libertà possano discutere di libertà nell'informatica e nella società. Lo scopo generale è ricreare le vibrazioni familiari dell'era BBS mettendo insieme strumenti vecchi e moderni, da IRC a Mastodon. Ecco dove spiego tutto:

- [ENG] dmi.unict.it/nfarceri/articles…
- [ITA] dmi.unict.it/nfarceri/articles…

Benvenuti a casa... vostra!

Questo è il primo articolo di questo sito, dove vengono introdotti gli scopi del sito stesso. In sintesi, il sito ha lo scopo di ricreare il feeling familiare e comunitario delle BBS degli anni '80 e '90 aggregando insieme più strumenti, vecchi e mod…

^{www.dmi.unict.it}

At the request of Pirate Party MEP Patrick Breyer, EU Internal Market Commissioner Breton has commented on manufacturers who equip their products with “kill switches”. This question was prompted by a recent case in which the Polish train manufacturer NewAg was found to have installed “kill switches” in several electric multiple units, which switch off the train’s power supply and compressors under certain conditions (location or operating time). Among other things, the manufacturer implemented the switch-off function to prevent the trains from being repaired by competitors and also to prevent the train software from being analysed. In his response, EU Commissioner Breton admits that existing or planned EU rules on the right to repair are largely limited to the protection of consumers and do not apply to businesses.

Patrick Breyer comments:

“The practice by some manufacturers to prevent independent companies from repairing and servicing products is unacceptable. The EU should put clear rules in place to prevent such abuses and protect the rights of users, as well as the competitiveness of independent repair services. The right to repair should also apply to business customers.

However, a mere right to repair falls short of what is needed in the digital era. Users must be given full control over the technology they use in their daily lives. We need a right to modify, customise and improve our legally acquired devices. The fact that copyright law currently prohibits this is disempowering and invites abuse, as the Polish case shows.”

A similar problem is also observed with computer games, where manufacturers make popular games unusable at will. In collaboration with the gamer initiative “Stop killing games”, the pirate party is calling for cultural protection of video games.

patrick-breyer.de/en/stopkilli…