Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Use of copyrighted material without permission or consent] #129

Open
RubenVerborgh opened this issue Dec 4, 2019 · 3 comments
Open

[Use of copyrighted material without permission or consent] #129

RubenVerborgh opened this issue Dec 4, 2019 · 3 comments

Comments

@RubenVerborgh
Copy link
Contributor

RubenVerborgh commented Dec 4, 2019

No description provided.

@michielbdejong
Copy link
Contributor

If you create C/R and C/ gets created on the fly (transparently), then the information about whether C/ existed beforehand stays more hidden, not less hidden?

@csarven
Copy link
Member

csarven commented Feb 18, 2025

Reopening the issue as it was closed by a non-CG member at the time, without CG's consent. The last useful revision in #139 (comment) is below, before the comment was erased.


This is a security follow-up on #68.

Servers are allowed to use 404 for 2 cases:

  1. when a resource does not exist
  2. when it does not want to acknowledge whether a resource exists

In #68, the current resolution is to automatically create intermediate containers as needed when a deeper document is created through PATCH (and perhaps other methods). In that case, success or failure of that operation might leak information in case 2 above.

@csarven csarven reopened this Feb 18, 2025
@csarven
Copy link
Member

csarven commented Feb 18, 2025

GitHub's ToS allow users to reference and reuse publicly available comments within GitHub (see Section D.5). And, the Solid GitHub org operates under an MIT license, promoting open collaboration and transparency. Additionally, as part of the Solid CG, contributions fall under the W3C Community Group CLA, which permits broad reuse within the community.

@RubenVerborgh RubenVerborgh changed the title Does recursive container creation leak information? [Use of copyrighted material without permission or consent] Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants