Cyber Act Forum, ottima riuscita per la quarta edizione della kermesse dedicata al tema della cybersecurity che si svolge a Viterbo e che quest’anno ha scelto come location Villa Sofia.

Venerdì 4 ottobre numerosi ospiti provenienti da tutto il mondo cyber hanno affollato la sala per ascoltare i talk degli esperti di fama internazionale sul palco; nella sala antistante erano presenti i desk informativi degli sponsor che hanno condiviso informazioni riguardanti la mission delle loro aziende.

“Al centro del dibattito emergono le dinamiche di un mondo in continua evoluzione e l’urgenza di un costante aggiornamento per prevenire le criticità legate alla sicurezza informatica. In tal senso, ogni impresa dovrebbe avvalersi di figure professionali e sistemi adeguati per tutelarsi da eventuali attacchi cibernetici. La perdita di dati può compromettere in maniera irreparabile la sopravvivenza di un’azienda,” avverte Gianluca Boccacci, Presidente dell’Associazione dei Cyber Actors, promotrice dell’evento.
Nella foto Gianluca Boccacci
“Con l’occasione sento di esprimere i miei ringraziamenti a tutti i nuovi membri del Direttivo dell’Associazione con i quali abbiamo formato una bella squadra, e anche a tutti i ragazzi che ci hanno aiutato nell’organizzazione del Forum”.

I Cyber Actors ringraziano anche tutti gli esperti che hanno preso parte all’evento: Angelo Tofalo, Davide Pala, Paola Girdinio, Luca Bongiorni, Mario Cervellini, Alicia Fawcett, Alessandro Curioni, Luca Francioso e Joele Milazzo, Adolfo Di Fonzo, Paola Giannetakis, Giovanni Manca.

L’appuntamento con la nuova edizione del Cyber Act Forum è per il 2025!

L'articolo Successo per il Cyber Act Forum 2024: Esperti Internazionali e Aggiornamenti sulla Cybersecurity a Villa Sofia proviene da il blog della sicurezza informatica.

Tool changing 3D printers are hot. The idea is that instead of switching filament, you swap out hot ends or other tools. That isn’t a new idea. However, most tool changers are expensive. [Engineers Grow] has one that is simple and inexpensive, relying on the printer’s own motors and some clever mechanics.

The first step was to make a modified extruder that allowed the filament to load and unload. The first attempt didn’t work well, but that is the nice thing about 3D printing — it is easy to try again. There is only one extruder, which is good from the standpoint that you don’t need a control board with many outputs and you avoid the expense of multiple extruders.

The next step is a spring-loaded filament guide to load and unload the new extruder. That didn’t work at first, either. Worse, fixing the problems required yet another redesign of the extruder.

The hot end holds with magnets. This isn’t always as stable as you would like, but it should work, especially with the pin alignment scheme. The tool plate engages with the head and moves to the side to break the magnetic grip. A bracket works the levers to handle the filament changes.

Everything seemed to work when manually moving things around. Macro development eventually wound up with everything working with two heads after troubleshooting a few issues. Of primary concern is the hot ends are not rigidly held, and docking wasn’t always repeatable. However, this is just a prototype and it does work. It only needs more rigidity and repeatability.

Outside of the printer itself, the changer costs about $100, although that will change depending on the number of extruders. Since the whole thing is printer-specific and not fully functional, there are no models or code — and it sounds like [Engineers Grow] plans to make them available only if you have a membership. But the idea is sound, and there is enough information in the video for you to do your own experiments using this mechanical-only design. Let us know what you come up with.

We’ve seen passive changers on CNC before. Many of the others we’ve seen use electromagnets. Our own [Sonya Vasquez] did a take on this with Jubilee.

youtube.com/embed/wjNQ7pUC6R8?…

hackaday.com/2024/10/08/mechan…

I recently wrote about using Klipper to drive my 3D printers, and one natural question is: Why use Klipper instead of Marlin? To some degree that’s like asking why write in one programming language instead of another. However, Klipper does offer some opportunities to extend the environment more easily. Klipper runs on a Linux host, so you can do all of the normal Linux things.

What if you wanted to create a custom G-code that would play a wave file on a speaker? That would let you have custom sounds for starting a print, aborting a print, or even finishing a print.

If you recall, I mentioned that the Klipper system is really two parts. Well, actually more than two parts, but two important parts at the core. Klipper is, technically, just the small software stub that runs on your 3D printer. It does almost nothing. The real work is in Klippy, which is mostly Python software that runs on a host computer like a Raspberry Pi or, in my case, an old laptop.

Because it is Python and quite modular, it is very simple to write your own extensions without having to major surgery or even fork Klipper. At least in theory. Most of the time, you wind up just writing G-code macros. That’s fine, but there are some limitations. This time, I’m going to show you how easy it can be using the sound player as an example.

Macros All the Way Down

Normally, you think of gcode as something like: G1 X50 Y50. Some of the newer codes don’t start with G, but they look similar. But with Klipper, G1, M205, and MeltdownExtruder are all legitimate tokens that could be “G-code.”

For example, suppose you wanted to implement a new command called G_PURGE to create a purge line (case doesn’t matter, by the way). That’s easy. You just need to put in your configuration file:
[gcode_macro g_purge]
gcode:
# do your purge code here
The only restriction is that numbers have to occur at the end of the name, if at all. You can create a macro called “Hackaday2024,” but you can’t create one called “Hackaday2024_Test.” At least, the documentation says so. We haven’t tried it.

There’s more to macros. You can add descriptions, for example. You can also override an existing macro and even call it from within your new macro. Suppose you want to do something special before and after a G28 homing command:
[gcode_macro g28]
description: Macro to do homing (no arguments)
rename_existing: g28_original
gcode:
M117 Homing...
g28_original
M117 Home done....

Not Enough!

By default, your G-code macros can’t call shell commands. There are some ways to add that feature, but letting a file just run any old command seems like an unnecessary invitation for mayhem. Instead, we’ll write a Klippy “extra.” This is a Python class that resides in your klipper/klippy/extra directory.

Your code will run with a config object that lets you learn about the system in different ways. Suppose you are writing code to set up one single item, and it doesn’t make sense that you might have more than one. For example, consider an extra that raises the print speed for all printing. Then, you’d provide an entry point, load_config, and it would receive the config object.

However, it is more common to write code to handle things that could — at least in theory — have multiple instances. For example, if you wanted to control a fan, you might imagine that a printer could have more than one of these fans. In that case, you use load_config_prefix. That allows someone who writes a configuration file to specify multiple copies of the thing you define:
[hackaday_fan fan1]
pin: 8

[hackaday_fan_fan2]pin: 9

The Sounds

In this case, we do want to allow for different sounds to play, so we’ll use load_config_prefix. Here’s the short bit of code that does the trick:

<h1>Play a sound from gcode</h1>

#

<h1>Copyright (C) 2023 Al Williams</h1>

<h1> </h1>

#

<h1>This file may be distributed under the terms of the GNU GPLv3 license.</h1>

import os
import shlex
import subprocess
import logging
class AplayCommand:
def <strong>init</strong>(self, config):
self.name = config.get_name().split()[-1] # get our name
self.printer = config.get_printer()
self.gcode = self.printer.lookup_object(039;gcode039;) # get wave and path
wav = config.get(039;wave039;)
path = config.get(039;path039;,None)
if path!=None:
wav = "aplay "+path+039;/039;+wav
else:
wav = "aplay " + wav
self.wav = shlex.split(wav) # build command line
self.gcode.register_mux_command( # register new command for gcode_macro
"APLAY", "SOUND", self.name,
self.cmd_APLAY_COMMAND, # worker for new command
desc=self.cmd_APLAY_COMMAND_help) # help text

cmd_APLAY_COMMAND_help = "Play a sound"

def cmd_APLAY_COMMAND(self, params):
try:
proc = subprocess.run(self.wav) # run aplay
except Exception:
logging.exception(
"aplay: Wave {%s} failed" % (self.name))
raise self.gcode.error("Error playing {%s}" % (self.name))

<h1>main entry point</h1>

def load_config_prefix(config):
return AplayCommand(config)

Note that the AplayCommand object does all the actual configuration when you initialize it with a config object. So, to create an “aplay object” in your config files:
[aplay startup]
wave: powerup.wav
path: /home/klipper/sounds

[aplay magic]
wave: /home/klipper/sounds/wand.wav
Then, to use that sound in a macro, you only need to use:
[gcode_macro get_ready]
gcode:
aplay sound=startup
You can make as many different sounds as you like, and if you provide an entire path for the wave parameter, you can omit the path. Optional parameters like this require a default in your code:
path = config.get('path',None)
Obviously, this assumes your Klipper computer has aplay installed and the wave files you want to play. Or, switch players and use whatever format you want.

You can read more about options and other things you can do in the “Adding a host module” section of the code overview documentation. Another good resource is the source code for the stock extras, many of which aren’t really things you’d probably consider as extra.

So next time you want to add some features to your printer, you can do it in Python with less work than you probably thought. Haven’t tried Klipper? You can learn more and get set up fairly quickly.

hackaday.com/2024/10/08/3d-pri…

Using a STM32F429 Discovery board [Jan Zwiener] put together a Game Boy-compatible system called STM32Boy. It is based around the Peanut-GB Game Boy emulator core, which is a pretty nifty and fast single-header GB emulator library in C99. Considering that the average 32-bit MCU these days is significantly faster than the ~4 MHz 8-bit Sharp SM83 (Intel 8080/Zilog Z80 hybrid) in the original Game Boy it’s probably no surprise that the STM32F429 (up to 180 MHz) can emulate this 8-bit SoC just fine.

Since Peanut-GB is a library, the developer using it is expected to provide their own routines to read and write RAM and ROM and to handle errors. Optional are the line drawing, audio read/write and serial Tx/Rx functions, with the library providing reset and a host of other utility functions. Audio functionality is provided externally, such as using the provided MiniGB APU. Although fast, it comes with a range of caveats that limit compatibility and accuracy.

For STM32Boy, [Jan] uses the LCD screen that’s on the STM32 development board to render the screen on, along with a Game Boy skin. The LCD’s touch feature is then used for the controls, as can be elucidated from the main source file. Of note is that the target GB ROM is directly compiled into the firmware image rather than provided via an external SD card. This involves using the xxd tool to create a hex version of the ROM image that can be included. Not a bad way to get a PoC up and running, but we imagine that if you want to create a more usable GB-like system it should at least be able to play more than one game without having to reflash the MCU.

hackaday.com/2024/10/08/runnin…

Gli stipendi dei Chief Information Security Officer (CISO) continuano ad aumentare, ma aumentano anche il loro carico di lavoro e le loro responsabilità. Secondo un rapporto IANS Research del 2024 , il compenso medio per un CISO è di 403.000 dollari all’anno, compreso stipendio, vari bonus e offerte aziendali. Nonostante una crescita dei ricavi del 6,4% nell’ultimo anno, le minacce alla sicurezza cambiano costantemente, aumentando la responsabilità del CISO nel proteggere l’azienda.

Inoltre, nuovi requisiti, come quelli della Securities and Exchange Commission (SEC) statunitense, obbligano i CISO a determinare l’importanza di un incidente entro quattro giorni dalla sua scoperta, il che spesso comporta rischi legali. Tuttavia, molti professionisti non dispongono di risorse sufficienti per svolgere questi compiti, il che aumenta lo stress.

Come sottolinea Fred Kwong, vicepresidente e CISO della DeVry University, una prevenzione efficace delle minacce porta a tagli di budget poiché il management si chiede se siano necessarie risorse aggiuntive se le misure attuali sembrano essere sufficientemente efficaci.

Tra il 2021 e il 2022, la domanda di CISO è aumentata a causa del lavoro a distanza e della maggiore distribuzione di ransomware da parte dei criminali informatici. Tuttavia, questa domanda è ora in calo. Secondo Nick Kakolovsky di IANS Research , solo l’11% dei CISO nel 2024 ha cambiato lavoro o ha ricevuto un bonus fedeltà, rispetto al 44% nel 2022.

I professionisti della cybersecurity nelle agenzie governative tendono ad avere meno probabilità di cambiare lavoro, anche se quasi la metà degli Stati Uniti ha assunto nuovi CISO nell’ultimo anno. La permanenza media di un CISO nella stessa posizione è scesa da 30 mesi nel 2022 a 23 mesi nel 2024. Gli analisti prevedono che la pressione su questi professionisti continuerà a crescere, poiché gli attacchi diventano più complessi, i budget si riducono e la carenza di personale aumenta.

Gli stipendi dei CISO presso le istituzioni scolastiche sono attualmente tra i più bassi, con una media di 243.000 dollari all’anno. Per esempio, l’ex specialista di cybersecurity dell’Università di Washington, Daniel Schwalbe, osserva che il carico di lavoro per la sicurezza nelle istituzioni scolastiche era enorme: c’erano circa mezzo milione di dispositivi sulla rete protetta e ogni giorno circa mille di essi potevano essere compromessi. Tuttavia, Schwalbe ha cambiato lavoro non per lo stipendio, ma per la mancanza di prospettive di carriera.

Anche il ruolo crescente dell’intelligenza artificiale aumenta la tensione. Come sottolinea Kakolowski, i CISO si trovano spesso a essere responsabili dei rischi legati all’intelligenza artificiale, anche se non sempre hanno conoscenze sufficienti in questo campo. Ciò può rappresentare un’ulteriore sfida per le aziende in cui i rischi legati all’IA non sono ancora completamente sotto controllo.

Il futuro dei CISO come professione appare quindi molto incerto. Da un lato, la domanda di professionisti della cybersecurity altamente qualificati continua ad aumentare. Dall’altro, la crescente complessità delle minacce, la carenza di personale e i budget limitati stanno creando serie sfide per la professione.

L'articolo Il Paradosso del CISO! Stipendio e Burnout sono Direttamente Proporzionali proviene da il blog della sicurezza informatica.

ISRAEL ATTACKS ON GAZA HAVE KILLED MORE WOMEN AND CHILDREN IN ONE YEAR THAN ANY CONFLICT IN THE LAST 18 YEARS.

instagram.com/p/DAokin9SqvF/?i…

AJ+ on Instagram: "This 10-year-old girl in Gaza wrote a will leaving behind her toys and allowance before she was killed by Israel’s attacks. In the will, Rasha divided her belongings between her cousins and brother Ahmad, who was also killed. “Please

153K likes, 1,850 comments - ajplus on October 2, 2024: "This 10-year-old girl in Gaza wrote a will leaving behind her toys and allowance before she was killed by Israel’s attacks.

^Instagram

The Zeros - Don't Push Me Around: definiti come i Ramones californiani se non addirittura messicani (il leader Javier Escovedo è figlio di emigranti, tutti musicisti). @Musica Agorà

iyezine.com/the-zeros-dont-pus…

The Zeros - Don't Push Me Around

The Zeros - Don't Push Me Around - The Zeros - Don't Push Me Around: definiti come i Ramones californiani se non addirittura messicani (il leader Javier Escovedo è figlio di emigranti, tutti musicisti). - The Zeros

^{Claudio Frandina (In Your Eyes ezine)}

Short, fast, loud and to the fucking point: questa è, da sempre, l’essenza degli ZEKE, leggendario combo speed rock statunitense che, dal 1992 a oggi, ha fatto del rock ‘n’ roll veloce, grezzo, tiratissimo e sparato a manetta la sua bandiera e natura musicale. @Musica Agorà

iyezine.com/zeke-snake-eyes-th…

ZEKE - SNAKE EYES / THE KNIFE 7"

ZEKE - SNAKE EYES / THE KNIFE 7" - Short, fast, loud and to the fucking point: questa è, da sempre, l'essenza degli ZEKE, leggendario combo speed rock statunitense che, dal 1992 a oggi, ha fatto del rock 'n' roll veloce, grezzo, tiratissimo e sparato…

^{Reverend Shit-Man (In Your Eyes ezine)}