possible #1615 solution: partial wildcard allowed-origins, with just … #1623
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…protocol specified (for example "http://*") could use glob ** pattern in order to match any sequence of characters (even the separator).
Signed-off-by: Aterocana <dominicimauriziogmail.com>
Related issue
@aeneasr
as discussed in #1615 I'm proposing this fix.Proposed changes
Basically I think the issue here is the protocol is specified, but no domain is: for example https://*.
Internally glob.Glob is compiled (with glob.Compile) with the provided string and
'.'
rune separator. Sinceg:=glob.Compile("https://*", '.')
doesn't matchg.Match("http://foobar.com")
due to.
separator, we could useg:=glob.Compile("https://**", '.') to ignore
.` separator in this specific case.In order to do so I simply tried to match if "://" substring is into an allowed-origin string.
Checklist
vulnerability, I confirm that I got green light (please contact security@ory.sh) from the maintainers to push the changes.
Further comments