Can I be my own CA for code signing certificates?

Hello,

I had a long read of :

http://java.sun.com/j2se/1.4.2/docs/guide/plugin/developer_guide/rsa_signing.html

and I have been poking around at :

http://www.openca.org/

http://www.openssl.org/

Before I download the above I was hoping for a little advice....

Is it possible to use one or both of the above to create my owncode signing certifcates?

I really don't see the need for paying verisign or thawte for a certifcate when our applet / jar is going to be used internally at a customers site. They will be trusting their own IT department, the certifcate, whether it is generated by me or thawte will at least verify that the code hasn't been tampered with, andmore importantly, it will allow the end user an easy way of allowing us the permissions we need versus editing by hand a policy file.

Does this sound reasonable?

- Alfred

[957 byte] By [AlfredTheGrey] at [2007-9-30 12:07:13]
# 1

I found the following discussion :

http://forum.java.sun.com/thread.jsp?forum=63&thread=132769&tstart=15&trange=15

and I have created my own self-signed certificate.

What does having the user download the certificate via open from the browser get you that saying "always trust" doesn't?

AlfredTheGrey at 2007-7-4 14:47:40 > top of Java-index,Security,Signed Applets...