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