Overview

Project website docs.freebsd.org/en
Translation license BSD 2-Clause "Simplified" License
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
File mask documentation/content/*/books/porters-handbook/security/_index.po
Translation file Download documentation/content/es/books/porters-handbook/security/_index.po
Last change Aug. 17, 2026, 12:43 p.m.
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 73 2,091 14,842
Translated 94% 69 87% 1,824 87% 12,925
Needs editing 5% 4 12% 267 12% 1,917
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

11 changes 0 changes 0 changes 12 changes 0 changes 0 changes 0 changes 0 changes 4 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 10 changes 14 changes
Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug

Quick numbers

2,091
Hosted words
73
Hosted strings
94%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+1%
Hosted words
+100%
—
Hosted strings
+100%
−5%
Translated
+100%
+100%
Contributors
—
User avatar None

New strings to translate

Documentation / books/porters-handbook/security/_index — Spanish

4 new strings to translate appeared to the translation. 2 weeks ago
User avatar None

Resource update

Documentation / books/porters-handbook/security/_index — Spanish

The "documentation/content/es/books/porters-handbook/security/_index.po" file was changed. 2 weeks ago
User avatar None

String updated in the repository

Documentation / books/porters-handbook/security/_index — Spanish

Committers can update the VuXML database themselves, assisting the Security Team and delivering crucial information to the community more quickly. Port maintainers can create VuXML entries for their vulnerable ports and file bugs requesting security/vuxml updates. Those who are not committers or have discovered an exceptionally severe vulnerability should not hesitate to contact the link:https://www.freebsd.org/administration.html#t-ports-secteam[FreeBSD Ports Security Team] first. If needed, also contact the link:https://www.freebsd.org/administration.html#t-secteam[FreeBSD Security Team] as described on the link:https://www.freebsd.org/security/#reporting[FreeBSD Security Information] page.
Los committers pueden actualizar ellos mismos la base de datos VuXML, ayudando así al equipo de responsables de seguridad y proporcionando información crucial a la comunidad con mayor rapidez. Aquellos que no sean committers o hayan descubierto una vulnerabilidad excepcionalmente grave no deben dudar en contactar directamente con el Equipo de Responsables de Seguridad, tal y como se describe en la página https://www.freebsd.org/security/#how[Información de seguridad de FreeBSD].
2 weeks ago
User avatar None

Source string changed

Documentation / books/porters-handbook/security/_index — Spanish

Committers can update the VuXML database themselves, assisting the Security Officer Team and delivering crucial information to the community more quickly. Port maintainers can create VuXML entries for their vulnerable ports and file bugs requesting security/vuxml updates. Those who are not committers or have discovered an exceptionally severe vulnerability should not hesitate to contact the Security Officer Team directly,link:https://www.freebsd.org/administration.html#t-ports-secteam[FreeBSD Ports Security Team] first. If needed, also contact the link:https://www.freebsd.org/administration.html#t-secteam[FreeBSD Security Team] as described on the link:https://www.freebsd.org/security/#howreporting[FreeBSD Security Information] page.
2 weeks ago
User avatar None

String updated in the repository

Documentation / books/porters-handbook/security/_index — Spanish

Given the huge number of ports in the tree, a security advisory cannot be issued on each incident without creating a flood and losing the attention of the audience when it comes to really serious matters. Therefore security vulnerabilities found in ports are recorded in https://vuxml.freebsd.org/[the FreeBSD VuXML database], which both Ports Security Team members and Security Team members also monitor for issues requiring their intervention.
Dado el enorme número de ports que hay en el árbol, no se puede emitir un aviso de seguridad sobre cada incidente sin crear una avalancha y perder la atención del público cuando se trata de asuntos realmente serios. Por eso las vulnerabilidades de seguridad encontradas en los ports se registran en https://vuxml.freebsd.org/[la base de datos VuXML de FreeBSD]. Los miembros del equipo de responsables de seguridad también la monitorizan en busca de problemas que requieran su intervención.
2 weeks ago
User avatar None

Source string changed

Documentation / books/porters-handbook/security/_index — Spanish

Given the huge number of ports in the tree, a security advisory cannot be issued on each incident without creating a flood and losing the attention of the audience when it comes to really serious matters. Therefore security vulnerabilities found in ports are recorded in https://vuxml.freebsd.org/[the FreeBSD VuXML database]. The Security Officer, which both Ports Security Team members and Security Team members also monitor it for issues requiring their intervention.
2 weeks ago
User avatar None

String updated in the repository

Documentation / books/porters-handbook/security/_index — Spanish

A very important and urgent step to take as early as possible after a security vulnerability is discovered is to notify the community of port users about the jeopardy. Such a notification serves two purposes. First, if the danger is really severe it will be wise to apply an instant workaround. For example, stop the affected network service or even deinstall the port completely until the vulnerability is closed. Second, a lot of users tend to upgrade installed packages only occasionally. They will know from the notification that they _must_ update the package without delay as soon as a corrected version is available.
Un paso muy importante y urgente que hay que dar lo antes posible tras el descubrimiento de una vulnerabilidad de seguridad es notificar el peligro a la comunidad de usuarios del puerto. Esta notificación tiene dos objetivos. En primer lugar, si el peligro es realmente grave, será prudente aplicar una solución inmediata. Por ejemplo, detener el servicio de red afectado o incluso desinstalar el puerto por completo hasta que se cierre la vulnerabilidad. En segundo lugar, muchos usuarios tienden a actualizar los paquetes instalados sólo de vez en cuando. Sabrán por la notificación que _deben_ actualizar el paquete sin demora en cuanto esté disponible una versión corregida.
2 weeks ago
User avatar None

Source string changed

Documentation / books/porters-handbook/security/_index — Spanish

A very important and urgent step to take as early as possible after a security vulnerability is discovered as possible is to notify the community of port users about the jeopardy. Such a notification serves two purposes. First, if the danger is really severe it will be wise to apply an instant workaround. For example, stop the affected network service or even deinstall the port completely until the vulnerability is closed. Second, a lot of users tend to upgrade installed packages only occasionally. They will know from the notification that they _must_ update the package without delay as soon as a corrected version is available.
2 weeks ago
User avatar None

String updated in the repository

Documentation / books/porters-handbook/security/_index — Spanish

Being a ports committer is not enough to commit to an arbitrary port. Remember that ports usually have maintainers, who must be respected.
Ser committer de un puerto no es suficiente para comprometerse con un puerto arbitrario. Recuerda que los ports suelen tener mantenedores, hay que respetarlos.
2 weeks ago
User avatar None

Source string changed

Documentation / books/porters-handbook/security/_index — Spanish

Being a ports committer is not enough to commit to an arbitrary port. Remember that ports usually have maintainers, who must be respected.
2 weeks ago
Browse all translation changes