August 2020 - tor-commits - lists.torproject.org

[translation/support-portal] https://gitweb.torproject.org/translation.git/commit/?h=support-portal
by translation＠torproject.org 18 Aug '20

18 Aug '20

commit c0d807bf4f3f673cb2036b38ed704a0683d8b6de Author: Translation commit bot <translation(a)torproject.org> Date: Tue Aug 18 18:18:04 2020 +0000 https://gitweb.torproject.org/translation.git/commit/?h=support-portal --- contents+ar.po | 21 +++++++++++++++++---- 1 file changed, 17 insertions(+), 4 deletions(-) diff --git a/contents+ar.po b/contents+ar.po index bbbc945656..0be85597d6 100644 --- a/contents+ar.po +++ b/contents+ar.po @@ -11527,6 +11527,8 @@ msgid "" "It's an automatically generated name which can be located on any Tor relay " "or client anywhere on the Internet." msgstr "" +"إنه اسم تم إنشاؤه تلقائيًا ويمكن وضعه على أي مرحل Tor أو عميل في أي مكان على" +" الإنترنت." #: https//support.torproject.org/abuse/remove-content-from-onion-address/ #: (content/abuse/remove-content/contents+en.lrquestion.description) @@ -11534,19 +11536,21 @@ msgid "" "Onion services are designed to protect both the user and service provider " "from discovering who they are and where they are from." msgstr "" +"تم تصميم خدمات Onion لحماية كل من المستخدم ومزود الخدمة من اكتشاف هويتهم ومن" +" أين أتوا." #: https//support.torproject.org/abuse/remove-content-from-onion-address/ #: (content/abuse/remove-content/contents+en.lrquestion.description) msgid "" "The design of onion services means the owner and location of the .onion site" " is hidden even from us." -msgstr "" +msgstr "يعني تصميم خدمات onion إخفاء مالك موقع .onion وموقعه حتى عنا." #: https//support.torproject.org/abuse/remove-content-from-onion-address/ #: (content/abuse/remove-content/contents+en.lrquestion.description) msgid "" "But remember that this doesn't mean that onion services are invulnerable." -msgstr "" +msgstr "لكن تذكر أن هذا لا يعني أن خدمات onion غير معرضة للخطر." #: https//support.torproject.org/abuse/remove-content-from-onion-address/ #: (content/abuse/remove-content/contents+en.lrquestion.description) @@ -11556,6 +11560,9 @@ msgid "" " content itself, sting operations, keyboard taps, and other physical " "investigations." msgstr "" +"يمكن أن تظل تقنيات الشرطة التقليدية فعالة للغاية ضدهم ، مثل إجراء مقابلات مع" +" المشتبه بهم ، وتحليل أسلوب الكتابة ، والتحليل الفني للمحتوى نفسه ، " +"والعمليات اللاذعة ، ونقرات لوحة المفاتيح ، وغيرها من التحقيقات المادية." #: https//support.torproject.org/abuse/remove-content-from-onion-address/ #: (content/abuse/remove-content/contents+en.lrquestion.description) @@ -11565,16 +11572,19 @@ msgid "" "as a national coordination point for investigation of child pornography: " "http://www.missingkids.com/." msgstr "" +"إذا كانت لديك شكوى بشأن مواد تتعلق بإساءة معاملة الأطفال ، فقد ترغب في إبلاغ" +" المركز الوطني للأطفال المفقودين والمستغَلين ، والذي يعمل كنقطة تنسيق وطنية " +"للتحقيق في المواد الإباحية للأطفال: http://www.missingkids.com/." #: https//support.torproject.org/abuse/remove-content-from-onion-address/ #: (content/abuse/remove-content/contents+en.lrquestion.description) msgid "We do not view links you report." -msgstr "" +msgstr "نحن لا نرى الروابط التي تبلغ عنها." #: https//support.torproject.org/abuse/respond-to-isp-about-exit-relay/ #: (content/abuse/respond-isp/contents+en.lrquestion.title) msgid "How do I respond to my ISP about my exit relay?" -msgstr "" +msgstr "كيف أستجيب لمزود خدمة الإنترنت الخاص بي بشأن تتابع الخروج الخاص بي؟" #: https//support.torproject.org/abuse/respond-to-isp-about-exit-relay/ #: (content/abuse/respond-isp/contents+en.lrquestion.description) @@ -11583,6 +11593,9 @@ msgid "" "here](https://community.torproject.org/relay/community-resources/tor-abuse-" "templates/)." msgstr "" +"يتم [جمع هنا] مجموعة من النماذج للاستجابة بنجاح لمزودي خدمات الإنترنت " +"(https://community.torproject.org/relay/community-resources/tor-abuse-" +"templates/)." #: https//support.torproject.org/abuse/help-trace-tor-user/ #: (content/abuse/tracing-users/contents+en.lrquestion.description)

1 0

[translation/communitytpo-contentspot] https://gitweb.torproject.org/translation.git/commit/?h=communitytpo-contentspot
by translation＠torproject.org 18 Aug '20

18 Aug '20

commit 24a1e52ba5f564093fefbcdbaa8dfa3258004704 Author: Translation commit bot <translation(a)torproject.org> Date: Tue Aug 18 18:15:11 2020 +0000 https://gitweb.torproject.org/translation.git/commit/?h=communitytpo-conten… --- contents+ka.po | 1 + 1 file changed, 1 insertion(+) diff --git a/contents+ka.po b/contents+ka.po index 47f847d5ee..7980bfe8c5 100644 --- a/contents+ka.po +++ b/contents+ka.po @@ -3192,6 +3192,7 @@ msgstr "იხილეთ დაწვრილებით, როგორ #: (content/onion-services/overview/contents+en.lrpage.body) msgid "### Act 1: Where the onion service sets up its introduction points" msgstr "" +"### მოქმედება 1: როცა onion მომსახურება ცდილობს შემსვლელი წერტილის გამართვას" #: https//community.torproject.org/onion-services/overview/ #: (content/onion-services/overview/contents+en.lrpage.body)

1 0

[sbws/master] fix: maint: Fix linter error after merging #29294
by juga＠torproject.org 18 Aug '20

18 Aug '20

commit 4bed2ce60b93e6ff73a0f70f3626e77a7f83ef31 Author: juga0 <juga(a)riseup.net> Date: Tue Aug 11 16:25:15 2020 +0000 fix: maint: Fix linter error after merging #29294 Closes: #40011 --- scripts/maint/release.py | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/scripts/maint/release.py b/scripts/maint/release.py index b5fdf3e..17f5788 100755 --- a/scripts/maint/release.py +++ b/scripts/maint/release.py @@ -36,7 +36,6 @@ It assumes that: https://github.com/GitTools/GitVersion """ -import re import subprocess import sys try: @@ -125,7 +124,7 @@ def main(args): print("-------------------------------") print("Obtaining Gitlab tarball...") subprocess.call( - "wget https://gitlab.torproject.org/tpo/network-health/sbws/-/archive/v{}/sbws-v{… " + "wget https://gitlab.torproject.org/tpo/network-health/sbws/-/archive/v{}/sbws-v{… " # noqa "-O v{}.tar.gz" .format(release_version, release_version, release_version).split(' ') ) @@ -151,8 +150,8 @@ def main(args): "git merge --no-ff mybranch" "git push myremote master") next_branch_version = "maint{}".format(release_version) - print("And create the next prerelease branch, eg:") - "git checkout -b {}".format(next_branch_version) + print("And create the next prerelease branch, eg:" + "git checkout -b {}".format(next_branch_version)) if __name__ == "__main__":

1 0

[sbws/master] Merge branch 'maint-1.1' into master
by juga＠torproject.org 18 Aug '20

18 Aug '20

commit a37f39ae1577c87e2c9ccc6bc1ea8f88479435a9 Merge: 112f7f7 4bed2ce Author: Georg Koppen <gk(a)torproject.org> Date: Sun Aug 16 15:27:02 2020 +0000 Merge branch 'maint-1.1' into master scripts/maint/release.py | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)

1 0

[sbws/maint-1.1] fix: maint: Fix linter error after merging #29294
by juga＠torproject.org 18 Aug '20

18 Aug '20

commit 4bed2ce60b93e6ff73a0f70f3626e77a7f83ef31 Author: juga0 <juga(a)riseup.net> Date: Tue Aug 11 16:25:15 2020 +0000 fix: maint: Fix linter error after merging #29294 Closes: #40011 --- scripts/maint/release.py | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/scripts/maint/release.py b/scripts/maint/release.py index b5fdf3e..17f5788 100755 --- a/scripts/maint/release.py +++ b/scripts/maint/release.py @@ -36,7 +36,6 @@ It assumes that: https://github.com/GitTools/GitVersion """ -import re import subprocess import sys try: @@ -125,7 +124,7 @@ def main(args): print("-------------------------------") print("Obtaining Gitlab tarball...") subprocess.call( - "wget https://gitlab.torproject.org/tpo/network-health/sbws/-/archive/v{}/sbws-v{… " + "wget https://gitlab.torproject.org/tpo/network-health/sbws/-/archive/v{}/sbws-v{… " # noqa "-O v{}.tar.gz" .format(release_version, release_version, release_version).split(' ') ) @@ -151,8 +150,8 @@ def main(args): "git merge --no-ff mybranch" "git push myremote master") next_branch_version = "maint{}".format(release_version) - print("And create the next prerelease branch, eg:") - "git checkout -b {}".format(next_branch_version) + print("And create the next prerelease branch, eg:" + "git checkout -b {}".format(next_branch_version)) if __name__ == "__main__":

1 0

[translation/support-portal] https://gitweb.torproject.org/translation.git/commit/?h=support-portal
by translation＠torproject.org 18 Aug '20

18 Aug '20

commit 08a0f196b3b84b570226a19f799fe314867bafa3 Author: Translation commit bot <translation(a)torproject.org> Date: Tue Aug 18 17:48:03 2020 +0000 https://gitweb.torproject.org/translation.git/commit/?h=support-portal --- contents+ar.po | 67 +++++++++++++++++++++++++++++++++++++++++++++++++++------- 1 file changed, 59 insertions(+), 8 deletions(-) diff --git a/contents+ar.po b/contents+ar.po index 799926e362..bbbc945656 100644 --- a/contents+ar.po +++ b/contents+ar.po @@ -11257,6 +11257,7 @@ msgid "" "they assume that IP addresses equate to humans, and by banning the IP " "address they can ban the human." msgstr "" +"يفترضون أن عناوين IP تعادل البشر ، ومن خلال حظر عنوان IP يمكنهم حظر الإنسان." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11265,6 +11266,9 @@ msgid "" "the literally millions of open proxies and compromised computers around the " "Internet." msgstr "" +"في الواقع ، ليس هذا هو الحال - العديد من هؤلاء المتصيدون يستفيدون بشكل " +"روتيني من الملايين من الوكلاء المفتوحين وأجهزة الكمبيوتر المخترقة حول " +"الإنترنت." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11274,11 +11278,14 @@ msgid "" "sprung up based on this flawed security model (not unlike the antivirus " "industry)." msgstr "" +"تخوض شبكات IRC معركة خاسرة لمحاولة حظر كل هذه العقد ، وقد نشأت صناعة منزلية " +"كاملة من القوائم السوداء والمتصيدون المضادون بناءً على نموذج الأمان المعيب " +"هذا (لا يختلف عن صناعة مكافحة الفيروسات)." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) msgid "The Tor network is just a drop in the bucket here." -msgstr "" +msgstr "شبكة Tor هي مجرد قطرة في الدلو هنا." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11286,6 +11293,7 @@ msgid "" "On the other hand, from the viewpoint of IRC server operators, security is " "not an all-or-nothing thing." msgstr "" +"من ناحية أخرى ، من وجهة نظر مشغلي خوادم IRC ، فإن الأمن ليس شيئًا أو لا شيء." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11293,6 +11301,8 @@ msgid "" "By responding quickly to trolls or any other social attack, it may be " "possible to make the attack scenario less attractive to the attacker." msgstr "" +"من خلال الرد السريع على المتصيدون أو أي هجوم اجتماعي آخر ، قد يكون من الممكن" +" جعل سيناريو الهجوم أقل جاذبية للمهاجم." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11300,6 +11310,7 @@ msgid "" "And most individual IP addresses do equate to individual humans, on any " "given IRC network at any given time." msgstr "" +"ومعظم عناوين IP الفردية تساوي الأفراد ، على أي شبكة IRC معينة في أي وقت." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11307,6 +11318,7 @@ msgid "" "The exceptions include NAT gateways which may be allocated access as special" " cases." msgstr "" +"تشمل الاستثناءات بوابات NAT التي قد يتم تخصيص الوصول إليها كحالات خاصة." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11315,6 +11327,9 @@ msgid "" "generally a losing battle to keep klining a single ill-behaved IRC user " "until that user gets bored and goes away." msgstr "" +"في حين أنها معركة خاسرة لمحاولة إيقاف استخدام البروكسيات المفتوحة ، إلا أنها" +" ليست معركة خاسرة عمومًا للاستمرار في إقناع مستخدم IRC واحد سيئ السلوك حتى " +"يشعر هذا المستخدم بالملل ويذهب بعيدًا." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11322,6 +11337,9 @@ msgid "" "But the real answer is to implement application-level auth systems, to let " "in well-behaving users and keep out badly-behaving users." msgstr "" +"لكن الجواب الحقيقي هو تنفيذ أنظمة المصادقة على مستوى التطبيق ، للسماح " +"للمستخدمين الذين يتصرفون بحسن التصرف وإبعاد المستخدمين الذين يتصرفون بشكل " +"سيء." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11329,11 +11347,13 @@ msgid "" "This needs to be based on some property of the human (such as a password " "they know), not some property of the way their packets are transported." msgstr "" +"يجب أن يستند هذا إلى بعض خصائص الإنسان (مثل كلمة المرور التي يعرفونها) ، " +"وليس بعض خصائص طريقة نقل الحزم الخاصة بهم." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) msgid "Of course, not all IRC networks are trying to ban Tor nodes." -msgstr "" +msgstr "بالطبع ، ليست كل شبكات IRC تحاول حظر عقد Tor." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11341,6 +11361,8 @@ msgid "" "After all, quite a few people use Tor to IRC in privacy in order to carry on" " legitimate communications without tying them to their real-world identity." msgstr "" +"بعد كل شيء ، يستخدم عدد غير قليل من الأشخاص Tor إلى IRC في الخصوصية لمواصلة " +"الاتصالات المشروعة دون ربطهم بهويتهم الحقيقية." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11349,13 +11371,16 @@ msgid "" "millions of IPs that bad people can use is worth losing the contributions " "from the well-behaved Tor users." msgstr "" +"تحتاج كل شبكة IRC إلى أن تقرر بنفسها ما إذا كان حظر عدد قليل من ملايين " +"عناوين IP التي يمكن أن يستخدمها الأشخاص السيئون يستحق خسارة مساهمات مستخدمي " +"Tor حسن التصرف." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) msgid "" "If you're being blocked, have a discussion with the network operators and " "explain the issues to them." -msgstr "" +msgstr "إذا تم حظرك ، فناقش مع مشغلي الشبكات واشرح لهم المشكلات." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11363,6 +11388,8 @@ msgid "" "They may not be aware of the existence of Tor at all, or they may not be " "aware that the hostnames they're klining are Tor exit nodes." msgstr "" +"قد لا يكونون على علم بوجود Tor على الإطلاق ، أو قد لا يكونون على دراية بأن " +"أسماء المضيفين التي يربطونها هي عقد خروج Tor." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11371,6 +11398,8 @@ msgid "" "you may want to consider moving to a network that is more open to free " "speech." msgstr "" +"إذا قمت بشرح المشكلة ، واستنتجوا أنه يجب حظر Tor ، فقد ترغب في التفكير في " +"الانتقال إلى شبكة أكثر انفتاحًا على حرية التعبير." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11378,6 +11407,8 @@ msgid "" "Maybe inviting them to #tor on irc.oftc.net will help show them that we are " "not all evil people." msgstr "" +"ربما ستساعدهم دعوتهم إلى #tor على irc.oftc.net في إظهار أننا لسنا جميعًا " +"أشرارًا." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11388,6 +11419,10 @@ msgid "" "tracker](https://trac.torproject.org/projects/tor/wiki/doc/BlockingIrc) so " "that others can share." msgstr "" +"أخيرًا ، إذا علمت بشبكة IRC يبدو أنها تحظر Tor ، أو عقدة خروج Tor واحدة ، " +"فيرجى وضع هذه المعلومات على [أداة تعقب كتلة Tor IRC] " +"(https://trac.torproject.org/projects/tor / wiki / doc / BlockingIrc) حتى " +"يتمكن الآخرون من المشاركة." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11395,16 +11430,18 @@ msgid "" "At least one IRC network consults that page to unblock exit nodes that have " "been blocked inadvertently." msgstr "" +"تستشير شبكة IRC واحدة على الأقل تلك الصفحة لإلغاء حظر عقد الخروج التي تم " +"حظرها بدون قصد." #: https//support.torproject.org/abuse/legal-questions-about-tor-abuse/ #: (content/abuse/legal-questions/contents+en.lrquestion.title) msgid "I have legal questions about Tor abuse." -msgstr "" +msgstr "لدي أسئلة قانونية حول إساءة استخدام Tor." #: https//support.torproject.org/abuse/legal-questions-about-tor-abuse/ #: (content/abuse/legal-questions/contents+en.lrquestion.description) msgid "We're only the developers." -msgstr "" +msgstr "نحن المطورين فقط." #: https//support.torproject.org/abuse/legal-questions-about-tor-abuse/ #: (content/abuse/legal-questions/contents+en.lrquestion.description) @@ -11412,6 +11449,8 @@ msgid "" "We can answer technical questions, but we're not the ones to talk to about " "legal questions or concerns." msgstr "" +"يمكننا الإجابة على الأسئلة الفنية ، لكننا لسنا من نتحدث عن الأسئلة أو " +"المخاوف القانونية." #: https//support.torproject.org/abuse/legal-questions-about-tor-abuse/ #: (content/abuse/legal-questions/contents+en.lrquestion.description) @@ -11421,11 +11460,14 @@ msgid "" "legal-faq/), and contact EFF directly if you have any further legal " "questions." msgstr "" +"يرجى إلقاء نظرة على [الأسئلة الشائعة حول Tor القانونية] " +"(https://community.torproject.org/relay/community-resources/eff-tor-legal-" +"faq/) ، والاتصال بـ EFF مباشرةً إذا كان لديك أي أسئلة قانونية أخرى." #: https//support.torproject.org/abuse/nodes-banned-from-mail-server/ #: (content/abuse/mail-server-ban/contents+en.lrquestion.title) msgid "Your nodes are banned from the mail server I want to use." -msgstr "" +msgstr "عُقدك ممنوعة من خادم البريد الذي أريد استخدامه." #: https//support.torproject.org/abuse/nodes-banned-from-mail-server/ #: (content/abuse/mail-server-ban/contents+en.lrquestion.description) @@ -11435,6 +11477,11 @@ msgid "" " are evil — they attempt to strong-arm network administrators on policy, " "service, and routing issues, and then extract ransoms from victims." msgstr "" +"على الرغم من أن [Tor ليس مفيدًا في إرسال الرسائل غير المرغوب فيها] (/ abuse " +"/ what-about-spammers /) ، يبدو أن بعض القائمين على القائمة السوداء " +"المتحمسين يعتقدون أن جميع الشبكات المفتوحة مثل Tor شريرة - فهم يحاولون تقوية" +" مدراء الشبكات فيما يتعلق بالسياسة ، والخدمة ، والتوجيه ، ثم انتزاع الفدية " +"من الضحايا." #: https//support.torproject.org/abuse/nodes-banned-from-mail-server/ #: (content/abuse/mail-server-ban/contents+en.lrquestion.description) @@ -11449,7 +11496,7 @@ msgstr "" #: https//support.torproject.org/abuse/remove-content-from-onion-address/ #: (content/abuse/remove-content/contents+en.lrquestion.title) msgid "I want some content removed from a .onion address." -msgstr "" +msgstr "أريد إزالة بعض المحتوى من عنوان .onion." #: https//support.torproject.org/abuse/remove-content-from-onion-address/ #: (content/abuse/remove-content/contents+en.lrquestion.description) @@ -11457,6 +11504,8 @@ msgid "" "The Tor Project does not host, control, nor have the ability to discover the" " owner or location of a .onion address." msgstr "" +"لا يستضيف Tor Project أو يتحكم أو يمتلك القدرة على اكتشاف مالك أو موقع عنوان" +" .onion." #: https//support.torproject.org/abuse/remove-content-from-onion-address/ #: (content/abuse/remove-content/contents+en.lrquestion.description) @@ -11464,11 +11513,13 @@ msgid "" "The .onion address is an address from [an onion service](https://tb-" "manual.torproject.org/onion-services/)" msgstr "" +"عنوان .onion هو عنوان من [an onion service](https://tb-" +"manual.torproject.org/onion-services/)" #: https//support.torproject.org/abuse/remove-content-from-onion-address/ #: (content/abuse/remove-content/contents+en.lrquestion.description) msgid "The name you see ending in .onion is an onion service descriptor." -msgstr "" +msgstr "الاسم الذي تراه ينتهي بـ .onion هو واصف خدمة onion." #: https//support.torproject.org/abuse/remove-content-from-onion-address/ #: (content/abuse/remove-content/contents+en.lrquestion.description)

1 0

[translation/support-portal] https://gitweb.torproject.org/translation.git/commit/?h=support-portal
by translation＠torproject.org 18 Aug '20

18 Aug '20

commit 7a84d5d3eff6713212cb09313b6e6c1db7513d9f Author: Translation commit bot <translation(a)torproject.org> Date: Tue Aug 18 17:18:00 2020 +0000 https://gitweb.torproject.org/translation.git/commit/?h=support-portal --- contents+ar.po | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/contents+ar.po b/contents+ar.po index 84669ddaa2..799926e362 100644 --- a/contents+ar.po +++ b/contents+ar.po @@ -11198,7 +11198,7 @@ msgstr "" #: https//support.torproject.org/abuse/tor-ip-for-legal-case/ #: (content/abuse/ip-legal-case/contents+en.lrquestion.title) msgid "I have questions about a Tor IP address for a legal case." -msgstr "" +msgstr "لدي أسئلة حول عنوان IP الخاص بـ Tor لقضية قانونية." #: https//support.torproject.org/abuse/tor-ip-for-legal-case/ #: (content/abuse/ip-legal-case/contents+en.lrquestion.description) @@ -11209,6 +11209,10 @@ msgid "" "directory](https://blog.torproject.org/blog/start-tor-legal-support-" "directory) of people who may be able to help you." msgstr "" +"يرجى قراءة [الأسئلة الشائعة القانونية التي كتبها محامو EFF] " +"(https://community.torproject.org/relay/community-resources/eff-tor-legal-" +"faq/). يوجد [دليل قانوني] متزايد (https://blog.torproject.org/blog/start-" +"tor-legal-support-directory) من الأشخاص الذين قد يكونون قادرين على مساعدتك." #: https//support.torproject.org/abuse/tor-ip-for-legal-case/ #: (content/abuse/ip-legal-case/contents+en.lrquestion.description) @@ -11218,16 +11222,20 @@ msgid "" "tool](https://exonerator.torproject.org/) to query the historic Tor relay " "lists and get an answer." msgstr "" +"إذا كنت بحاجة إلى التحقق مما إذا كان عنوان IP معين يعمل كعقدة خروج Tor في " +"تاريخ ووقت معينين ، فيمكنك استخدام [أداة ExoneraTor] " +"(https://exonerator.torproject.org/) للاستعلام عن مرحل Tor التاريخي قوائم " +"والحصول على إجابة." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.title) msgid "Tor is banned from the IRC network I want to use." -msgstr "" +msgstr "تم حظر Tor من شبكة IRC التي أريد استخدامها." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) msgid "Sometimes jerks make use of Tor to troll IRC channels." -msgstr "" +msgstr "في بعض الأحيان ، يستفيد الحمقى من Tor للتنصت على قنوات IRC." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11235,11 +11243,13 @@ msgid "" "This abuse results in IP-specific temporary bans (\"klines\" in IRC lingo), " "as the network operators try to keep the troll off of their network." msgstr "" +"ينتج عن إساءة الاستخدام هذه عمليات حظر مؤقتة خاصة بـ IP (\"klines\" في لغة " +"IRC) ، حيث يحاول مشغلو الشبكات إبعاد المتصيد عن شبكتهم." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) msgid "This response underscores a fundamental flaw in IRC's security model:" -msgstr "" +msgstr "تؤكد هذه الاستجابة على وجود خلل أساسي في نموذج أمان IRC:" #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description)

1 0

[torspec/master] Demonstrate how to remove MAPADDRESS entries
by dgoulet＠torproject.org 18 Aug '20

18 Aug '20

commit b443bc3603cc7b5d6e492b955fafc744ade54f04 Author: Damian Johnson <atagar(a)torproject.org> Date: Fri Aug 14 16:07:39 2020 -0700 Demonstrate how to remove MAPADDRESS entries Our docs accurately describe how to remove MAPADDRESS entries, but doesn't demonstrate it. Exemplifying how to query our mappings and remove them. https://gitlab.torproject.org/tpo/core/tor/-/issues/40104 --- control-spec.txt | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/control-spec.txt b/control-spec.txt index e338d79..a5eaeee 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -516,9 +516,19 @@ Example: - C: MAPADDRESS 0.0.0.0=torproject.org 1.2.3.4=tor.freehaven.net - S: 250-127.192.10.10=torproject.org - S: 250 1.2.3.4=tor.freehaven.net + C: MAPADDRESS 1.2.3.4=torproject.org + S: 250 1.2.3.4=torproject.org + + C: GETINFO address-mappings/control + S: 250-address-mappings/control=1.2.3.4 torproject.org NEVER + S: 250 OK + + C: MAPADDRESS 1.2.3.4=1.2.3.4 + S: 250 1.2.3.4=1.2.3.4 + + C: GETINFO address-mappings/control + S: 250-address-mappings/control= + S: 250 OK {Note: This feature is designed to be used to help Tor-ify applications that need to use SOCKS4 or hostname-less SOCKS5. There are three

1 0

[tor/master] Merge branch 'tor-gitlab/mr/126'
by dgoulet＠torproject.org 18 Aug '20

18 Aug '20

commit 1089ac6f2275e5d6b62debb5dd05a936fdbad6a7 Merge: 80d2376f33 563f8610fd Author: David Goulet <dgoulet(a)torproject.org> Date: Tue Aug 18 08:56:27 2020 -0400 Merge branch 'tor-gitlab/mr/126' changes/ticket40101 | 3 +++ doc/HACKING/CircuitPaddingDevelopment.md | 14 ++++++------- doc/HACKING/CircuitPaddingQuickStart.md | 36 ++++++++++++++++---------------- doc/HACKING/Fuzzing.md | 2 +- doc/HACKING/GettingStarted.md | 11 +++++----- doc/HACKING/ReleasingTor.md | 2 +- doc/TUNING | 15 +++++++------ doc/man/tor.1.txt | 8 +++---- src/app/config/app_config.md | 3 +-- src/app/config/config.c | 4 ++-- src/core/or/circuitbuild.c | 2 +- src/core/or/circuitlist.c | 2 +- src/feature/relay/relay_config.c | 2 +- src/feature/relay/router.c | 2 +- src/lib/string/compat_string.h | 2 +- src/test/test_options.c | 2 +- 16 files changed, 56 insertions(+), 54 deletions(-)

1 0

[tor/master] Revise trac.torproject.org urls to refer to gitlab replacements.
by dgoulet＠torproject.org 18 Aug '20

18 Aug '20

commit 563f8610fd7471bd564b0f2e81223d7eb2e64da0 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Aug 14 09:21:02 2020 -0400 Revise trac.torproject.org urls to refer to gitlab replacements. Closes #40101. --- changes/ticket40101 | 3 +++ doc/HACKING/CircuitPaddingDevelopment.md | 14 ++++++------- doc/HACKING/CircuitPaddingQuickStart.md | 36 ++++++++++++++++---------------- doc/HACKING/Fuzzing.md | 2 +- doc/HACKING/GettingStarted.md | 11 +++++----- doc/HACKING/ReleasingTor.md | 2 +- doc/TUNING | 15 +++++++------ doc/man/tor.1.txt | 8 +++---- src/app/config/app_config.md | 3 +-- src/app/config/config.c | 4 ++-- src/core/or/circuitbuild.c | 2 +- src/core/or/circuitlist.c | 2 +- src/feature/relay/relay_config.c | 2 +- src/feature/relay/router.c | 2 +- src/lib/string/compat_string.h | 2 +- src/test/test_options.c | 2 +- 16 files changed, 56 insertions(+), 54 deletions(-) diff --git a/changes/ticket40101 b/changes/ticket40101 new file mode 100644 index 0000000000..7af42b9499 --- /dev/null +++ b/changes/ticket40101 @@ -0,0 +1,3 @@ + o Documentation: + - Replace URLs from our old bugtracker so that they refer to the + new bugtracker and wiki. Closes ticket 40101. diff --git a/doc/HACKING/CircuitPaddingDevelopment.md b/doc/HACKING/CircuitPaddingDevelopment.md index a4e65697b8..1344ebd3d8 100644 --- a/doc/HACKING/CircuitPaddingDevelopment.md +++ b/doc/HACKING/CircuitPaddingDevelopment.md @@ -156,7 +156,7 @@ it). This document focuses primarily on the circuit padding framework's cover traffic features, and will only briefly touch on the potential obfuscation and -application layer coupling points of the framework. Explicit layer coupling +application layer coupling points of the framework. Explicit layer coupling points can be created by adding either new [machine application events](#62-machine-application-events) or new [internal machine events](#63-internal-machine-events) to the circuit padding framework, so that @@ -178,7 +178,7 @@ Most importantly: this framing allows cover traffic defenses to be modeled as an optimization problem search space, expressed as fields of a C structure (which is simultaneously a compact opaque bitstring as well as a symbolic vector in an abstract feature space). This kind of space is particularly well -suited to search by gradient descent, GAs, and GANs. +suited to search by gradient descent, GAs, and GANs. When performing this optimization search, each padding machine should have a fitness function, which will allow two padding machines to be compared for @@ -186,7 +186,7 @@ relative effectiveness. Optimization searches work best if this fitness can be represented as a single number, for example the total amount by which it reduces the [Balanced Accuracy](https://en.wikipedia.org/wiki/Precision_and_recall#Imbalanced_Dat… -of an adversary's classifier, divided by an amount of traffic overhead. +of an adversary's classifier, divided by an amount of traffic overhead. Before you begin the optimization phase for your defense, you should also carefully consider the [features and @@ -1024,11 +1024,11 @@ would gladly accept patches that do so. The following list gives an overview of these improvements, but as this document ages, it may become stale. The canonical list of improvements that -researchers may find useful is tagged in our bugtracker with -[circpad-researchers](https://trac.torproject.org/projects/tor/query?keywords=~circpad-researchers), +researchers may find useful is labeled in our bugtracker with +[Padding Research](https://gitlab.torproject.org/tpo/core/tor/-/issues?scope=all&utf…, and the list of improvements that are known to be necessary for some research -areas are tagged with -[circpad-researchers-want](https://trac.torproject.org/projects/tor/query?keywords=~circpad-researchers-want). +areas are labeled with +[Padding Research Requires](https://gitlab.torproject.org/tpo/core/tor/-/issues?scope=all&utf…. Please consult those lists for the latest status of these issues. Note that not all fixes will be backported to all Tor versions, so be mindful of which diff --git a/doc/HACKING/CircuitPaddingQuickStart.md b/doc/HACKING/CircuitPaddingQuickStart.md index 2b01dae074..25bf05048c 100644 --- a/doc/HACKING/CircuitPaddingQuickStart.md +++ b/doc/HACKING/CircuitPaddingQuickStart.md @@ -7,7 +7,7 @@ circuit padding framework from scratch. Notes were taken as part of porting [Adaptive Padding Early (APE)](https://www.cs.kau.se/pulls/hot/thebasketcase-ape/) from basket2 to the circuit padding framework. The goal is just to document the process and provide -useful pointers along the way, not create a useful machine. +useful pointers along the way, not create a useful machine. The quick and dirty plan is to: 1. clone and compile tor @@ -29,7 +29,7 @@ fixes that have since been merged to origin/master. If you need the newest framework features, you should use that master instead. ```console -$ sh autogen.sh +$ sh autogen.sh $ ./configure $ make ``` @@ -73,7 +73,7 @@ We have one more step left before we move on the machine: configure TB to always use our middle relay. Edit `Browser/TorBrowser/Data/Tor/torrc` and set `MiddleNodes <fingerprint>`, where `<fingerprint>` is the fingerprint of the relay. Start TB, visit a website, and manually confirm that the middle is used -by looking at the circuit display. +by looking at the circuit display. ## Add a bare-bones APE padding machine @@ -89,10 +89,10 @@ might be broken in the future, just search for the headings): [circuitpadding_machines.h](https://gitweb.torproject.org/tor.git/tree/src/c…. Please consult the above links for details. Moving forward, the focus is to -describe what was done, not necessarily explaining all the details why. +describe what was done, not necessarily explaining all the details why. Since we plan to make changes to tor, create a new branch `git checkout -b -circuit-padding-ape-machine tor-0.4.1.5`. +circuit-padding-ape-machine tor-0.4.1.5`. We start with declaring two functions, one for the machine at the client and one at the relay, in `circuitpadding_machines.h`: @@ -107,8 +107,8 @@ The definitions go into `circuitpadding_machines.c`: ```c /**************** Adaptive Padding Early (APE) machine ****************/ -/** - * Create a relay-side padding machine based on the APE design. +/** + * Create a relay-side padding machine based on the APE design. */ void circpad_machine_relay_wf_ape(smartlist_t *machines_sl) @@ -137,14 +137,14 @@ circpad_machine_relay_wf_ape(smartlist_t *machines_sl) // register the machine relay_machine->machine_num = smartlist_len(machines_sl); circpad_register_padding_machine(relay_machine, machines_sl); - + log_info(LD_CIRC, "Registered relay WF APE padding machine (%u)", relay_machine->machine_num); } -/** - * Create a client-side padding machine based on the APE design. +/** + * Create a client-side padding machine based on the APE design. */ void circpad_machine_client_wf_ape(smartlist_t *machines_sl) @@ -191,13 +191,13 @@ circpad_machine_client_wf_ape(origin_padding_machines); circpad_machine_relay_wf_ape(relay_padding_machines); ``` -We run `make` to get a new `tor` binary and copy it to our local TB. +We run `make` to get a new `tor` binary and copy it to our local TB. ## Run the machine To be able to view circuit info events in the console as we launch TB, we add `Log -[circ]info notice stdout` to `torrc` of TB. +[circ]info notice stdout` to `torrc` of TB. Running TB to visit example.com we first find in the log: @@ -224,13 +224,13 @@ Aug 30 18:36:55.000 [info] circpad_handle_padding_negotiated(): Middle node did We see that our middle support padding (since we upgraded to tor-0.4.1.5), that we attempt to negotiate, our machine starts on the client, transitions to the end state, and is freed. The last line shows that the middle doesn't have a -padding machine that can run. +padding machine that can run. Next, we follow the same steps as earlier and replace the modified `tor` at our middle relay. We don't update the logging there to avoid logging on the info level on the live network. Looking at the client log again we see that negotiation works as before except for the last line: it's missing, so the -machine is running at the middle as well. +machine is running at the middle as well. ## Implementing the APE state machine @@ -239,14 +239,14 @@ more machines (for the receive portion of WTFP-PAD, beyond AP), and pick reasonable parameters for the distributions (I completely winged it now, as when implementing APE). The [circuit-padding-ape-machine branch](https://github.com/pylls/tor/tree/circuit-padding-ape-machine) contains -the commits for the full machines with plenty of comments. +the commits for the full machines with plenty of comments. Some comments on the process: -- `tor-0.4.1.5` does not support two machines on the same circuit, the following - fix has to be made: https://trac.torproject.org/projects/tor/ticket/31111 . +- `tor-0.4.1.5` did not support two machines on the same circuit, the following + fix had to be made: https://bugs.torproject.org/tpo/core/tor/31111 . The good news is that everything else seems to work after the small change in - the fix. + the fix. - APE randomizes its distributions. Currently, this can only be done during start of `tor`. This makes sense in the censorship circumvention setting (`obfs4`), less so for WF defenses: further randomizing each circuit is likely diff --git a/doc/HACKING/Fuzzing.md b/doc/HACKING/Fuzzing.md index d9e133008a..1a9185aebf 100644 --- a/doc/HACKING/Fuzzing.md +++ b/doc/HACKING/Fuzzing.md @@ -130,4 +130,4 @@ $ src/test/fuzz/fuzz-http --debug < /path/to/test.case Please report any issues discovered using the process in Tor's security issue policy: -https://trac.torproject.org/projects/tor/wiki/org/meetings/2016SummerDevMeeting/Notes/SecurityIssuePolicy +https://gitlab.torproject.org/tpo/core/team/-/wikis/NetworkTeam/SecurityPolicy diff --git a/doc/HACKING/GettingStarted.md b/doc/HACKING/GettingStarted.md index ee3da10a4b..6d61be9881 100644 --- a/doc/HACKING/GettingStarted.md +++ b/doc/HACKING/GettingStarted.md @@ -71,10 +71,11 @@ Once you've reached this point, here's what you need to know. Many people have gotten started by looking for an area where they personally felt Tor was underperforming, and investigating ways to fix it. If you're looking for ideas, you can head to - [trac](https://trac.torproject.org) our bug tracking tool and look for - tickets that have received the "easy" tag: these are ones that developers + [gitlab](https://gitlab.torproject.org) our bug tracking tool and look for + tickets that have received the "First Contribution" label: these are ones + that developers think would be pretty simple for a new person to work on. For a bigger - challenge, you might want to look for tickets with the "lorax" + challenge, you might want to look for tickets with the "Project Ideas" keyword: these are tickets that the developers think might be a good idea to build, but which we have no time to work on any time soon. @@ -140,10 +141,10 @@ Once you've reached this point, here's what you need to know. 8. Submitting your patch We review patches through tickets on our bugtracker at - [trac](https://trac.torproject.org). You can either upload your patches there, or + [gitlab](https://gitlab.torproject.org). You can either upload your patches there, or put them at a public git repository somewhere we can fetch them (like gitlab, github or bitbucket) and then paste a link on the appropriate - trac ticket. + ticket. Once your patches are available, write a short explanation of what you've done on trac, and then change the status of the ticket to diff --git a/doc/HACKING/ReleasingTor.md b/doc/HACKING/ReleasingTor.md index 6513583ec5..24b66a069a 100644 --- a/doc/HACKING/ReleasingTor.md +++ b/doc/HACKING/ReleasingTor.md @@ -215,7 +215,7 @@ $ git push origin tag tor-0.4.x.y-<status> can vary. For templates to use when announcing, see: - https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/Announc… + https://gitlab.torproject.org/tpo/core/team/-/wikis/NetworkTeam/Announcemen… ## V. Aftermath and cleanup diff --git a/doc/TUNING b/doc/TUNING index 24552a38cb..7da37e1adc 100644 --- a/doc/TUNING +++ b/doc/TUNING @@ -1,13 +1,13 @@ -Most operating systems limit an amount of TCP sockets that can be used +Most operating systems limit an amount of TCP sockets that can be used simultaneously. It is possible for a busy Tor relay to run into these -limits, thus being unable to fully utilize the bandwidth resources it +limits, thus being unable to fully utilize the bandwidth resources it has at its disposal. Following system-specific tips might be helpful to alleviate the aforementioned problem. Linux ----- -Use 'ulimit -n' to raise an allowed number of file descriptors to be +Use 'ulimit -n' to raise an allowed number of file descriptors to be opened on your host at the same time. FreeBSD @@ -17,7 +17,7 @@ Tune the followind sysctl(8) variables: * kern.maxfiles - maximum allowed file descriptors (for entire system) * kern.maxfilesperproc - maximum file descriptors one process is allowed to use - * kern.ipc.maxsockets - overall maximum numbers of sockets for entire + * kern.ipc.maxsockets - overall maximum numbers of sockets for entire system * kern.ipc.somaxconn - size of listen queue for incoming TCP connections for entire system @@ -31,8 +31,8 @@ Mac OS X Since Mac OS X is BSD-based system, most of the above hold for OS X as well. However, launchd(8) is known to modify kern.maxfiles and kern.maxfilesperproc -when it launches tor service (see launchd.plist(5) manpage). Also, -kern.ipc.maxsockets is determined dynamically by the system and thus is +when it launches tor service (see launchd.plist(5) manpage). Also, +kern.ipc.maxsockets is determined dynamically by the system and thus is read-only on OS X. OpenBSD @@ -79,8 +79,7 @@ Disclaimer Do note that this document is a draft and above information may be technically incorrect and/or incomplete. If so, please open a ticket -on https://trac.torproject.org or post to tor-relays mailing list. +on https://gitlab.torproject.org or post to tor-relays mailing list. Are you running a busy Tor relay? Let us know how you are solving the out-of-sockets problem on your system. - diff --git a/doc/man/tor.1.txt b/doc/man/tor.1.txt index e8dcc7b236..4b37548b07 100644 --- a/doc/man/tor.1.txt +++ b/doc/man/tor.1.txt @@ -211,9 +211,9 @@ backslash character (\) before the end of the line. Comments can be used in such multiline entries, but they must start at the beginning of a line. Configuration options can be imported from files or folders using the %include -option with the value being a path. This path can have wildcards. Wildcards are -expanded first, then sorted using lexical order. Then, for each matching file or -folder, the following rules are followed: if the path is a file, the options from +option with the value being a path. This path can have wildcards. Wildcards are +expanded first, then sorted using lexical order. Then, for each matching file or +folder, the following rules are followed: if the path is a file, the options from the file will be parsed as if they were written where the %include option is. If the path is a folder, all files on that folder will be parsed following lexical order. Files starting with a dot are ignored. Files in subfolders are ignored. @@ -3854,7 +3854,7 @@ https://spec.torproject.org. See also **torsocks**(1) and **torify**(1). == BUGS Because Tor is still under development, there may be plenty of bugs. Please -report them at https://trac.torproject.org/. +report them at https://bugs.torproject.org/. == AUTHORS diff --git a/src/app/config/app_config.md b/src/app/config/app_config.md index b359ce77f6..96a55494ff 100644 --- a/src/app/config/app_config.md +++ b/src/app/config/app_config.md @@ -2,5 +2,4 @@ @brief app/config: Top-level configuration code Refactoring this module is a work in progress, see -[ticket 29211](https://trac.torproject.org/projects/tor/ticket/29211). - +[ticket 29211](https://bugs.torproject.org/tpo/core/tor/29211) diff --git a/src/app/config/config.c b/src/app/config/config.c index 23f280891b..b5ea8fcd71 100644 --- a/src/app/config/config.c +++ b/src/app/config/config.c @@ -3458,7 +3458,7 @@ options_validate_cb(const void *old_options_, void *options_, char **msg) "configured. This is bad because it's very easy to locate your " "entry guard which can then lead to the deanonymization of your " "hidden service -- for more details, see " - "https://trac.torproject.org/projects/tor/ticket/14917. " + "https://bugs.torproject.org/tpo/core/tor/14917. " "For this reason, the use of one EntryNodes with an hidden " "service is prohibited until a better solution is found."); return -1; @@ -3475,7 +3475,7 @@ options_validate_cb(const void *old_options_, void *options_, char **msg) "be harmful to the service anonymity. Because of this, we " "recommend you either don't do that or make sure you know what " "you are doing. For more details, please look at " - "https://trac.torproject.org/projects/tor/ticket/21155."); + "https://bugs.torproject.org/tpo/core/tor/21155."); } /* Single Onion Services: non-anonymous hidden services */ diff --git a/src/core/or/circuitbuild.c b/src/core/or/circuitbuild.c index 76e9ccf0a5..ab4ce9f784 100644 --- a/src/core/or/circuitbuild.c +++ b/src/core/or/circuitbuild.c @@ -2148,7 +2148,7 @@ count_acceptable_nodes, (const smartlist_t *nodes, int direct)) * The alternative is building the circuit in reverse. Reverse calls to * onion_extend_cpath() (ie: select outer hops first) would then have the * property that you don't gain information about inner hops by observing - * outer ones. See https://trac.torproject.org/projects/tor/ticket/24487 + * outer ones. See https://bugs.torproject.org/tpo/core/tor/24487 * for this. * * (Note further that we still exclude the exit to prevent A - B - A diff --git a/src/core/or/circuitlist.c b/src/core/or/circuitlist.c index c0c28c9e2d..c31fe00dea 100644 --- a/src/core/or/circuitlist.c +++ b/src/core/or/circuitlist.c @@ -2144,7 +2144,7 @@ circuit_mark_all_dirty_circs_as_unusable(void) * This function is in the critical path of circuit_mark_for_close(). * It must be (and is) O(1)! * - * See https://trac.torproject.org/projects/tor/ticket/23512. + * See https://bugs.torproject.org/tpo/core/tor/23512 */ void circuit_synchronize_written_or_bandwidth(const circuit_t *c, diff --git a/src/feature/relay/relay_config.c b/src/feature/relay/relay_config.c index d3f904d286..6504c680eb 100644 --- a/src/feature/relay/relay_config.c +++ b/src/feature/relay/relay_config.c @@ -1037,7 +1037,7 @@ options_validate_relay_mode(const or_options_t *old_options, "Tor is currently configured as a relay and a hidden service. " "That's not very secure: you should probably run your hidden service " "in a separate Tor process, at least -- see " - "https://trac.torproject.org/8742"); + "https://bugs.torproject.org/tpo/core/tor/8742."); if (options->BridgeRelay && options->DirPort_set) { log_warn(LD_CONFIG, "Can't set a DirPort on a bridge relay; disabling " diff --git a/src/feature/relay/router.c b/src/feature/relay/router.c index 675b977ade..9bf0e7026f 100644 --- a/src/feature/relay/router.c +++ b/src/feature/relay/router.c @@ -176,7 +176,7 @@ routerinfo_err_is_transient(int err) /** * For simplicity, we consider all errors other than * "not a server" transient - see discussion on - * https://trac.torproject.org/projects/tor/ticket/27034 + * https://bugs.torproject.org/tpo/core/tor/27034. */ return err != TOR_ROUTERINFO_ERROR_NOT_A_SERVER; } diff --git a/src/lib/string/compat_string.h b/src/lib/string/compat_string.h index f05265bdcc..5c9bf05ebd 100644 --- a/src/lib/string/compat_string.h +++ b/src/lib/string/compat_string.h @@ -42,7 +42,7 @@ static inline int strcasecmp(const char *a, const char *b) { * (If --enable-fragile-hardening is passed to configure, we use the hardened * variants, which do not suffer from this issue.) * - * See https://trac.torproject.org/projects/tor/ticket/15205 + * See https://bugs.torproject.org/tpo/core/tor/15205. */ #undef strlcat #undef strlcpy diff --git a/src/test/test_options.c b/src/test/test_options.c index 8e0d19f126..714ee4767f 100644 --- a/src/test/test_options.c +++ b/src/test/test_options.c @@ -1013,7 +1013,7 @@ test_options_validate__relay_with_hidden_services(void *ignored) "Tor is currently configured as a relay and a hidden service. " "That's not very secure: you should probably run your hidden servi" "ce in a separate Tor process, at least -- see " - "https://trac.torproject.org/8742\n"); + "https://bugs.torproject.org/tpo/core/tor/8742.\n"); done: teardown_capture_of_logs();

1 0