Imageuploader 2.5, 3.0 - Certificate Unavailability Issue

Options

Previous Topic Next Topic

bizzy User Profile View All Posts by User View Thanks		#1 Posted : Wednesday, August 18, 2004 3:18:00 PM(UTC)
Rank: Member Groups: Member Joined: 8/18/2004(UTC) Posts: 41		To use this product the download of the client is based of Aurigma's certificates. If Aurigma's certificates are not valid due to expiration or if due to some bad luck you go out of business (hope not since you have a fine set of product profile) what happens to people who need to install the client? We understand one solution to this is for us to use our own certificates and your source code and take this responsibility on ourselves. But it is expensive and also not trivial to get since it involves generating certificate, approvals from Thawte or Verisign, etc. 1. What is your option to us when this situation occurs if we are dependent on your default system? 2. If we do not need source code can you still generate certificates for our website if we got registered with Thawte or Verisign? This could be done at a lower cost than your choice of buying source code and doing the generation of certificates. This will give lots of your customers a choice of upgrading to this option and be a revenue source for you and also gives us a lower cost option with less hassles on the technical side of generating these certificates. Please let us your answers to these important issues. Thanks.

Fedor User Profile View All Posts by User View Thanks		#2 Posted : Wednesday, August 18, 2004 3:32:00 PM(UTC)
Rank: Advanced Member Groups: Member, Administration, Moderator Joined: 7/28/2003(UTC) Posts: 1,660 Thanks: 5 times Was thanked: 76 time(s) in 74 post(s)		To use this product the download of the client is based of Aurigma's certificates. If Aurigma's certificates are not valid due to expiration or if due to some bad luck you go out of business (hope not since you have a fine set of product profile) what happens to people who need to install the client? When we sign ActiveX controls we need valid certificate only on signing date. Code signing certificates differs from SSL certificates in this place. For example we have valid code signing certificate till the end of 2004 and signed control in 2004. Signed control will have valid signature and in 2005, 2006, 2007... However we willn't have possibility to sign control with this certificate in 2005, 2006, 200... As conclusion I want to say that if we released signed control, it will be have valid signature forever and you needn't worry about it. ======================================================== 02/14/2008, Fedor Additional info Signed ActiveX control has always valid signature, at that time as Java applet signature is valid until certificate expiration only, so in this case you need to update Java applet to the version with new signature. ======================================================== Edited by user Thursday, February 14, 2008 2:42:18 PM(UTC) \| Reason: Not specified
		Best regards, Fedor Skvortsov

Users browsing this topic
Guest

Forum Jump

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.