Code signing

[MielieSpoor]

Damn its expensive to properly sign your code!

 

[dequadin]

What's expensive? Do you need a certificate per assembly?

 

[MielieSpoor]

What's expensive? Do you need a certificate per assembly?

No, paying $549 for 2years to sign your assemblies. You can sign all you assemblies with the one cert for two years but you have to that amount every two years to keep your code properly signed...

 

[WiT8litZ]

Yeap. Had to sign our J2ME application also recently. Bought only a 1yr certificate to see how it goes.

 

[MielieSpoor]

VeriSign is even worse with their prices. $499 for 1 year! Its worth it in the end but you app must be big enough otherwise its just not worth it.

 

[SilverNodashi]

what exactly do you mean by "signing your code"? What code are you referring to? and how does it get "signed"?

 

[WiT8litZ]

With J2ME you sign your code mostly to be able to access permission settings that normally require user approval everytime you use it ie. network access or location access. Thus the user can setup the app to always use the services without asking, and depending on your app, will approve service and user experience.

Not sure what happens when you sign .net code though.

 

[SilverNodashi]

aah ok, so it's more for compiled code, or end-user code, not really web code like php / asp / xml / etc?

 

[dequadin]

aah ok, so it's more for compiled code, or end-user code, not really web code like php / asp / xml / etc?

The web analogy, would be a security certificate for your site alla https

 

[SilverNodashi]

sure, when I first saw the topic I also thought SSL, but SSL is different since it secures the connection between the server (be it on HTTS / SMPTS / FTPS / POP3S / SSH / etc), and the end user.

But clearly code signing is different

 

[dequadin]

sure, when I first saw the topic I also thought SSL, but SSL is different since it secures the connection between the server (be it on HTTS / SMPTS / FTPS / POP3S / SSH / etc), and the end user.

But clearly code signing is different

Yes but you also use a security certificate to say that www.yoursite.com is really your site, and not www.sneakyhacker.com

So there are similarities...