Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Conversation

@AfsanehR-zz
Copy link
Contributor

@AfsanehR-zz AfsanehR-zz commented Dec 27, 2018

Fixes #34205
Description
Null is passed for credentials when calling SqlConnectionPoolKey ChangePassword method.

Customer Impact
Wrong connection pool gets cleared when calling ChangePassword using a SecureString.

Regression
No, since this code path exists in .Net Framework and credential is mistakenly passed as null.

Risk
High. A password change may cause the connections from wrong pool to be killed causing unexpected application disruption.

conn3.Open();
conn4.Open();

SecureString NewPassword = new SecureString();
Copy link
Contributor

Choose a reason for hiding this comment

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

Nit: newPassword

@saurabh500
Copy link
Contributor

cc @danmosemsft

@afsanehr it would be good to send a PR to master as well and have that merged before the release branch is merged with Shiproom approval.

@danmoseley danmoseley removed the Servicing-consider Issue for next servicing release review label Jan 3, 2019
@AfsanehR-zz AfsanehR-zz added the Servicing-consider Issue for next servicing release review label Jan 22, 2019
@AfsanehR-zz AfsanehR-zz reopened this Jan 22, 2019
@leecow leecow added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Jan 24, 2019
@leecow leecow modified the milestones: 2.2.x, 2.2.3 Jan 24, 2019
@danmoseley
Copy link
Member

Please wait for branch to open in about 2-3 weeks. Approx 2/12.

@danmoseley danmoseley added the * NO MERGE * The PR is not ready for merge yet (see discussion for detailed reasons) label Jan 24, 2019
@wtgodbe wtgodbe removed the * NO MERGE * The PR is not ready for merge yet (see discussion for detailed reasons) label Feb 13, 2019
@wtgodbe wtgodbe merged commit 87ca51b into dotnet:release/2.2 Feb 13, 2019
@AfsanehR-zz
Copy link
Contributor Author

@danmosemsft do we need to port this to other branch or is it considered complete? If so, let me know please so I can close the related issue #34205 Thanks!

@wtgodbe
Copy link
Member

wtgodbe commented Feb 14, 2019

Is there a reason this PR was specifically opened in release/2.2? Was there also a PR opened in release/2.1?

@AfsanehR-zz
Copy link
Contributor Author

@wtgodbe The feature was added originally to Release/2.2 branch before and not 2.1 Link
This fix is also both in master and now in Release/2.2

@wtgodbe
Copy link
Member

wtgodbe commented Feb 22, 2019

I see, that makes sense. I'll make the necessary changes to ensure this gets shipped with 2.2.3.

@danmoseley
Copy link
Member

Good catch @wtgodbe. Does #33697 need a change also?

@wtgodbe
Copy link
Member

wtgodbe commented Feb 22, 2019

That one's good to go, Santi already made the necessary packaging changes.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants