title: Options for using an unsigned 3rd party applet in Java 1.7.0_51 and later
body: <p>I mostly develop in .NET, but a few of my projects use 3rd-party Java applets, so I'm hoping some Java experts can give me some advice.</p>
  
  <p>The latest version of Java (1.7 update 45) brings up a scary-looking prompt when an unsigned applet launches, warning it could do bad things to the user's PC. This Java version has a built-in expiry date - from January, users will need to update to u51, which will refuse to run unsigned applets at all. These requirements can be sidestepped by users moving the Java Security settings below "minimum recommended", but that's probably not an option for us.</p>
  
  <p>First question: is this summary correct, or have I misunderstood something and we'll be able to carry on with the unsigned applet no problem?</p>
  
  <p>Second, what are my options for dealing with a 3rd-party applet for which the publisher doesn't offer a signed version? I believe I can just sign the jar myself, but are there any technical or legal problems with that idea? The application's only for internal use at my company's sites. We could either sign it with a self-issued certificate, which corporate IT would need to add to the approved list on people's desktops, or we could ask about buying a certificate. Again, any advice on these plans appreciated.</p>