Win a copy of Escape Velocity: Better Metrics for Agile Teams this week in the Agile and Other Processes forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Frank Carver
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • fred rosenberger

Trusted Applet..............?????

 
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,
Can anyone explain me what is an trusted applet and how about making an applet a trusted one.
Anand
 
Ranch Hand
Posts: 347
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Anand.
The reason for making a trusted applet is to give the applet more permissions than it would usually have.
For example, applets normally cannot read or write files on the client's machine. This is a good security measure. The user feels confident that they can use the applet without any bad consequences to their system.
Perhaps your applet needs to write a file on the user's system. You must get special permission from the user to do so. First, the programmer makes a trusted applet by digitally signing it. This is done so that the user can verify the signature and feel confidant that they trust the applet's creator not to damage their system.
For detailed information about signing applets, see here: http://developer.java.sun.com/developer/onlineTraining/Security/Fundamentals/Security.html#secSigning
Once the client has verified the signature and granted permission, your applet can proceed.
Generally speaking, you should not let your applet "out of the sandbox" (giving it more than normal permission) unless absolutely necessary.
Hope this helps.
Stephanie
 
anand rk
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Stephanie Grasson:
Hello Anand.
The reason for making a trusted applet is to give the applet more permissions than it would usually have.
For example, applets normally cannot read or write files on the client's machine. This is a good security measure. The user feels confident that they can use the applet without any bad consequences to their system.
Perhaps your applet needs to write a file on the user's system. You must get special permission from the user to do so. First, the programmer makes a trusted applet by digitally signing it. This is done so that the user can verify the signature and feel confidant that they trust the applet's creator not to damage their system.
For detailed information about signing applets, see here: http://developer.java.sun.com/developer/onlineTraining/Security/Fundament als/Security.html#secSigning
Once the client has verified the signature and granted permission, your applet can proceed.
Generally speaking, you should not let your applet "out of the sandbox" (giving it more than normal permission) unless absolutely necessary.
Hope this helps.
Stephanie



Stephanie thanx alot for ur xplanation it was real good
 
Thank you my well lotioned goddess! Here, have my favorite tiny ad!
The trailboss has a kickstarter
https://coderanch.com/t/754577/Garden-Master-kickstarter
reply
    Bookmark Topic Watch Topic
  • New Topic