Does recursive container creation leak information?
Open
Nobody has claimed this yet.
doc: Protocol
topic: accessibility
topic: security privacy cryptography
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
This issue has no description.
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.
Research direction
No files, tests, reproduction steps, or entry points are named in the issue. Start by reviewing the three-comment thread and the specification's recursive container creation section; done means establishing whether information is leaked and recording a clear resolution in the specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100