[v0.18.0] - 2022-09-27
--------------------
### New Features
- Adding support for OpenWrt 21.03
- Add final version of RequiredRSASize
Keep the old version for backward compatibility
Upstream commit:
https://github.com/openssh/openssh-portable/commit/1875042c
### Bug Fixes
- Update source template to match generated files
### Other Changes
- Remove legacy files
- Update pre-commit plugins to latest
- Linting fixes
- keep v prefix in version/tag
Keep the `v` prefix in the version/tag
Signed-off-by: Rich Megginson <rmeggins@redhat.com>
[v0.17.0] - 2022-08-31
--------------------
- Make drop-in config file functionality configurable by user
This PR simplifies the logic behind the drop-in config files and also
allows the user to use drop-in configs even if the distribution does not
support it out of the box.
- Allow user to override variables
A previous commit hardcoded many variables to the values under vars/,
making it impossible for the user to parameterize things like the systemd
service name. The assumption was that the __sshd_* variables were useless
in an effort to blindly adhere to best practices, but they were crucial in
allowing flexibility to the user.
- none
[v0.16.1] - 2022-07-28
--------------------
- add parameter RSAMinSize
Add support for the new RSAMinSize parameter.
- Ensure values are cast to correct type
- Addition notes about secondary variables
- Fix various linting issues
- Revert incorrect module name
- tests: Do not be picky about spaces/tabs
When testing with cloud-init, it modifies the sshd_configuration and can
replace some tabs with whitespaces. This happens frequently around the
subsystem keyword. There are no functional changes, but the matching
did not work as expected.
Signed-off-by: Jakub Jelen <jjelen@redhat.com>
- the role still supports ansible 2.9
- Add CHANGELOG.md
- Add changelog_to_tag.yml to .github/workflows
Description:
When a new changelog section is added to CHANGELOG.md and pushed,
changelog_to_tag.yml is triggered, which generates a new tag and
a new release.
Signed-off-by: Rich Megginson <rmeggins@redhat.com>
https://github.com/willshersystems/ansible-sshd/issues/188
This shouldn't be necessary, but there seems no way to
guarantee using a version of Jinja which doesn't have this
problem.
In addition - it is not good practice to compare values to
`true` or `false` - instead, just ensure the value is a `bool`
type and evaluate in a boolean context.
