-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Unable to Install Mono Project due to package unsigned #21708
Comments
Can this please be addressed? This looks is a roadblock to most corporate users. |
I can confirm that I'm seeing it with the 6.12.0.199 available from the download/stable page on mono-project.org. I'm eager to try Mono for the first time and I'm trying to be prudent by installing only software I can verify is authentic. Thanks to @rolfbjarne for mentioning 6.12.0.182, which I will use as a workaround. |
The 6.12.0.182 build is 18 months old. |
Seems 6.12.0.5 (preview) is signed. |
From @llamaseer on Fri, 08 Sep 2023 17:18:39 GMT
The present Mono Project for Mac download for Mac 6.12.0.199 appears to be unsigned (both Visual Studio channgel and Stable channel.
This makes it impossible to install, at least for those of us who have a managed security policy which prevents it (I unfortunately don't have access to alternative systems to verify the behavior in other conditions). This includes by opening with Ctrl+click or using 'Open Anyway' from 'Privacy and Security' settings. 'Security' -> 'Allow applications downloaded from' is set to 'App store and identified developers'.
I was able to successfully install a previous binary (6.12.0.182) and confirmed with
pkgutil --check-signature
that the previous package was signed and the newer one is not.Steps to Reproduce
MonoFramework-MDK-6.12.0.199.macos10.xamarin.universal.pkg
) from https://www.mono-project.com/download/stable/#download-macExpected Behavior
Actual Behavior
Environment
Version information
Build Logs
NA
Example Project (If Possible)
NA
Copied from original issue dotnet/macios#18977
The text was updated successfully, but these errors were encountered: