[Snyk] Security upgrade paramiko from 2.6.0 to 3.4.0

[vs4vijay]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • requirements.txt

⚠️ Warning

paramiko 3.4.0 has requirement cryptography>=3.3, but you have cryptography 2.7.
paramiko 3.4.0 has requirement bcrypt>=3.2, but you have bcrypt 3.1.7.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	688/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.9	Authentication Bypass by Capture-replay SNYK-PYTHON-PARAMIKO-6130887	paramiko: 2.6.0 -> 3.4.0	No	Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[sweep-ai]

Apply Sweep Rules to your PR?

• Apply: All docstrings and comments should be up to date.
• Apply: Code should be properly indented and follow consistent indentation style.
• Apply: Variable and function names should be descriptive and follow a consistent naming convention.
• Apply: There should be no commented out code or unused code in the repository.
• Apply: Code should be organized into logical modules and classes.
• Apply: There should be no hard-coded values in the code. Use constants or configuration files instead.