Skip to content
This repository was archived by the owner on Dec 6, 2024. It is now read-only.

Conversation

@Aditi8007
Copy link

This code change address multiple issue of "Use of a broken or risky cryptographic algorithm".

Copy link

@samirparhi-dev samirparhi-dev left a comment

Choose a reason for hiding this comment

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

LGTM from the security prospective. I am not very sure about functionality.
@Anjana2310 : Kindly review

Copy link
Contributor

@Anjana2310 Anjana2310 left a comment

Choose a reason for hiding this comment

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

Adding @ravishanigarapu and @devikasuresh20 for review

Copy link
Contributor

@ravishanigarapu ravishanigarapu left a comment

Choose a reason for hiding this comment

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

Need some clarification on this PR. these changes will be impact on historical records

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants