Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port Access violation occurring in System.DirectoryServices.ActiveDirectory.ForestTrustRelationshipInformation fix from .netfx to .net-core #66726

Merged
merged 2 commits into from
Mar 31, 2022

Conversation

kumarravi
Copy link
Contributor

  • Description: Access violation occurring in System.DirectoryServices.ActiveDirectory.ForestTrustRelationshipInformation.GetForestTrustInfoHelper
  • Customer Impact: None yet, customer had an issue in .netfx because they were using .netfx to fetch forest trust information. If any customer uses .netcore to do something similar then this fix should mitigate the issue. None of the customers have reported any issues with .netcore yet.
  • Regression: Yes, The issue was introduced when windows 1B security fixes were released. We missed the corresponding fix in ,net code and hence this pr.
  • Risk: Very low
  • Original Issue: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1465335
  • Original PR: https://vstfdevdiv/DevDiv2/DevDiv/_versionControl/changeset/1764922

@ghost ghost added the community-contribution Indicates that the PR has been added by a community member label Mar 16, 2022
@dnfadmin
Copy link

dnfadmin commented Mar 16, 2022

CLA assistant check
All CLA requirements met.

@ghost
Copy link

ghost commented Mar 16, 2022

Tagging subscribers to this area: @dotnet/area-system-directoryservices, @jay98014
See info in area-owners.md if you want to be subscribed.

Issue Details
  • Description: Access violation occurring in System.DirectoryServices.ActiveDirectory.ForestTrustRelationshipInformation.GetForestTrustInfoHelper
  • Customer Impact: None yet, customer had an issue in .netfx because they were using .netfx to fetch forest trust information. If any customer uses .netcore to do something similar then this fix should mitigate the issue. None of the customers have reported any issues with .netcore yet.
  • Regression: Yes, The issue was introduced when windows 1B security fixes were released. We missed the corresponding fix in ,net code and hence this pr.
  • Risk: Very low
  • Original Issue: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1465335
  • Original PR: https://vstfdevdiv/DevDiv2/DevDiv/_versionControl/changeset/1764922
Author: kumarravi
Assignees: -
Labels:

area-System.DirectoryServices, community-contribution

Milestone: -

@danmoseley
Copy link
Member

@kumarravi unlike the .NET Framework sources, this codebase uses nullable reference type annotations hence the error. If you know a reference is undoubtedly not nullable, it may be appropriate to use the ! operator to stop the error.

BTW, should we include you in https://github.com/dotnet/runtime/blob/main/docs/area-owners.md ?

@danmoseley danmoseley requested a review from joperezr March 16, 2022 23:58
@kumarravi
Copy link
Contributor Author

@danmoseley Thanks for the review. Apologies for not being clear but this PR is work in progress. And thanks again for the resolution of the errors I was seeing. You saved me some time which I would have spent trying to resolve these.

Since Active directory team is the owner of this code, I would like to be added as the co-owner of the repo. Thanks

@danmoseley
Copy link
Member

@kumarravi Feel free to offer a PR to the markdown I linked. (It's easy, no builds/tests will run)

@kumarravi
Copy link
Contributor Author

kumarravi commented Mar 17, 2022

@danmoseley Apologies but I cannot find the markdown that you linked. Can you let me know what you mean by "offer a PR to the markup"?

@joperezr
Copy link
Member

Thanks for the contribution @kumarravi I will take a look at this very soon.

Apologies but I cannot find the markdown that you linked. Can you let me know what you mean by "offer a PR to the markup"?

He means that if you want to be included as a area-owner for DirectoryServices, you can submit a separate PR where you are modifying this file: https://github.com/dotnet/runtime/blob/main/docs/area-owners.md

In particular, you would want to add your alias right next to the DirectoryServices area like:

-| area-System.DirectoryServices                  | @ericstj      | @dotnet/area-system-directoryservices               | Consultants: @BRDPM @grubioe @jay98014               
+| area-System.DirectoryServices                  | @ericstj      | @dotnet/area-system-directoryservices               | Consultants: @BRDPM @grubioe @jay98014 @kumarravi         

@kumarravi
Copy link
Contributor Author

@joperezr a gentle reminder about the above request. Thanks!

Copy link
Member

@joperezr joperezr left a comment

Choose a reason for hiding this comment

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

Sorry for missing the review here. I'm not familiar with this code, but the changes look good and match the internal checked in fix. Is there a test that we can add for regression protection here?

@kumarravi
Copy link
Contributor Author

@joperezr Thanks for the approval. I really appreciate it. I think the reason we did not put any tests for this fix was that this
scenario is so end case and complex that is not easy to put in a test case. @jay98014 please feel to correct me if I am wrong.

Looks like I do not have the permissions to merge this PR. I would have to request write access. Can someone with write access merge this PR or tell me how to request the same.

@joperezr joperezr merged commit fe0f600 into dotnet:main Mar 31, 2022
@ghost ghost locked as resolved and limited conversation to collaborators May 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.DirectoryServices community-contribution Indicates that the PR has been added by a community member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants