Appendix 1: Java Security

                      

Home

Members

Project Design

Implementation Design

Simulation Results

Benefits and Drawbacks of our Project

Improvements, Applications And Related Work

Conclusion

References

Appendix 1: Java Security

Appendix 2: Incomplete Chunks

Appendix 3: Source Code

Demo: A Test Drive 

 




The Java implementation used in browsers restricts the applets to be run inside a “sandbox”, i.e., the browser does not allow the applet to access privileged resources, such as the file system, network, etc, due to obvious security risk associates with these operations when performed by malicious applets. Our client application requires both an access to user’s hard drive, in order to store the received file, and the ability to open network connections with other servers. Therefore the applet must request additional privileges. In order to request these privileges, the applet must be digitally signed (in Netscape), or the user must trust the applet (in Explorer). In Netscape browsers (version 4.xx) it is possible to allow unsigned applets to request these privileges as well.

 

The side effect of this method is that the user is prompted with a dialog box every time he runs the applet (unless he decides to permanently trust the applet).

 

In our project we use a test certificate issued by the Entrust demo server, to digitally sign the applet. The certificate expires on Sep 13, 1999, and a new certificate must be installed to run the applet after that date.

Please contact Genady or Nir regarding copyright issues 
For problems or questions regarding this web contact the members.
Last updated: Wednesday, September 08, 1999.