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

core(is-on-https): consider about:* secure #4749

Merged
merged 1 commit into from
Mar 14, 2018
Merged

Conversation

patrickhulce
Copy link
Collaborator

@paulirish
Copy link
Member

A more involved fix is flipping nonApplicable to true in this case.

Also it looks like about: is not a secure origin..

image

lol that this was reported. :)

@patrickhulce
Copy link
Collaborator Author

@paulirish how about when on an HTTPS page?

elawrence's comment seemed like this was legit. I'm not sure we should flag abouts as there's no action item to convert about:blank into an HTTPS URL is there? does an about:blank iframe on an https page do anything bad?

Contexts that inherit a security context (about:, javascript:) should probably be exempted from the audit.

@paulirish
Copy link
Member

I see, okay. So we're focused on about:blank as a resource/iframe on the page rather than the root document itself. Okay, fine then. :)

This makes sense. Also good luck trying to audit a root 'about:blank' page. :p

@paulirish paulirish merged commit b5172c9 into master Mar 14, 2018
@paulirish paulirish deleted the add_about_secure_scheme branch March 14, 2018 23:23
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

Successfully merging this pull request may close these issues.

3 participants