Security hardening not on Python bridge documentation
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation, security
Research direction
Compare the Go bridge setup with the Python bridge setup shown in the issue, starting with the hardening lines highlighted in the attached image. Determine whether those settings are required for Python bridges; done means the documentation clearly answers that question and includes the relevant guidance if applicable.
Written by the indexing model from the issue text.
Description
Hi, I'm unsure if this is an issue in the documentation per se or a question.
Is there a reason why these hardening lines are only in the Go bridge setup but not on the Python one?
(a) Is this only inherently necessary for Go bridges? (If the answer is yes, then my post is a question)
(b) Would these lines be good to add in the Python bridges too? (if the answer is yes, then my post is an issue in the documentation that could be patched)
- Dominant language
- Markdown
- Stars
- 81
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mautrix/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
/reject -> crashOpen
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Similar issues
-
area:docs good first issue P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
uttrflow/uttrflow-swift#3445 ·
Maintainers usually reply within 1 day
-
adr
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kristofdegrave/homeassistant-smart-charging#1607 ·
Maintainers usually reply within 1 day
-
Feature
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Narezzurri/OpenVPN-Config-Manager#95 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
doc good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
collective/icalendar#1865 · 2 comments ·
Maintainers usually reply within 1 day