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

Add validation checks to protect injection into top level #465

Open
cmungall opened this issue Nov 22, 2018 · 0 comments
Open

Add validation checks to protect injection into top level #465

cmungall opened this issue Nov 22, 2018 · 0 comments

Comments

@cmungall
Copy link
Contributor

Continuing discussion from #463

Experiment here: #464 (I didn't merge, so it's possible that this was actually safe)

Currently it seems possible to inject anything into the top level. Of course we'd never merge such a request but for long term maintenance we should make this a check.

First we should define the rules of what are allowed on the top level. I can see a spectrum:

  1. myont.{obo,owl,json}[.gz]
  2. myont.*
  3. myont-.

I would opt for 2. ie. people "own" everything after a period or slash

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant