NETWAYS / NETWAYS/ansible-collection-elasticstack
Support 2b or 2y as indentation by Bcrypt
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
We should support 2b or 2y indentation for logstaash user password hashing, when we not support Elasticsearch 7 anymore in this collection. At the moment we support 2a which gut for elasticsearch company is. 2y and 2b are more secure than 2a. We should only make the indentation parameter in the logstash writer user as a variable and put the new value in defaults.yml
Here are the relevant links:
https://passlib.readthedocs.io/en/stable/lib/passlib.hash.bcrypt.html
https://github.com/elastic/elasticsearch/pull/76083
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Logstash writer user configuration and defaults.yml in the Ansible collection. Read the linked Passlib bcrypt documentation and Elasticsearch pull request first, then verify how the current 2a setting is represented. Done means the indentation value is configurable and the supported bcrypt value is defined in defaults.yml.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, elasticsearch
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100