All translations have been updated for the Debian Bookworm version of the Debian Administrator's Handbook. Due to Debian Trixie being released soon, we hope to release the Trixie version of the book soon as well. Thus, there might only be a brief period to translate the Bookworm version of the book this time. We thank everybody who has contributed so far and hope that you continue your great work.

Translation status

567 Strings 91%
Browse Translate
16,138 Words 82%
128,724 Characters 82%

Strings status

Strings Words Characters
567 16,138 128,724
All strings Browse Translate Zen
517 13,282 106,212
Translated strings Browse Translate Zen
50 2,856 22,512
Unfinished strings Browse Translate Zen
9 228 1,671
Untranslated strings Browse Translate Zen
41 2,628 20,841
Strings marked for edit Browse Translate Zen
22 1,949 15,905
Strings with any failing checks Browse Translate Zen
40 235 4,771
Translated strings with dismissed checks Browse Translate Zen
5 1,488 11,635
Failing check: Mismatching line breaks Browse Translate Zen
18 1,068 9,419
Failing check: XML markup Browse Translate Zen

Overview

Project website debian-handbook.info
Instructions for translators

https://debian-handbook.info/contribute/ Mailing list for translators: <debian-handbook-translators@lists.alioth.debian.org
Project maintainers User avatar rhertzogUser avatar pereUser avatar dleidert
Translation license GNU General Public License v2.0 or later
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://salsa.debian.org/hertzog/debian-handbook.git
Repository branch bookworm/main
Last remote commit Update PO files c274c239
User avatar dleidert authored 2 days ago
Last commit in Weblate ru-RU: Translated using Weblate. 66b9dbd5
User avatar ashed authored yesterday
Weblate repository https://hosted.weblate.org/git/debian-handbook/12_advanced-administration/
File mask */14_security.po
Translation file Download ca-ES/14_security.po
Last change April 22, 2025, 2:06 a.m.
Last change made by None
Language Catalan
Language code ca
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 8,218,781
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
3 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 567 16,138 128,724
Translated 91% 517 82% 13,282 82% 106,212
Needs editing 7% 41 16% 2,628 16% 20,841
Read-only 0% 0 0% 0 0% 0
Failing checks 3% 22 12% 1,949 12% 15,905
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 1% 9 1% 228 1% 1,671
Last 12 months Previous

Activity in last 12 months

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 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
AprMayJunJulAugSepOctNovDecJanFebMar

Quick numbers

16,138
Hosted words
567
Hosted strings
91%
Translated
3
Contributors
and previous 30 days

Trends of last 30 days

+3%
Hosted words
+100%
+2%
Hosted strings
+100%
−8%
Translated
+100%
—
Contributors
—
User avatar None

Resource updated
The “ca-ES/14_security.po” file was changed. 2 days ago
User avatar None

String added in the repository
comparing the system to the last known uncompromised backup can quickly reveal the changes left by the attacker, e.g. files added, changed, or deleted;
 
2 days ago
User avatar None

String added in the repository
Once the “dynamic” elements have been saved, the next step is to store a complete image of the hard-disk. Making such an image is impossible if the filesystem is still evolving, which is why it must be remounted read-only. The simplest solution is often to halt the server brutally (after running <command>sync</command>) and reboot it on a rescue CD. Each partition should be copied with a tool such as <command>dd</command>; these images can be sent to another server (possibly with the very convenient <command>nc</command> tool). Another possibility may be even simpler: just get the disk out of the machine and replace it with a new one that can be reformatted and reinstalled. Most server providers offer a so-called rescue-console that essentially provides the same functionality as a rescue CD.
Un cop s'han salvat els elements “dinàmics”, el següent pas és emmagatzemar una imatge completa del disc dur. Fer una imatge així és impossible si el sistema de fitxers encara està evolucionant, i per això ha de ser remuntat només de lectura. La solució més simple és sovint aturar el servidor de cop (després d'executar <command>sync</command>) i reiniciar-lo amb un CD de rescat. Cada partició s'ha de copiar amb una eina com <command>dd</command>; aquestes imatges es poden enviar a un altre servidor (possiblement amb la molt convenient eina <command>nc</command>). Una altra possibilitat pot ser fins i tot més simple: simplement treure el disc de la màquina i substituir-lo per un altre de nou que pugui ser reformatat i reinstal·lat.
2 days ago
User avatar None

Source string changed
Once the “dynamic” elements have been saved, the next step is to store a complete image of the hard-disk. Making such an image is impossible if the filesystem is still evolving, which is why it must be remounted read-only. The simplest solution is often to halt the server brutally (after running <command>sync</command>) and reboot it on a rescue CD. Each partition should be copied with a tool such as <command>dd</command>; these images can be sent to another server (possibly with the very convenient <command>nc</command> tool). Another possibility may be even simpler: just get the disk out of the machine and replace it with a new one that can be reformatted and reinstalled. Most server providers offer a so-called rescue-console that essentially provides the same functionality as a rescue CD.
2 days ago
User avatar None

String added in the repository
This may only be possible if the server is physically accessible. When the server is hosted in a hosting provider's data center halfway across the country, or if the server is not accessible for any other reason, it is usually a good idea to start by gathering some important information (see <xref linkend="sect.keeping-everything-that-could-be-used-as-evidence" />, <xref linkend="sect.forensic-analysis" /> and <xref linkend="sect.reconstituting-the-attack-scenario" />), then isolating that server as much as possible by shutting down as many services as possible (usually, everything but <command>sshd</command>). This case is still awkward, since one can't rule out the possibility of the attacker having SSH access like the administrator has; this makes it harder to “clean” the machines. If possible, and if the provider supports it, the server can be put offline and accessed through the providers KVM/IPMI interface or their rescue console. If the affected machine is a virtual machine, a snapshot should be taken immediately to secure evidence.
Això només pot ser possible si el servidor és físicament accessible. Quan el servidor està allotjat en un centre de dades d'un proveïdor d'allotjament a l'altre costat del país, o si el servidor no és accessible per cap altra raó, normalment és una bona idea començar recopilant informació important (vegeu <xref linkend="sect.keeping-everything-that-could-be-used-as-evidence" />, <xref linkend="sect.forensic-analysis" /> i <xref linkend="sect.reconstituting-the-attack-scenario" />), per després aïllar aquest servidor tant com sigui possible mitjançant el tancament de tots els serveis possibles (normalment tots excepte <command>sshd</command>). Aquest cas encara és incòmode, ja que no es pot descartar la possibilitat que l'atacant tingui accés a SSH com té l'administrador; això fa més difícil “netejar” les màquines.
2 days ago
User avatar None

Source string changed
This may only be possible if the server is physically accessible. When the server is hosted in a hosting provider's data center halfway across the country, or if the server is not accessible for any other reason, it is usually a good idea to start by gathering some important information (see <xref linkend="sect.keeping-everything-that-could-be-used-as-evidence" />, <xref linkend="sect.forensic-analysis" /> and <xref linkend="sect.reconstituting-the-attack-scenario" />), then isolating that server as much as possible by shutting down as many services as possible (usually, everything but <command>sshd</command>). This case is still awkward, since one can't rule out the possibility of the attacker having SSH access like the administrator has; this makes it harder to “clean” the machines. If possible, and if the provider supports it, the server can be put offline and accessed through the providers KVM/IPMI interface or their rescue console. If the affected machine is a virtual machine, a snapshot should be taken immediately to secure evidence.
2 days ago
User avatar None

String added in the repository
a program that utilizes all CPU cores or memory;
 
2 days ago
User avatar None

String added in the repository
a command that suddenly shows errors like segmentation faults;
 
2 days ago
User avatar None

String added in the repository
Another very common scenario nowadays is a ransomware attack. The attackers will encrypt the data on the machine and leave a note with instructions how to pay ransom to get the key to decrypt the data. Of course, it is not for certain that even after paying, the data can be recovered or be sure it hasn't been stolen (and sold) as well.
 
2 days ago
User avatar None

String added in the repository
The consequences of an intrusion will have various levels of obviousness depending on the motivations of the attacker. “Script-kiddies“ only apply recipes they find on web sites; most often, they deface a web page or delete data. In more subtle cases, they add invisible contents to web pages so as to improve referrals to their own sites in search engines. In others, they simply install crypto-miners and use the compromised system to fill their crypto wallets.
Les conseqüències d'una intrusió tindran diversos nivells d'obvietat depenent de les motivacions de l'atacant. Els «Script-kiddies» només apliquen receptes que troben en llocs web; la majoria de vegades desmunten una pàgina web o n'eliminen dades. En casos més subtils, afegeixen continguts invisibles a les pàgines web per tal de millorar les referències als seus propis llocs en els motors de cerca.
2 days ago
Browse all translation changes