Add topic about "Streangthening the security"
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker
- Domain
- documentation, security
Research direction
Start with the DITA-OT user's manual and the linked using Docker images topic to understand the existing guidance. Define the security topic's scope around vetted plugins, input/temp/output folder boundaries, server-side job limits, trusted content, and isolation; done means the guidance is added without leaving these concerns unresolved.
Written by the indexing model from the issue text.
Description
Description
From the DITA OT meetup discussion, Jarno may do some code changes in the DITA OT to have it avoid reading/writing content from outside the input/output folders but he cannot stop plugins from doing this.
Possible Solution
Maybe we should have a topic in the user's manual about "Streangthening the security".
Maybe tell people that they should properly check and vet all plugins bundled in the DITA OT.
Maybe tell that as the DITA OT reads content and then writes the published output they should take care to properly define the input, temp and output folders so that they do not overwrite other files.
Maybe say that if you are running DITA OT on the server side you should also avoid hogging the CPU by running too many instances at the same time or allowing the same user to post too many jobs, so have some kind of jobs executor and avoid running too many DITA OTs in parallel.
Maybe say that the content processed by the DITA OT should come from reliable people to avoid attacks based on the parsers used to parse the input content.
Maybe say that the best way to isolate the DITA OT so that it never writes or reads content from the outside would be to run it in a container like docker:
https://www.dita-ot.org/dev/topics/using-docker-images#ariaid-title1
@jelovirt if you have any ideas here?
- Dominant language
- XSLT
- Stars
- 64
- Forks
- 102
- Avg merge
- 14h 50m
- Merged PRs (30d)
- 1
Contributor 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 dita-ot/docs
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
coverage feature
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·