Skip to content

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Dec 11, 2023

Bandit releaed new version (1.7.6) few days ago. We had >=1.7.5 and it started to detect new potential issue (Auto Add Hostkey) in Google and SSH providers. Both case are valid however (in the first case the key is a throw-away one and just - dynamically - created so we cannot have it stored yet. Auto-Adding makes sense in this case. In case of SSH provider, the user must deliberately choose this option and they are clearly warned that it is not secure option.

We are also fixing bandit to a pinned version. The problem with

= in case of pre-commit is that the result might depend on cache
of pre-commit - in main we are still using 1.7.5 as it has been cached, but new PRs use 1.7.6 because they have no access to main cache.

We will have a separate pre-commit added to make sure that we are updating to latest versions of other pre-commits soon. We need to make sure we are updating those deliberately.


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

Bandit releaed new version (1.7.6) few days ago. We had >=1.7.5 and
it started to detect new potential issue (Auto Add Hostkey) in
Google and SSH providers. Both case are valid however (in the first
case the key is a throw-away one and just - dynamically - created
so we cannot have it stored yet. Auto-Adding makes sense in this case.
In case of SSH provider, the user must deliberately choose this
option and they are clearly warned that it is not secure option.

We are also fixing bandit to a pinned version. The problem with
>= in case of pre-commit is that the result might depend on cache
of pre-commit - in main we are still using 1.7.5 as it has been
cached, but new PRs use 1.7.6 because they have no access to main
cache.

We will have a separate pre-commit added to make sure that we are
updating to latest versions of other pre-commits soon. We need
to make sure we are updating those deliberately.
@potiuk potiuk force-pushed the mark-seurity-issues-found-as-save branch from d8b5b9f to e53ca67 Compare December 11, 2023 07:20
@potiuk
Copy link
Member Author

potiuk commented Dec 11, 2023

Passed static checks. Merging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants