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

S.S.C.OpenSsl doesn't have UnsupportedOSPlatform annotation at assembly level on IosSimulator #54212

Closed
MaximLipnin opened this issue Jun 15, 2021 · 8 comments

Comments

@MaximLipnin
Copy link
Contributor

MaximLipnin commented Jun 15, 2021

Not sure whether it's an issue - when building S.S.C.OpenSsl for IosSimulator, the build produces a PNSE-assembly but the assembly metadata has [assembly: SupportedOSPlatform("iOS")] annotation even though it's marked as unsupported at csproj level using <UnsupportedOSPlatforms>windows;browser;android;ios;tvos</UnsupportedOSPlatforms> (see https://github.com/dotnet/runtime/blob/main/src/libraries/System.Security.Cryptography.OpenSsl/Directory.Build.props#L6)

image

@dotnet-issue-labeler dotnet-issue-labeler bot added area-System.Security untriaged New issue has not been triaged by the area owner labels Jun 15, 2021
@ghost
Copy link

ghost commented Jun 15, 2021

Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq, @GrabYourPitchforks
See info in area-owners.md if you want to be subscribed.

Issue Details

Not sure whether it's an issue - when building S.S.C.OpenSsl for IosSimulator, the build produces a PNSE-assembly but the assembly metadata has [assembly: SupportedOSPlatform("iOS")] annotation even though it's marked as unsupported at assembly level using <UnsupportedOSPlatforms>windows;browser;android;ios;tvos</UnsupportedOSPlatforms> (see https://github.com/dotnet/runtime/blob/main/src/libraries/System.Security.Cryptography.OpenSsl/Directory.Build.props#L6)

image

Author: MaximLipnin
Assignees: -
Labels:

area-System.Security, untriaged

Milestone: -

@ghost
Copy link

ghost commented Jun 15, 2021

Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

Not sure whether it's an issue - when building S.S.C.OpenSsl for IosSimulator, the build produces a PNSE-assembly but the assembly metadata has [assembly: SupportedOSPlatform("iOS")] annotation even though it's marked as unsupported at assembly level using <UnsupportedOSPlatforms>windows;browser;android;ios;tvos</UnsupportedOSPlatforms> (see https://github.com/dotnet/runtime/blob/main/src/libraries/System.Security.Cryptography.OpenSsl/Directory.Build.props#L6)

image

Author: MaximLipnin
Assignees: -
Labels:

area-Infrastructure-libraries

Milestone: -

@akoeplinger
Copy link
Member

@buyaa-n this sounds unexpected.

@ghost ghost added this to Untriaged in Infrastructure Backlog Jun 15, 2021
@akoeplinger akoeplinger moved this from Untriaged to 6.0.0 in Infrastructure Backlog Jun 15, 2021
@akoeplinger akoeplinger added this to the 6.0.0 milestone Jun 15, 2021
@buyaa-n
Copy link
Member

buyaa-n commented Jun 15, 2021

That is expected, MSBuild would add SupportedOSPlatform attribute for any targeted build with the target platform, even it was not needed for PNSE only assembly

@ViktorHofer
Copy link
Member

We could easily fix that in our infra if we want to but I'm not sure it's important...

@buyaa-n
Copy link
Member

buyaa-n commented Jun 16, 2021

We could easily fix that in our infra if we want to but I'm not sure it's important...

I believe the cross-platform build is important because that is the one that will be shipped (which has the UnsupportedOSPlatform for windows, browser, android, ios, tvos as expected). Honestly, I do not know for what we need an assembly that throws inside for all APIs nor how/when it is used, so I could not say if fixing this is important or how important it is 😛

@safern
Copy link
Member

safern commented Jun 16, 2021

Does it really matter though? Assemblies that throw not supported are runtime assemblies and the analyzer runs against the compile assemblies (ref). I know it's odd, but it doesn't seem to hurt anything.

@akoeplinger
Copy link
Member

Yeah I didn't realize this was about the implementation assembly and not the ref assembly. I agree that it's not important for the former.

Infrastructure Backlog automation moved this from 6.0.0 to Done Jun 16, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Jul 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants