>>We could get around this security issue by either:
>> 1. proxy the feeds through the original server
>> 2. use a signed applet
>>
>
> It may be time to bite the bullet and distribute both signed and unsigned
> applets. The former are useful for demonstration from local hard disk
> anyway!
>
> Perhaps we should obtain the $250 Verisign applet signing certificate
> on behalf of Jmol;
I just checked pricing:
www.verisign.com
Sun Java Signing Digital ID
CodeSigner Standard US$400
CodeSigner Pro US$695
* their web site had remarkably little information as to the
difference between Standard and Pro
* no information about annual renewal fee
* I will call them to get more info
www.thawte.com
Initial code-signing certificate US$199
Annual renewal US$159
In addition to being more expensive, VeriSign seems to have a somewhat
tarnished reputation these days. In large part because of their
NetworkSolutions subsidiary.
> any idea if SF themselves might be able to help in this regard?
I have sent two emails to SF asking them about a code signing service. I
think that it would be a good service for them to offer as part of their
project support services. Unfortunately, to date I have not received a
response from SF.
Miguel
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Jmol-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jmol-developers
