@@ -11,7 +11,7 @@ msgid ""
1111msgstr ""
1212"Project-Id-Version :Python 3.14\n "
1313"Report-Msgid-Bugs-To :\n "
14- "POT-Creation-Date :2025-09-11 14:18 +0000\n "
14+ "POT-Creation-Date :2025-09-13 14:14 +0000\n "
1515"PO-Revision-Date :2025-08-15 19:00+0000\n "
1616"Last-Translator :python-doc bot, 2025\n "
1717"Language-Team :Swedish (https://app.transifex.com/python-doc/teams/5390/ "
@@ -25,6 +25,112 @@ msgstr ""
2525msgid "Remote debugging attachment protocol"
2626msgstr ""
2727
28+ msgid ""
29+ "This protocol enables external tools to attach to a running CPython process "
30+ "and execute Python code remotely."
31+ msgstr ""
32+
33+ msgid ""
34+ "Most platforms require elevated privileges to attach to another Python "
35+ "process."
36+ msgstr ""
37+
38+ msgid "Permission requirements"
39+ msgstr ""
40+
41+ msgid ""
42+ "Attaching to a running Python process for remote debugging requires elevated "
43+ "privileges on most platforms. The specific requirements and troubleshooting "
44+ "steps depend on your operating system:"
45+ msgstr ""
46+
47+ msgid "Linux"
48+ msgstr ""
49+
50+ msgid ""
51+ "The tracer process must have the ``CAP_SYS_PTRACE`` capability or equivalent "
52+ "privileges. You can only trace processes you own and can signal. Tracing may "
53+ "fail if the process is already being traced, or if it is running with set-"
54+ "user-ID or set-group-ID. Security modules like Yama may further restrict "
55+ "tracing."
56+ msgstr ""
57+
58+ msgid "To temporarily relax ptrace restrictions (until reboot), run:"
59+ msgstr ""
60+
61+ msgid "``echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope``"
62+ msgstr ""
63+
64+ msgid ""
65+ "Disabling ``ptrace_scope`` reduces system hardening and should only be done "
66+ "in trusted environments."
67+ msgstr ""
68+
69+ msgid ""
70+ "If running inside a container, use ``--cap-add=SYS_PTRACE`` or ``--"
71+ "privileged``, and run as root if needed."
72+ msgstr ""
73+
74+ msgid "Try re-running the command with elevated privileges:"
75+ msgstr ""
76+
77+ msgid "``sudo -E !!``"
78+ msgstr ""
79+
80+ msgid "macOS"
81+ msgstr ""
82+
83+ msgid ""
84+ "To attach to another process, you typically need to run your debugging tool "
85+ "with elevated privileges. This can be done by using ``sudo`` or running as "
86+ "root."
87+ msgstr ""
88+
89+ msgid ""
90+ "Even when attaching to processes you own, macOS may block debugging unless "
91+ "the debugger is run with root privileges due to system security restrictions."
92+ msgstr ""
93+
94+ msgid "Windows"
95+ msgstr ""
96+
97+ msgid ""
98+ "To attach to another process, you usually need to run your debugging tool "
99+ "with administrative privileges. Start the command prompt or terminal as "
100+ "Administrator."
101+ msgstr ""
102+
103+ msgid ""
104+ "Some processes may still be inaccessible even with Administrator rights, "
105+ "unless you have the ``SeDebugPrivilege`` privilege enabled."
106+ msgstr ""
107+
108+ msgid ""
109+ "To resolve file or folder access issues, adjust the security permissions:"
110+ msgstr ""
111+
112+ msgid "Right-click the file or folder and select **Properties**."
113+ msgstr ""
114+
115+ msgid "Go to the **Security** tab to view users and groups with access."
116+ msgstr ""
117+
118+ msgid "Click **Edit** to modify permissions."
119+ msgstr ""
120+
121+ msgid "Select your user account."
122+ msgstr ""
123+
124+ msgid "In **Permissions**, check **Read** or **Full control** as needed."
125+ msgstr ""
126+
127+ msgid "Click **Apply**, then **OK** to confirm."
128+ msgstr ""
129+
130+ msgid ""
131+ "Ensure you've satisfied all :ref:`permission-requirements` before proceeding."
132+ msgstr ""
133+
28134msgid ""
29135"This section describes the low-level protocol that enables external tools to "
30136"inject and execute a Python script within a running CPython process."