pinsickle 17 Junior Poster in Training

The easiest way would not be not to store the password but a hash of the password. That way even if your packets are sniffed the person only sees garbage. When the user creates a password or logs in you can hash the password prior to sending it over the the network. The on the server side you can compare the send hash to the hash you have stored for the user in your database. Just Google hashing with salt to see examples.

iamthwee commented: Agrees +15
pinsickle 17 Junior Poster in Training

The method is overloaded to handle character arrays but not overloaded for any other array. http://download.oracle.com/javase/1.4.2/docs/api/java/io/PrintStream.html

jon.kiparsky commented: Yep. Good answer. +2
pinsickle 17 Junior Poster in Training

I've noticed every time someone claims they have an easy or quick question, you can count on a minimum of a week or two of struggle to get the problem figured out.

If it was so easy, why do you have to ask? :icon_wink:

Lol true, I actually it figured out last night (was trying to make it too idea complicated). Just finished debugging it and it seems to work.