collective / collective/rapido.core
existing methods of whitelisting modules don't work.
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Methods for whitelisting that used to work on pythonscripts don't seem to work with rapido (zope.untrustedpython) code.
There seems to be no way currently to allow marking a module as safe for import in rapido.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reading the linked Zope Security documentation, then trace how rapido handles zope.untrustedpython imports and module whitelisting. The work is done when a module can be safely marked for import in rapido using the documented whitelisting approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100