Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
mkbundle --list-targets fails due to expired certificate
root@Orac:~# mkbundle --list-targets
System.Net.WebException: Error: TrustFailure (The authentication or decryption has failed.) ---> System.IO.IOException: The authentication or decryption has failed. ---> System.IO.IOException: The authentication or decryption has failed. ---> Mono.Security.Protocol.Tls.TlsException: Invalid certificate received from server. Error code: 0xffffffff800b010a
This is from a fresh install this am on a clean copy of ubuntu. Either the cert has expired or you are using a cert not in the trust store.
The certificate is probably not expired. Rather it seems that the file is hosted on github.com and the site is properly returning the github.com certificate which is failing because the URL being resolved is for a mono domain name.
Fresh install of what version?
Mono master (91014ff) returns the expected list of targets on OSX.
Mono JIT compiler version 4.6.0 (Stable 126.96.36.199/746756c Wed Sep 21 14:16:42 UTC 2016)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
LLVM: supported, not enabled.
This is running on a clean install of Ubuntu (16.4)
Oh and now it is fixed...
Thanks Philip, Feel free to re-open if it reappears.
I have a slightly different error ( Bug 58033 ) on the much newer mono 4.8.0 on fedora 26.