password : Java Glossary

This view this page, you should have a recent Java installed, preferably 32-bit JRE (Java Runtime Environment) 1.7.0_04.
password  password
A word you use to prove that you are truly you to a computer. You will have a password to log on to your operating system, one for each affiliate, and even one for various free services on the web. Snoops can look at your files without knowing your login password by booting with an Ubuntu Linux CD (Compact Disk) and examining your files, bypassing Windows and its passwords. To protect against that, you need to encrypt your files. Then you have passwords on your files, not just Windows as a whole.
Selecting Passwords Server
Implementing Passwords Puzzles
Digests Generating Passwords
Graphical Passwords Diceware
Client Links

Selecting Passwords

Passwords that are easy to guess include the names of loved ones and relatives, words in the dictionary, especially ones with strong emotional connotation like God, whale, love.

A tool can crack your password just by trying all words in the dictionary. So you must disguise them. Add digits, mix the case. This little program will generate you an impossible to guess password. If want to make sure I am not keeping a copy, download the source, check the program out, and run it on your own machine.

Sorry, you need Java 1.3 or later to run this Applet.

If, Password, the above Password Generator Java Applet does not work…

  1. If Copy/Paste (Ctrl-C/Ctrl-V) do not work, you can turn them back on by modifying your java.policy file. This is not for the novice or faint of heart. instructions Your alternative is to download this program and run it without a browser.
  2. Often problems can be fixed simply by clicking the reload button on your browser.
  3. Make sure you have both JavaScript and Java enabled in your browser.
  4. This Java Applet needs 32-bit (not 64-bit) Java 1.3 or later. For best results use the latest 1.7.0_04. If you have both 32 and 64-bit JVMs installed, in the Java Control Panel, configure your 32-bit java.exe as the user JVM and your 64-bit java.exe as the system JVM. You also need a recent browser.
  5. It works under any operating system that supports Java e.g. W2K/XP/W2003/Vista/W7-32/W7-64/Linux/Ubuntu/Solaris/OSX
  6. You should see the Applet above looking much like this screenshot. If you don’t, the following hints should help you get it working:
  7. Especially if this Applet has worked before, try clearing the browser cache and rebooting.
  8. To ensure your Java is up to date, check with Wassup. First, download it and run it as an application independent of your browser, then run it online as an Applet to add the complication of your browser.
  9. If the above Applet does not work, check the Java console for error messages.
  10. If the above Applet does not work, you might have better luck with the downloadable version available below.
  11. If you are using Mac OS X and would like an improved Look and Feel, download the QuaQua look & feel from randelshofer.ch/quaqua. UnZip the contained quaqua.jar and install it in ~/Library/Java/Extensions or one of the other ext dirs.
  12. If you are using Microsoft Internet Explorer 7, 8 or 9, try another browser. Seriously. Microsoft has taken great pains, over and over, to screw up Java and every other multi-platform standardisation.
  13. If you are using Microsoft Internet Explorer 7, 8 or 9, you must click to allow blocked content permission for Active X to run. This also gives permission to Java to run. Click the Information bar, and then click Allow blocked content. Unfortunately, this also allows dangerous ActiveX code to run. However, you must do this in order to get access to perfectly-safe Java Applets running in a sandbox. This is part of Microsoft’s war on Java. Don’t put up with it! Use a different browser.
  14. If you are using Microsoft Internet Explorer 9, makes sure the Java Plug-In SSV helper add-in is installed and enabled. If it is not, try reinstalling the Java JRE.
  15. If you have Windows 7 64-bit and Internet Explorer 64-bit, in theory you can use 64-bit Java, but I never been able to get it to work.
  16. Try upgrading to a more recent version of your browser, or try a different browser e.g. Firefox, SeaMonkey, Safari or Avant.
  17. If you still can’t get the program working click HELP for more detail.
  18. If you can’t get the above Applet working after trying the advice above and from the HELP button below, have bugs to report or ideas to improve the program or its documentation, please send me an email atemail Roedy Green.
Java powered   Get New Java  Get New Browser   Help

If the print is too small to see, use the Opera browser and zoom. Or copy/paste the generated password blind.

Implementing Passwords

In a highly secure system, each end has a public and private key. They each encrypt and digitally sign a random message for the other to establish identity. Even these have to be carefully designed to withstand a man-in-the-middle attack.

There are some lower tech alternatives:

Digest Passwords

Servers often don’t store bald passwords. They store some sort of digest of them. That way if someone cracks the password file, they still don’t know the passwords.

Typically raw binary bytes generated by such authentication schemes are exchanged in base64.

Tomcat has a single signon so that all applications in a realm share the same set of user-ids and passwords. If a user logs into one application, he is logged into all. This scheme uses cookies to authenticate each request.

Tomcat lets you configure the tables and columns to automatically look up and validate passwords. Caucho Resin similarly lets you configure SQL (Standard Query Language) queries to automatically find the passwords in your database.

Graphical Passwords

Another way is to use graphical passwords, easier for the user to remember, and harder to steal. The basic idea is you display a complex image to the user and he selects a number of click points. I suspect this scheme is much less secure than it creators claim, since there are a limited number of natural points of interest in a photo, which could be easily discovered by showing the photo to 100 people.

Passwords at the Client

When your Applet or JWS (Java Web Start) applications is pretending to be a browser talking to a server, you can use the java.net.Authenticator to automatically insert the userid and password base64-encoded in your HTTP (Hypertext Transfer Protocol) headers in the Authorization field. If the server does not like you userid/password combination in return a 401 Unauthorized response code. The server gives you no hint as to whether the userid or the password is the problem. You might consider this obnoxious behaviour, but it is done that way to make life difficult for people trying to hack the system.

Passwords at the Server

How passwords are handled is specific to each application server. Most will provide a rudimentary, unsuitable-for-production flat file scheme. The better ones will provide a means of configuring a database for the users. Almost all allow you to extend a class to provide a custom source.

Java Servlets defines a simple password scheme controlled entirely by a flat file web.xml. This would be suitable for a small company where the list of users and passwords could be maintained with a text editor by the system administrator.

The best approach (for expandability) is to incorporate a third party SSO (Single Sign-On) (some application servers come with one). This allows you to add new applications and share the login across them with a minimum of effort. Also, they typically plug into an existing LDAP (Lightweight Directory Access Protocol) taking user and password management out of the application’s hands. This allows corporations to take advantage of existing LDAP data when deploying applications.

Tomcat offers five different interfaces to databases of passwords. JDBC (Java Data Base Connectivity) Realm lets you interface to a SQL users and userroles tables. You configure the name of your table containing the user ids and passwords (among other things) and your roles table which describes which roles a user can play. You assign Tomcat a userid/password and jDBC connect string to give it with read-only access to your database to perform the authentications. It is much simpler than it first looks.

Puzzles

Things I have not yet figured out include:

Diceware

This is a scheme for picking a password without using a computer, just some casino dice. The paranoid instructions are somewhat tongue in cheek. The scheme is just as vulnerable as any other if there is a keystroke logger (hardware or software) installed on your computer. It is just as vulnerable as other schemes to others discovering a copy of your password stored somewhere. The big advantage is you don’t have to trust the author of password-generating software.


CMP homejump to top You can get the freshest copy of this page from: or possibly from your local J: drive (Java virtual drive/mindprod.com website mirror)
http://mindprod.com/jgloss/password.html J:\mindprod\jgloss\password.html
logo
Please email your , letters to the editor, errors, omissions, typos, formatting errors, ambiguities, unclear wording, broken/redirected link reports, suggestions to improve this page or comments to Roedy Green : feedback email. If you want your message, your name or email kept confidential, not considered for public posting, please explicitly specify that. Unless you state otherwise, I will treat your message as a letter to the editor that I may or may not publish in the feedback section. After that, it will be too late to retract it. If you disagree with something I said, please quote it and cite the web page where you found it, tell me why you think it is wrong, and, if possible, provide some supporting evidence. Threatening to kill me or spouting obscenities has yet to persuade me to change my mind.
mindprod.com IP:[65.110.21.43]
view BlogYour face IP:[38.107.179.211]
You are visitor number 26,992.