-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
registry/handles/app: always append default urls regexps #2035
Conversation
Current coverage is 51.10% (diff: 100%)@@ master #2035 diff @@
==========================================
Files 128 128
Lines 11402 11404 +2
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
- Hits 6822 5828 -994
- Misses 3714 4825 +1111
+ Partials 866 751 -115
|
Hi @runcom - I feel like I'm missing some context here. Why should foreign layer URLs be prohibited when validation is disabled? It seems a bit counter-intuitive. |
I know, but we didn't want default installation to allow layers urls, did we? |
I wonder why validation is not enabled by default. |
I don't have any clue, great question. |
does anyone have any idea on @aaronlehmann thought? |
So this change is effectively changing the default behavior from support
I also don't know if this was an intentional decision, can ping @stevvooe as well. Either way let's make that decision now. I think I agree that it is better to be more restrictive by default with foreign URLs since it has the potential for malicious use. |
@@ -244,6 +244,8 @@ func NewApp(ctx context.Context, config *configuration.Configuration) *App { | |||
options = append(options, storage.ManifestURLsDenyRegexp(re)) | |||
} | |||
} | |||
} else { | |||
options = append(options, storage.ManifestURLsAllowRegexp(regexp.MustCompile("^$"))) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn't realize we just plopped all this in the middle of a function. Sigh.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we refactor this later but at least agree on whether we should make this change or not....
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@runcom I'm just lamenting. Let's not make big changes in this PR.
@dmcgowan @runcom The backwards compatibility policy would dictate that we continue to be relaxed about extra fields. Let's introduce a
There may be a way to simplify that... |
9ec2a07
to
d67e749
Compare
@@ -190,6 +190,8 @@ type Configuration struct { | |||
Validation struct { | |||
// Enabled enables the other options in this section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a deprecated note here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
LGTM May need more to let people know about the deprecation. |
d67e749
to
fde1d11
Compare
LGTM Could we add note in the |
fde1d11
to
b81eb3a
Compare
@dmcgowan updated |
Signed-off-by: Antonio Murdaca <[email protected]>
b81eb3a
to
0fb25dd
Compare
is this ready to go? |
Note for 2.7 change list, |
I just saw this issue after creating #2795. |
Even when validation is off, we don't want to allow manifests with foreign layers urls.
Signed-off-by: Antonio Murdaca [email protected]