Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home4/thezonie/public_html/fileai-com/blog/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home4/thezonie/public_html/fileai-com/blog/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /home4/thezonie/public_html/fileai-com/blog/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /home4/thezonie/public_html/fileai-com/blog/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /home4/thezonie/public_html/fileai-com/blog/wp-includes/classes.php on line 593

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home4/thezonie/public_html/fileai-com/blog/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home4/thezonie/public_html/fileai-com/blog/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /home4/thezonie/public_html/fileai-com/blog/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /home4/thezonie/public_html/fileai-com/blog/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /home4/thezonie/public_html/fileai-com/blog/wp-includes/classes.php on line 710

Strict Standards: Redefining already defined constructor for class wpdb in /home4/thezonie/public_html/fileai-com/blog/wp-includes/wp-db.php on line 58

Deprecated: Assigning the return value of new by reference is deprecated in /home4/thezonie/public_html/fileai-com/blog/wp-includes/cache.php on line 99

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /home4/thezonie/public_html/fileai-com/blog/wp-includes/cache.php on line 404

Deprecated: Assigning the return value of new by reference is deprecated in /home4/thezonie/public_html/fileai-com/blog/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /home4/thezonie/public_html/fileai-com/blog/wp-includes/theme.php on line 576
the [ file ai ] blog » certificate

Posts Tagged ‘certificate’

To Buy A Cert Or Not To Buy A Cert?

Saturday, July 5th, 2008

Today I received some insightful feedback from a reader named “Shirley” from velvetblues.com regarding her experience using fileai.com. In her comment she said that she “received a security warning and opted out” when trying to use the site for the first time.

Unfortunately, I understand where she’s coming from. In this day an age, when you’re browsing the web and a window pops up entitled “Security Warning” most peoples’ initial reaction is to click the “Cancel” button. The problem is, that’s the way Signed Java Applets work on today’s modern browsers, and a Signed Java Applet is what enables fileai.com to do cool things like accept drag-and-drop files, negotiate through gnarly firewall and router network configurations, and transfer files directly without having to upload them to a server.

There is one thing I can do to make the Security Warnings a little less scary, but it’ll cost me $300 - $500 to do so. :(

If I purchase a Code Signing Certificate from Verisign or Thawte (the same companies that sell SSL Certificates that make web pages secure) then my Signed Java Applet Security Warnings will change from this:

Security Warning - Windows XP

Security Warning - Mac OS X

to something like this:

Signed Java Applet Security Warning in Windows

Signed Java Applet Security Warning - OS X

(Obviously they won’t say “Northwestern University”, but you get the idea.)

So I guess the questions is: If I spent the $300-$500 to buy a Code Signing Certificate to make the Security Warnings say that my Signed Java Applet was “Verified”, would that make any of you more willing to click “Run” or “Trust”? Or is just the fact that there is a Security Warning staring you in the face enough to make you go somewhere else?

Thanks for all the great feedback, and please keep it coming! :)