Lector de Feeds

← Older revision Revision as of 09:11, 1 March 2025 (2 intermediate revisions by the same user not shown)Line 1: Line 1:  +  +  '''Utiliser des applications Java dans les navigateurs Firefox et Chromium''' '''Utiliser des applications Java dans les navigateurs Firefox et Chromium'''    Line 11: Line 13:       −Le serveur télécharge alors un petit fichier .jnlp, qu'il faut alors éxecuter. Mais Firefox et Chromium ne soutiennent plus les formats Java.  +Le serveur télécharge alors un petit fichier .jnlp, qu'il faut alors éxecuter.    +   +Mais Firefox et Chromium ne soutiennent plus les formats Java.       Une alternative a été créée : OpenWebStart, il est sur github.com. Une alternative a été créée : OpenWebStart, il est sur github.com. Line 26: Line 30:  Voir doc: Voir doc:  https://openwebstart.com/docs/OWSGuide.html#_what_is_openwebstart https://openwebstart.com/docs/OWSGuide.html#_what_is_openwebstart  +  Et maintenant, firefox et Chromium exécutent les fichiers .jnlp. Et maintenant, firefox et Chromium exécutent les fichiers .jnlp. Scroll44

Created page with "'''Utiliser des applications Java dans les navigateurs Firefox et Chromium''' Pour cela, il faut exécuter des scripts java sur son navigateur, avec son et image. Démarche..."

New page

'''Utiliser des applications Java dans les navigateurs Firefox et Chromium'''

Pour cela, il faut exécuter des scripts java sur son navigateur, avec son et image.


Démarche :


Tout d’abord, il faut installer java-17-openjdk du CCM.



Le serveur télécharge alors un petit fichier .jnlp, qu'il faut alors éxecuter. Mais Firefox et Chromium ne soutiennent plus les formats Java.

Une alternative a été créée : OpenWebStart, il est sur github.com.

https://github.com/karakun/OpenWebStart/releases/

Ce qu'il faut faire c'est télécharger OpenWebStart_linux_1_11_1.deb

Et faire en ROOT :
dpkg -i OpenWebStart_linux_1_11_1.deb

L'installation se passe bien. Les fichiers sont installés dans /opt

Voir doc:
https://openwebstart.com/docs/OWSGuide.html#_what_is_openwebstart
Et maintenant, firefox et Chromium exécutent les fichiers .jnlp. Scroll44

‎Logiciel

← Older revision Revision as of 09:02, 1 March 2025 Line 165: Line 165:  * [[Hubic-fr|<span style="color:green;">Hubic</span>]] * [[Hubic-fr|<span style="color:green;">Hubic</span>]]  * [[Contrôle à distance avec X11VNC et tunnel SSH-fr#Installation SSH|SSH, configurer le serveur]] * [[Contrôle à distance avec X11VNC et tunnel SSH-fr#Installation SSH|SSH, configurer le serveur]]  +* [[Utiliser des applications Java dans les navigateurs Firefox et Chromium]]  </div> </div>    Scroll44

Publication date: 28 Feb 2025
Type: bugfix
Affected Mageia releases : 9
Description gnome-boxes can't redirect usb ports to guest systems, this is due missing requiriment on spice-gtk. This update fixes the issue. References

• https://bugs.mageia.org/show_bug.cgi?id=33445

SRPMS 9/core

• gnome-boxes-44.2-1.1.mga9

Publication date: 28 Feb 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-1378 Description A vulnerability, which was classified as problematic, was found in radare2. Affected is an unknown function in the library /libr/main/rasm2.c of the component rasm2. The manipulation leads to memory corruption. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. References

• https://bugs.mageia.org/show_bug.cgi?id=34044
• https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/message/6L3CRKPOLSYHPHW4QETC25D65CTE33EO/
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-1378

SRPMS 9/core

• radare2-5.8.8-1.5.mga9

correção em evita

← Older revision Revision as of 22:32, 27 February 2025 Line 39: Line 39:  Em vez de digitar o nome completo do comando ou diretório, digite as primeiras letras e pressione a tecla TAB (tabulação). Isso: Em vez de digitar o nome completo do comando ou diretório, digite as primeiras letras e pressione a tecla TAB (tabulação). Isso:  * economiza tempo; * economiza tempo; −* vita erros de digitação;   +* evita erros de digitação;     * atua como ajuda de memória, listando todas as possibilidades correspondentes às primeiras letras digitadas. * atua como ajuda de memória, listando todas as possibilidades correspondentes às primeiras letras digitadas.    Xgrind

The Brazilian forum no longer exists.

← Older revision Revision as of 22:23, 27 February 2025 Line 17: Line 17:  * Greek: http://www.mageia-gr.org/forum/ * Greek: http://www.mageia-gr.org/forum/  * Italian: http://mageiaitalia.org/forum * Italian: http://mageiaitalia.org/forum −* Portuguese: https://www.mageiadobrasil.com.br/forum/   * Russia: https://forum.mageia.org.ru/, https://linuxforum.ru/viewforum.php?id=80 * Russia: https://forum.mageia.org.ru/, https://linuxforum.ru/viewforum.php?id=80  * Spanish: https://blogdrake.net/foros * Spanish: https://blogdrake.net/foros Xgrind

Publication date: 26 Feb 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-1390 Description pam_cap: Fix potential configuration parsing error. (CVE-2025-1390) References

• https://bugs.mageia.org/show_bug.cgi?id=34048
• https://ubuntu.com/security/notices/USN-7287-1
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-1390

SRPMS 9/core

• libcap-2.52-5.1.mga9

Publication date: 26 Feb 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2024-57392 Description A buffer overflow vulnerability in Proftpd commit 4017eff8 allows a remote attacker to execute arbitrary code and can cause a denial of service (DoS) on the FTP service by sending a maliciously crafted message to the ProFTPD service port. (CVE-2024-57392) References

• https://bugs.mageia.org/show_bug.cgi?id=34042
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/E36XSNXDCOSSYTPKEMAEUAZ6QVQJTSFZ/
• https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/message/C3HZA5IS6YXHXDULEZHLHWOVCC3IYNGP/
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-57392

SRPMS 9/core

• proftpd-1.3.8c-1.1.mga9

Publication date: 26 Feb 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-26465 Description Machine-in-the-middle attack vulnerability if verifyhostkeydns is enabled. (CVE-2025-26465) References

• https://bugs.mageia.org/show_bug.cgi?id=34036
• https://openwall.com/lists/oss-security/2025/02/18/1
• https://openwall.com/lists/oss-security/2025/02/18/4
• https://lists.debian.org/debian-security-announce/2025/msg00030.html
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/STTU3AYQZPT4FUMERJH7RQ3KH3TMQDUI/
• https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/message/GGMBNUMHNWAKKPCVKBQBXE7C4WSYOBAY/
• https://ubuntu.com/security/notices/USN-7270-1
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-26465

SRPMS 9/core

• openssh-9.3p1-2.4.mga9

To do a good job, we need good tools. Some of our servers are old, no longer powerful enough and have limited disk resources to meet the needs of developers. RPM manufacturing takes a long time and this is detrimental to the efficiency of maintaining and evolving the distribution. In short, the machines are well depreciated.

This is why our infrastructure is first getting a makeover. Better adapted to new technologies, it will allow our developers to work faster and more efficiently.

So where is this new infrastructure?

 We received 5 new servers:

– 2 new nodes for building packages: HPE ProLiant DL 360 Gen10 – 2xXeon 6126 (12C/2.6GHz) –

256GB RAM – 2xSSD 3.8TB HW Raid 1 – 2x10Gb/s NICs

– 2 servers to replace sucuk and duvel: HPE ProLiant DL 380 Gen10 – 2 Xeon 6126 (12C/2.6GHz) –

256GB RAM – 2xSSD 3.8TB HW Raid 1 – 10xHDD 12TB HW Raid 5 – 2x10Gb/s NICs

– 1 server for deployment and backup: HPE ProLiant DL80 Gen9 – 2xXeon  E5-2603v4

(6C/1.7GHz) – 256GB RAM – 6xHDD 6TB (donated, with some renewed parts)

– 1 Arista 7120T switch 20xRJ-45 10Gb/s 4xSFP+ 10Gb/s for interconnecting the machines

One of the ideas is to use the latest server to deploy quickly and as automatically as possible the construction nodes and other machines. The method is ready for x86_64 nodes and is being finalized for ARM nodes. The preparation of the servers takes time because the teams anticipate the future and future developments.

Once the preparation part of our servers is finished, the integration part into the Data Center will remain.

We are therefore taking our time to do things well in order to perpetuate the future and future versions of Mageia.

In the meantime, the future version 10 of Mageia continues to bubble in its cauldron! But we are not ready yet to plan a release date for the moment.

Feel free to come and strengthen our teams.

Para hacer un buen trabajo, necesitamos buenas herramientas. Algunos de nuestros servidores son viejos, ya no son lo bastante potentes y tienen recursos de disco limitados para satisfacer las necesidades de los desarrolladores. Se tarda mucho en producir los RPM, lo que va en detrimento de la eficacia del mantenimiento y la actualización de la distribución. En resumen, las máquinas están bien amortizadas.

Es por eso que nuestra infraestructura está recibiendo un lavado de cara. Más adaptada a las nuevas tecnologías, permitirá a nuestros desarrolladores trabajar de forma más rápida y eficaz. ¿Cuál es el estado de esta nueva infraestructura? Hemos recibido 5 nuevos servidores:

· 2 nuevos nodos de construcción de paquetes: HPE ProLiant DL 360 Gen10 – 2xXeon 6126 (12C/2.6GHz) – 256GB RAM – 2xSSD 3.8TB HW Raid 1 – 2x10Gb/s NICs.

· 2 servidores para reemplazar sucuk y duvel: HPE ProLiant DL 380 Gen10 – 2 Xeon 6126 (12C/2.6GHz) – 256GB RAM – 2xSSD 3.8TB HW Raid 1 – 10xHDD 12TB HW Raid 5 – 2x10Gb/s NICs.

· 1 servidor de despliegue y copia de seguridad: HPE ProLiant DL80 Gen9 – 2xXeon E5-2603v4 (6C/1.7GHz) – 256GB RAM – 6xHDD 6TB (una donación, con algunas partes renovadas)

· 1 switch Arista 7120T 20xRJ-45 10Gb/s 4xSFP+ 10Gb/s para interconectar las máquinas.

El plan es utilizar el último servidor para desplegar los nodos de construcción y el resto de máquinas de forma rápida y lo más automática posible. El método está listo para los nodos x86_64 y se está ultimando para los nodos ARM (servidores remotos). La preparación de los servidores lleva su tiempo, ya que nuestros equipos se anticipan al futuro y a los futuros desarrollos.

Una vez finalizada la preparación de nuestros servidores, el siguiente paso será integrarlos en el Centro de Datos. Por lo tanto, nos estamos tomando nuestro tiempo para hacer las cosas bien y poder asegurar el futuro y las futuras versiones de Mageia. Por el momento, no publicamos una fecha de lanzamiento provisional para Mageia 10.

Mientras tanto, ¡la futura versión 10 de Mageia sigue burbujeando en su caldero!

No dudes en unirte a nuestros equipos.