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.

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 yesterday
Last commit in Weblate sv-SE: Translated using Weblate. e847ba88
User avatar hanklank authored 6 hours ago
Weblate repository https://hosted.weblate.org/git/debian-handbook/12_advanced-administration/
File mask */14_security.po
Translation file Download fa-IR/14_security.po
Last change April 22, 2025, 2:06 a.m.
Last change made by None
Language Persian
Language code fa
Text direction Right to left
Case sensitivity Case-insensitive
Number of speakers 89,208,445
Number of plurals 2
Plural type One/other
Plurals Singular 0, 1
Plural 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, …
Plural formula n > 1
yesterday

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 567 16,138 128,724
Translated 52% 297 49% 7,941 45% 58,622
Needs editing 35% 203 34% 5,596 38% 50,071
Read-only 0% 0 0% 0 0% 0
Failing checks 22% 126 21% 3,435 26% 34,082
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 11% 67 16% 2,601 15% 20,031
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
52%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated
The “fa-IR/14_security.po” file was changed. yesterday
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;
 
yesterday
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.
زمانی که این عنصرهای ... ذخیره‌سازی شوند، گام بعدی ذخیره‌سازی یک تصویر کامل از هارد-دیسک است. ایجاد چنین تصویری در صورت تغییر اندازه فایل سیستم غیرممکن است، به همین دلیل است که ابتدا باید به صورت فقط-خواندنی متصل گردد. ساده‌ترین راهکار توقف اجباری سرور (پس از اجرای <command>sync</command>) و اجرای مجدد آن روی یک دیسک نجات است. هر پارتیشن باید با ابزاری مانند <command>dd</command> رونوشت گرفته شود؛ این تصاویر می‌توانند به سرور دیگری فرستاده شوند (احتمالا با ابزار <command>nc</command>). احتمال دیگر حتی از این نیز ساده‌تر است: تنها کافی است دیسک را از ماشین خارج کرده و با یک دیسک جدید جایگزین کنیم تا بتوان عملیات فرمت‌دهی و نصب مجدد را انجام داد.
yesterday
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.
yesterday
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.
اینکار تنها در صورت دسترسی فیزیکی به سرور ممکن است. زمانی که سرور در یک مرکز داده سرویس میزبانی درون کشور قرار گرفته یا به هر دلیل دیگر قابل دسترس نباشد، ایده خوبی است که اطلاعات بیشتری در این مورد جمع‌آوری (<xref linkend="sect.keeping-everything-that-could-be-used-as-evidence" />، <xref linkend="sect.forensic-analysis" /> و <xref linkend="sect.reconstituting-the-attack-scenario" /> را مشاهده کنید)، سپس تا آنجا که امکان دارد سرور را با استفاده از خاموش کردن سرویس‌های ممکن ایزوله کنیم (معمولا، همه سرویس‌ها بجز <command>sshd</command>). این مورد نیز مشکلات خود را دارد، چون کسی نمی‌تواند بگوید آیا مهاجم نیز مانند مدیر سیستم دسترسی SSH را بدست گرفته است یا خیر: اینکار “پاکسازی” ماشین را دشوارتر می‌سازد.
yesterday
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.
yesterday
User avatar None

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

String added in the repository
a command that suddenly shows errors like segmentation faults;
 
yesterday
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.
 
yesterday
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.
عواقب یک نفوذ سطوح مختلفی از مشاهدات درباره انگیزه مهاجم اصلی را شامل می‌شود. <emphasis>Script-kiddie</emphasis> تنها از دستورالعمل‌های موجود در وبسایت‌ها استفاده می‌کند؛ اغلب یا وبسایت را از دسترس خارج یا داده‌ها را تخریب می‌کنند. در موارد نامحسوس دیگر، آن‌ها اقدام به افزودن محتوای نامرئی در صفحات وب می‌کنند تا از طریق موتورهای جستجو بازدید بیشتری از سایت خود دریافت کنند.
yesterday
Browse all translation changes