[MonoDevelop] Code signing error in MonoDevelop.MonoMac

Jeff Stedfast jeff at xamarin.com
Wed Jul 25 14:57:27 UTC 2012


Can you try upgrading to Xcode 4.3? I'm wondering if the problem is because
we pass the certificate thumbprint (instead of the Common Name) to the
codesign utility.

The logic in MonoDevelop right now assumes that if you have Lion, it is
safe to use the thumbprint instead of the Common Name (thumbprint is better
if you have multiple keys with the same Common Name), but perhaps codesign
is bundled with Xcode and not OSX.

Jeff

On Tue, Jul 24, 2012 at 11:46 PM, zezba9000 <zezba9000 at gmail.com> wrote:

> Im using:
> XCode 4.2.
> MonoDevelop 3.0.3.4.
> Mono 2.10.9
> OSX 10.7.4
>
> If im the only one having this problem with those specs that would be nice
> to know.
> Are you able to test code signing an app to try and reproduce this?
> You could use some old key to try and sign some test app with MonoDevelop
> 3.0.3.4.
>
> Ive tried to build MonoDevelop.MonoMac, but could never get the Addin to
> load correctly in MonoDevelop, otherwise I would take a stab at fixing this
> (what seems to be) code issue.
>
>
>
> --
> View this message in context:
> http://mono.1490590.n4.nabble.com/Code-signing-error-in-MonoDevelop-MonoMac-tp4650528p4650549.html
> Sent from the Mono - MonoDevelop IDE mailing list archive at Nabble.com.
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/monodevelop-list/attachments/20120725/49da2f51/attachment.html>


More information about the Monodevelop-list mailing list