Lector de Feeds
An avalanche of AI bots is repeatedly taking parts of our website down
We have always had bots visiting our website. They were mostly kind bots, like the crawlers that keep the databases of search engines up-to-date. Those kind bots start by looking at our robots.txt files before doing anything, and respect the restrictions that are set in those files.
However, things have changed. Like other websites, for instance Wikipedia, we are more and more being visited by AI scrapers, bots that scrape the Internet for anything they can find to train AI applications. They are usually extremely hungry for information, so they download much, much more than an ordinary user would do. Moreover, many of them are impolite: they don’t respect the rules set in our robots.txt files, they hide who they really are, they don’t put a little pause in between requests – on the contrary, they hammer our servers with requests from lots and lots of different IP addresses at the same time. The result is that parts of mageia.org, like our Bugzilla, Wiki and Forums, become unreachable.
Below you can see the CPU load of one of our most important servers, where, amongst other things, our forums and wiki are located:
Even if our infra upgrade had already been finished, this would be really hard to mitigate.
Blocking the used IP addresses is useless because they constantly switch to new ones. One of our sysadmins just told me about a big issue: “mobile proxies” where bots proxy their request through unsuspecting users’ phones. That makes the requests look much more legitimate and hard to block without also blocking real users. A lot of that happens without users even knowing their phone is being used like this. Some applications include proxies along with some game or other app and hide it in fine print in the terms of service. Last year, it was reported that Google had removed a bunch of such applications from their store.
Apart from phones, there are IoT devices and also ordinary computers that ended up in botnets, because they were not well protected. They can be used for AI scraping and probably are now.
Our sysadmins do time and again succeed in mitigating the problem, but it is a “cat and mouse game”, so the problem is likely to reoccur.
If you know people working on AI applications which need to be trained, please ask them to make sure their bots read and respect the robots.txt files they encounter. And, of course, please nudge your friends and family, when you think they need that, to make sure their computers and other smart devices get all security updates as soon as they are released.
Kernel-Arten-de
Nuestros sitios están intermitentemente fuera de servicio por una avalancha de robots IA
Siempre hemos tenido visitas de robots en nuestros sitios. Normalmente, son inofensivos, como los rastreadores, que mantienen actualizados los motores de búsqueda. Esos robots comienzan por revisar nuestros archivos robots.txt, antes de hacer nada y respetan las restricciones contenidas en esos archivos.
Pero las cosas han cambiado, al igual que otros sitios, hemos sido visitados cada vez más frecuentemente por escarbadores IA, robots que indagan en el internet por cualquier cosa que puedan encontrar para entrenar aplicaciones IA. Estos son extremadamente hambrientos de información, así que descargan mucho más de lo que cualquier usuario podría hacer. Peor aún, muchos de ellos son mal educados y no respetan las reglas de nuestros archivos robots.txt, esconden su identidad, y no hacen pausas entre peticiones – al contrario, golpean nuestros servidores con peticiones desde montones de direcciones IP diferentes al mismo tiempo. Como resultado, partes de mageia.org, como Bugzilla, Wiki y Foros, se hacen inaccesibles.
A continuación, pueden ver la carga de la CPU de uno de nuestros servidores más importantes, donde se encuentran, entre otros, nuestros foros y wiki:
Incluso si nuestra actualización de infraestructura ya hubiera terminado, esto sería realmente difícil de mitigar.
Bloquear las direcciones IP es inútil, ya que constantemente están cambiando por otras. Uno de nuestros administradores apunta a un gran problema: “proxis móviles”, los robots dirigen sus peticiones desde teléfonos sin que los usuarios sospechen. Esto hace que las peticiones parezcan legítimas y las hace difíciles de bloquear sin bloquear al usuario real. Mucho de esto pasa sin que los usuarios sepan que sus teléfonos son usados de esta forma, algunos proxis son incluidos en juegos u otras aplicaciones y lo ocultan en las letras pequeñas de los términos de servicio. El año anterior, se reportó que Google elimino montones de este tipo de aplicaciones de su tienda.
Además de los teléfonos, están todos esos dispositivos IoT y computadoras que terminan formando parte de botnets, debido a su mala protección. Ahora quizas esten siendo utilizados por escarbadores IA.
Nuestros administradores de sistemas tienen éxito en mitigar el problema , pero es el «juego del gato y el ratón», así que es un problema recurrente.
Si conocen a personas que estén trabajando en entrenar aplicaciones IA, por favor pídales que se aseguren de que sus robots lean y respeten los archivos robots.txt que encuentren.
Y desde luego, cuando crea necesario, incentive a sus amigos y familiares a asegurarse de que sus computadoras y otros dispositivos inteligentes tengan todas las actualizaciones de seguridad tan pronto como se publiquen.
Traducido por katnatek de la publicación original de marja
Alien-de
MGASA-2025-0158 - Updated dropbear packages fix security vulnerability
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-47203 Description dbclient in Dropbear SSH before 2025.88 allows command injection via an untrusted hostname argument, because a shell is used. References
- https://bugs.mageia.org/show_bug.cgi?id=34264
- https://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/2025q2/002385.html
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-47203
- dropbear-2022.83-2.2.mga9
MGASA-2025-0157 - Updated openssh packages fix security vulnerability
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-32728 Description In sshd in OpenSSH before 10.0, the DisableForwarding directive does not adhere to the documentation stating that it disables X11 and agent forwarding. (CVE-2025-32728) References
- https://bugs.mageia.org/show_bug.cgi?id=34224
- https://ubuntu.com/security/notices/USN-7457-1
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-32728
- openssh-9.3p1-2.5.mga9
Kernel flavours
Other kernels: Add section about the kernel series in cauldron
← Older revision Revision as of 14:02, 16 May 2025 (One intermediate revision by the same user not shown)Line 54: Line 54: This kernel is for processors with a unique core like pentium I (i586 architecture) and is able to address till 4 Gb memory. This kernel is for processors with a unique core like pentium I (i586 architecture) and is able to address till 4 Gb memory. −This kernel is proposed with the same version as kernel-desktop+This kernel is proposed with the same version as kernel-desktop. + +This package will not be available in Mageia 10 and later. With the transition from i586 to i686+SSE2, this architecture now supports PAE (Physical Address Extension), enabling support for up to 64 GB of memory as in standard -desktop flavor. == Other kernels == == Other kernels == Line 63: Line 65: The release follows the up-to-date "release candidates" from kernel.org and can provide support for recent features if not available in standard kernels. The release follows the up-to-date "release candidates" from kernel.org and can provide support for recent features if not available in standard kernels. + +==Kernel series in Cauldron== + +In cauldron we now have -lts, -mainline, and -stable kernel series. These series are (at least for now) intended for Cauldron only and provide opportunities to test newer hardware, as well as aligning the packages required for building stable kernels (e.g.: newer Rust, newer LLVM, missing libraries, etc.). + +The -lts series also allows testing compatibility with the "previous" latest working LTS series, which could be useful in many cases, e.g. for proprietary drivers (e.g., NVIDIA) when they won't build anymore on newer kernels or for verifying different hardware behavior of older hardware with respect to newer kernels. + +Note that it is not guaranteed that all series cover all architectures and flavors. For some series, the build may be limited to a single architecture (e.g., x86_64) and single flavor (e.g., desktop), or new flavors may emerge (e.g., desktop-tunedv3 for x86_64-v3). Marja
