Lector de Feeds

Criando a página Gravar a ISO do Mageia em um pen drive-pt-BR

New page

[[Category:Documentation]]

{{multi language banner|[[Mageia_ISO_auf_ein_USB_Laufwerk_dumpen_-_Alternative_Werkzeuge-de|Deutsch]] ; [[Dump_Mageia_ISO_on_a_USB_flash_drive_-_Alternative_tools|English]] ; [[Copier_un_ISO_de_Mageia_sur_une_clé_USB_-_outils_alternatifs-fr|Français]] ; [[Dump_Mageia_ISO_op_een_usb_stick_-_alternatieve_gereedschappen-nl|Nederlands]] ; [[Colocar_ISO_do_Mageia_numa_unidade_de_pen_USB_-_Ferramentas_alternativas|Português (Portugal)]] ; [[Gravar a ISO do Mageia em um pen drive - Ferramentas alternativas-pt-BR|português brasileiro]] ;}}

* Para Linux, veja… [[Mídias de instalação#Gravar a ISO do Mageia_em_um_pen_drive-pt-BR|Gravar a ISO do Mageia em um pen drive]].

* Para o Microsoft Windows, você pode escolher uma das seguintes ferramentas:
**[https://rufus.akeo.ie/ Rufus]. Para versões mais antigas do Rufus (v2.x e abaixo), você deve usar a opção "DD Image" - isso também é mencionado no [https://github.com/pbatard/rufus/wiki/FAQ#Live_media_issues FAQ do rufus]. As versões atuais do Rufus devem detectar isso automaticamente.<br>
**[https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager], para versões recentes do Windows. Você precisará mudar para "todos os arquivos" quando tentar abrir o .iso, pois ele só permite .img por padrão.<br>
**O [https://www.winimage.com/ WinImage] funciona bem em sistemas com restrições, como o Microsoft Windows 7 Starter. Veja uma página dedicada no wiki atual, sobre como usá-lo: [[Dump Mageia ISO on a USB flash drive - WinImage]].<br>
**[https://www.balena.io/etcher/ Etcher] Xgrind

‎Go: Proposed workflow

← Older revision Revision as of 19:42, 15 February 2025 Line 99: Line 99:  The [https://vuln.go.dev/ Go Vulnerability Database] can be used on an ongoing basis to find security issues in Go packages from the SBOMs of those packages. The [https://vuln.go.dev/ Go Vulnerability Database] can be used on an ongoing basis to find security issues in Go packages from the SBOMs of those packages.    −''details TBD''+A possible workflow:  +   +# After the RPM %install step, run the following:  +#: <pre>syft scan --output spdx-tag-value="%{NAME}-%{VERSION}.%{RELEASE}.%{ARCH}.spdx" dir:%{buildroot}</pre>  +#: ''syft'' scans the installed binaries and generates a SBOM including the Go dependencies embedded therein (including Go's stdlib version). The resulting SBOM file can be stored in a permanent location for later scans.  +# Periodically, scan all the SBOM files to see if any of them show dependencies that have reported vulnerabilities by running on each file:  +#: <pre>grype --output json sbom:"%{NAME}-%{VERSION}.%{RELEASE}.%{ARCH}.spdx"</pre>  +# If any new vulnerabilities are found, open a bug so the package can be rebuilt.     == See Also == == See Also == Danf

Publication date: 14 Feb 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2023-49502 , CVE-2024-31578 Description A buffer overflow vulnerability in Ffmpeg v.n6.1-3-g466799d4f5 allows a local attacker to execute arbitrary code via the ff_bwdif_filter_intra_c function in the libavfilter/bwdifdsp.c:125:5 component. (CVE-2023-49502) FFmpeg version n6.1.1 was discovered to contain a heap use-after-free via the av_hwframe_ctx_init function. (CVE-2024-31578) References

• https://bugs.mageia.org/show_bug.cgi?id=34015
• https://lists.suse.com/pipermail/sle-updates/2024-April/035125.html
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-49502
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-31578

SRPMS 9/core

• ffmpeg-5.1.6-1.2.mga9

9/tainted

• ffmpeg-5.1.6-1.2.mga9.tainted

Publication date: 14 Feb 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2024-5569 Description Denial of Service via crafted zip file in jaraco/zipp. (CVE-2024-5569) References

• https://bugs.mageia.org/show_bug.cgi?id=33395
• https://lists.suse.com/pipermail/sle-updates/2024-July/035932.html
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-5569

SRPMS 9/core

• python-zipp-3.8.1-3.1.mga9

Publication date: 14 Feb 2025
Type: bugfix
Affected Mageia releases : 9
Description The application crashed and the package needed additional requirements to make it work well once installed. This update fixes the issues. References

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

SRPMS 9/core

• texstudio-4.5.1-2.1.mga9

Publication date: 14 Feb 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-22866 Description Timing sidechannel for P-256 on ppc64le in crypto/internal/nistec. (CVE-2025-22866) References

• https://bugs.mageia.org/show_bug.cgi?id=34009
• https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/message/3TLTJ366QWWXT5LOMCQMCAWW4WSJRVJG/
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-22866

SRPMS 9/core

• golang-1.22.12-1.mga9

Publication date: 14 Feb 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-1094 Description PostgreSQL quoting APIs miss neutralizing quoting syntax in text that fails encoding validation. (CVE-2025-1094) References

• https://bugs.mageia.org/show_bug.cgi?id=34018
• https://www.postgresql.org/about/news/postgresql-173-167-1511-1416-and-1319-released-3015/
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-1094

SRPMS 9/core

• postgresql15-15.11-1.mga9
• postgresql13-13.19-1.mga9

Publication date: 14 Feb 2025
Type: bugfix
Affected Mageia releases : 9
Description Issues with the conversions and the progress bar have been reported. This update fixes the issues and removes python3-sip as a requirement as is no longer needed References

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

SRPMS 9/core

• ffmulticonverter-1.8.0-10.1.mga9

‎Apprenticeship in progress

← Older revision Revision as of 09:56, 14 February 2025 Line 224: Line 224:  | pol4n || neoclust || [https://ml.mageia.org/l/arc/dev/2022-03/msg00117.html 2022-03-11] || {{yes|Done}} || {{yes|Done}} || {{yes|Done}} || {{yes|Done}} || rpcbind/sitecopy/spamassassin/ssdeep/sslsplit || {{yes|Done}} || {{yes|Done}} || tap<br>woff2<br>shairplay<br>ntpsec<br>clusterscripts<br>nagios-plugins<br>xymons<br>zathuras<br>rizins<br>vnstat || 2022-08-18 | pol4n || neoclust || [https://ml.mageia.org/l/arc/dev/2022-03/msg00117.html 2022-03-11] || {{yes|Done}} || {{yes|Done}} || {{yes|Done}} || {{yes|Done}} || rpcbind/sitecopy/spamassassin/ssdeep/sslsplit || {{yes|Done}} || {{yes|Done}} || tap<br>woff2<br>shairplay<br>ntpsec<br>clusterscripts<br>nagios-plugins<br>xymons<br>zathuras<br>rizins<br>vnstat || 2022-08-18  |- |- −| joselp || papoteur,mokraemer || {{yes|Done}} ||  || {{yes|Done}} ||  ||  ||  ||  || ||  ||  +| joselp || papoteur,mokraemer || {{yes|Done}} ||  || {{yes|Done}} ||  ||  ||  ||  || photomontage ||  ||    |- |-  | zekemx || kekepower || {{yes|Done}} ||  || ||  ||  || 1. conky ||  ||  ||  || | zekemx || kekepower || {{yes|Done}} ||  || ||  ||  || 1. conky ||  ||  ||  || Papoteur

‎Releasing the update: Mention advisories.mageia.org

← Older revision Revision as of 08:21, 13 February 2025 Line 399: Line 399:  Once the update candidate has been validated (i.e., approved) by the QA Team, a member of the Once the update candidate has been validated (i.e., approved) by the QA Team, a member of the  Sysadmin Team [[#42|[42]]] will see that the updated packages get pushed to the mirrors and that the advisory is Sysadmin Team [[#42|[42]]] will see that the updated packages get pushed to the mirrors and that the advisory is −posted to the website and e-mailed to the updates-announce mailing list [[#43|[43]]] . Every Linux distribution has+posted to https://advisories.mageia.org/ and e-mailed to the updates-announce mailing list [[#43|[43]]] . Every Linux distribution has −a similar mailing list for update announcements. Varying amounts of automation and manual work are+a similar mailing list for update announcements. The advisories will also be picked eventually up by aggregators like https://osv.dev/. −involved in this last stage of the process for different Linux distributions.+Varying amounts of automation and manual work are involved in this last stage of the process for each separate Linux distributions.     == Other considerations == == Other considerations == Danf

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.