Code:
sys.programGroupAllUsers$Boolean=true
secret=THIS-IS-A-DUMMY-SECRET
sys.programGroupDisabled$Boolean=false
sys.languageId=en
sys.programGroupName=JAuth OpenAuth Desktop Client
sys.installationDir=C\:\\Program Files\\JAuth
Ok so right now it is using some algorithm to generate those 6 digit pins from "THIS-IS-A-DUMMY-SECRET" and the current time rounded to the nearest 30 seconds? So I can either change the text there or do what you recommend and open a file consisting of some secret string (key, whatever) using:
Code:
java -jar jauth.jar secret.txt
Or (same thing) create a shortcut pointing to:
"jauth.exe glbse.secret"
If I set up authenticator on bitfloor I will need to input my secret string. If I used google authenticator it would generate a secret string for me which I would then be telling bitfloor. Then when I log in bitfloor will ask me to generate a pin and input it, while at the same time generating one on their end. If these are the same I am able to log in. Also, if I write down the secret provided by google authenticator I can simply input that into JAuth if I lose my phone, which will then generate the 6 digit pin that allows me to log in.
If I only use a computer, should I have the secret.txt file saved only in a truecrypt volume? It seems insecure to have it just out in the open.
.
