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

Update TLS configuration options #2330

Merged
merged 1 commit into from
Sep 1, 2016
Merged

Conversation

urso
Copy link

@urso urso commented Aug 21, 2016

rename tls to SSL + adapt some fields:

  • insecure has become verification_mode. insecure: false is replaced by mode full and insecure: true by mode none.
  • renamed certificate_key to key
  • introduced key_passphrase
  • replaced min_version and max_version with supported_protocols using an array of ok versions. New versions strings: SSLv3, SSLV3.0, TLSv1 (use TLSv1.0), TLSv1.0, TLSv1.1 and TLSv1.2

Changes:

  • rewrite TLS dialer and TLS configuration
  • add support for encrypted key files
  • use TLS dialer with elasticsearch output (some more manual tests with and without system certificates required)
  • update unit/integration tests to use new settings
  • update default configuration files to use new ssl settings
  • update documentation (docs URL did also change from tls to ssl)
  • update migration script

@urso urso added in progress Pull request is currently in progress. discuss Issue needs further discussion. labels Aug 21, 2016
@@ -19,7 +19,7 @@ configuration settings, you need to restart {beatname_uc} to pick up the changes
* <<redis-output>>
* <<file-output>>
* <<console-output>>
* <<configuration-output-tls>>
* <<configuration-output-ssl>>
Copy link
Contributor

Choose a reason for hiding this comment

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

Just a note that when we change IDs for topics, we need to ask the web team to set up redirects, or our links from forum topics will be broken. That's a good reason to avoid renaming IDs unless (which is probably true in this case) you definitely want the name to change, and it's worth the extra work to get the redirect set up.

@urso urso force-pushed the ssl-settings branch 3 times, most recently from 0df5e97 to a5cffdc Compare August 24, 2016 12:28
@urso urso added review libbeat and removed in progress Pull request is currently in progress. discuss Issue needs further discussion. labels Aug 25, 2016
@urso urso changed the title [WIP] Update TLS configuration options Update TLS configuration options Aug 25, 2016

===== enabled

The `enabled` settings can be used to disable the ssl configuration by setting
Copy link
Contributor

Choose a reason for hiding this comment

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

typo: setting


If you follow the section on migrating the configuration, you will have TLS
enabled. However, you must be aware that if the `tls` section is missing from the
If you follow the section on migrating the configuration, you will have WSSL
Copy link
Member

Choose a reason for hiding this comment

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

WSSL?

Copy link
Author

Choose a reason for hiding this comment

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

ups

@ruflin
Copy link
Member

ruflin commented Aug 30, 2016

This needs an update to the CHANGELOG.md file under breaking changes.

# Enable SSL support. SSL is automatically enabled, if any SSL setting is set.
#ssl.enabled: true

# Configure SSL verification mode. If `none` is configured, all server host
Copy link
Member

Choose a reason for hiding this comment

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

s/host/hosts/



@collect_lines
def migrate_tls_settings(content):
Copy link
Member

Choose a reason for hiding this comment

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

nice

@ruflin
Copy link
Member

ruflin commented Aug 30, 2016

LGTM. I left a few minor comments. Would be good to get a second review as this one is quite big.

@ruflin
Copy link
Member

ruflin commented Aug 30, 2016

@urso Did you run make docs to check if all the docs still build?

@urso
Copy link
Author

urso commented Aug 30, 2016

Did you run make docs to check if all the docs still build?

Yep, still builds.

Only issue with docs is (as described by @dedemorton):

Just a note that when we change IDs for topics, we need to ask the web team to set up redirects, or our links from forum topics will be broken. That's a good reason to avoid renaming IDs unless (which is probably true in this case) you definitely want the name to change, and it's worth the extra work to get the redirect set up.

@tsg
Copy link
Contributor

tsg commented Aug 31, 2016

All looking good, thanks @urso for the great work.

Seems like quite a few redirects are required. We should decide one way or the other so we know if we want to merge the PR as is or adjust it.

@ruflin
Copy link
Member

ruflin commented Aug 31, 2016

I suggest to go with the new urls and do redirects, as ssl is probably also what people search for and want to see in the url.

@urso Needs rebase.

@urso
Copy link
Author

urso commented Aug 31, 2016

Yeah, not really happy about all the redirect. But agree with @ruflin about using ssl over tls.

@urso urso force-pushed the ssl-settings branch 2 times, most recently from 3e74fce to 2f2bbe5 Compare August 31, 2016 11:31
rename tls to SSL + adapt some fields:

- `insecure` has become `verification_mode`. `insecure: false` is replaced by
  mode `full` and `insecure: true` by mode `none`.
- renamed `certificate_key` to `key`
- introduced `key_passphrase`
- replaced `min_version` and `max_version` with `supported_protocols` using an
  array of ok versions. New versions strings: `SSLv3`, `SSLV3.0`, `TLSv1` (use
  TLSv1.0), `TLSv1.0`, `TLSv1.1` and `TLSv1.2`

Changes:
- rewrite TLS dialer and TLS configuration
- add support for encrypted key files
- use TLS dialer with elasticsearch output (some more manual tests with and
  without system certificates required)
- update unit/integration tests to use new settings
- update default configuration files to use new ssl settings
- update documentation (docs URL did also change from `tls` to `ssl`)
- update migration script
@ruflin ruflin merged commit d15cab2 into elastic:master Sep 1, 2016
@urso urso deleted the ssl-settings branch February 19, 2019 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants