Skip to content
This repository has been archived by the owner on Feb 24, 2020. It is now read-only.

Add insecure option http #1945

Merged
merged 1 commit into from Jan 11, 2016
Merged

Conversation

blixtra
Copy link
Collaborator

@blixtra blixtra commented Jan 8, 2016

This adds code, tests, and documentation for a new "http" --insecure-options flag.

fixes #1836

@blixtra
Copy link
Collaborator Author

blixtra commented Jan 8, 2016

I'll add a CHANGELOG entry after the 0.15 release is done.

@@ -19,19 +19,21 @@ const (
insecureImage = 1 << (iota - 1)
insecureTls
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Damn, this should really be "insecureTLS" (c.f.)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was telling that to Alban on Friday. I'll do a quick PR for that.

@jonboulle
Copy link
Contributor

LGTM

With this the user will need to explicitly allow http connections.
Previously, this was hard-code to be true.

Fixes rkt#1945
@blixtra blixtra force-pushed the blixtra/add-insecure-option-http branch from b10c006 to d7d19d0 Compare January 11, 2016 09:30
@blixtra
Copy link
Collaborator Author

blixtra commented Jan 11, 2016

I've added the CHANGELOG and squashed the commits.

iaguis added a commit that referenced this pull request Jan 11, 2016
@iaguis iaguis merged commit fa2ac2d into rkt:master Jan 11, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

discovery: adding option: --insecure-options=http
4 participants