Closed GoogleCodeExporter closed 9 years ago
Sorry, tried to set it to feature request but just dont see where to do that.
Original comment by wil...@gmail.com
on 23 Apr 2013 at 5:05
I've changed it to a feature request.
Sounds like a good idea and useful change. Can we flush out a bit more
information and how you would use it.
So are you saying you would like winauth to show all the authenticators
(presumably you choose which ones or it could just auto load them all and you
hide some).
Do you typically have the same set of authenticator at any time? Would this
change often?
Do you care how the authenticators are stored (in separate files) or not?..give
me more leeway in changing how they work. For instance, this would be important
for portability.
What encryption do you use now and would you like it to change? Password per
authenticator or single password for a whole group?
Would you do the same things to use the codes? i.e. just see them or
copy/paste, or just a hotkey per code? Something more advanced, e.g. automated
Do you care about skins?
Original comment by winauth
on 23 Apr 2013 at 6:27
Darn I had a big lengthy comment written to answer your questions and it
disappeared. I will rewrite this now to answer :), cheers btw!
Original comment by wil...@gmail.com
on 24 Apr 2013 at 6:32
See below for answers in line to your questions:
---So are you saying you would like winauth to show all the authenticators
(presumably you choose which ones or it could just auto load them all and you
hide some).---
I would if possible like for winauth to have an option to show multiple codes
from different generators on 1 panel. IE you will have a panel that shows codes
like below and it can auto load all of them that you have it running at start,
or if you want you can have an option per code to have it hide from the main
view and allow users to click on specific code generators in a drop down to
show that code. Here's the example of how I think it would look:
/-------------------------\
| WinAuth V.UBER |
| Named Blizzard Gen 1: |
| TheCode |
| |
| Name Blizzard Gen 2: |
| TheCode |
| |
| Named GW2 Gen 1: |
| TheCode |
| |
| Named Rift Gen 1: |
| TheCode |
\-------------------------/
That would be like 1 panel.
---Do you typically have the same set of authenticator at any time? Would this
change often?---
I use 4 Authenticators for WoW, 4 for Rift, and 4 for GW2. This is due to
sharing my authenticators with my fiance. So that we can just grab our tablet
and look up each others codes. Mine are named MyName TheNameOfTheGame (Primary)
and MyName TheNameOfTheGame (Secondary) for instance to help keep them
organized that way sorting keeps them in the right alphabetical order.
---Do you care how the authenticators are stored (in separate files) or
not?..give me more leeway in changing how they work. For instance, this would
be important for portability.---
I don't see any issues with storing them in any method, though for your later
question regarding security it may be best to encrypt each in a different file
to protect it that way if a user got ahold of your directory they would need to
crack the encryption on each authenticator so as to not have access to all of
your games.
---What encryption do you use now and would you like it to change? Password per
authenticator or single password for a whole group?---
I would say password per authenticator for viewing the actual strings that way
they can't just edit it but for accessing the over-all ui to show the codes, I
would say maybe 1 master password?
---Would you do the same things to use the codes? i.e. just see them or
copy/paste, or just a hotkey per code? Something more advanced, e.g.
automated---
I would say just see them and type them manually, I don't believe in Copy /
Pasting this type of data, too many chances for interception of the data.
---Do you care about skins?---
I'm a minimalist at heart so I believe the cleaner, techy feel the better :).
See the attached mockup. Here's the layout,
Top Row is the Title Bar. Right side 3 ---'s is the click area to get the
options drop down to pop up. Things like what Settings / Areas to open up
specific Authenticators can be in here.
The small bar that you see just under this title bar is the Timer that shows
how long these codes will be shown since the code provided is generated based
on the time the user will know how long he has until it switched.
The next big block is as follows:
Left Icon can be changed in the options for this authenticator to whatever Icon
you want. You can have the GW2 / Blizzard / Rift Icon here or just the Generic
Lock.
Top Row on each "Authenticator" is where the Custom Name of that Authenticator
is shown. Each of these Authenticators is Sorted Alphabetically by this Name,
IE 1 2 3 will come in order then it will sort by the Name type, ie if it says
Blizzard that will be before GuildWars2 then (Primary) will be before
(Secondary).
Bottom Row will obviously be the actual Code that's Generated.
When a user right clicks on any of these Authenticator Rows they get options
for that Authenticator like Sync Time (in case the codes being provided aren't
in sync with the current time they should be). or View Details, or Rename, etc.
View Details would show things like the 2 sets of Blizzard Details ie the
EU-XXXX-XXXX-XXXX or US-XXXX-XXXX-XXXX numbers.
I really hope this helps. I think this would be a totally banging Authenticator
that you could get lots of donations for. I know I would donate!
Let me know what you think?
Original comment by wil...@gmail.com
on 24 Apr 2013 at 7:12
Attachments:
Thanks. That has helped a lot.
This interests me because I am finding I am stacking up a whole load of
authenticators too, not so much for games anymore, but email accounts and other
websites that are gradually adding 2-factor authentication. I use winauth for
them (or a duplicate on my phone) and can understand the pain in switching back
and forth bewteen each one. I never honestly imagined there would be so many.
So yep. This is something I want to do. Can't promise it's going to be quick,
orders of weeks probably.
Combing what you put together (and reiterating most of it), I'm thinking of:
1. Display very much like you have in your mockup, with a line per
authenticator ordered by name or added date. Show the name and the code, with a
way to lock/unlock and get at the details (i.e. raw key, serial, etc). Likely
when you add one you will choose if you want it shown by default or not. In
that case you'd see "------" until you click the line and then it would
display. This is because it would also be an opportunity to prompt for the
password per authenticator to show the code.
2. If you have another "set" they can be loaded from a different file
3. Locking/unlocking will unload/load the authenticator, i.e. back to "------"
4. All authenticators will be stored in a single portable file. There will be
an optional master password (like now) as well as using the built-in Windows
encryption so it is useless if copied to another machine. Additionally the key
of each authenticator can be encrypted with another password.
5. Some way to do a "copy" if allowed
6. Hotkey can be assigned to each authenticator to run the script - like
now...which I use :)
7. Skins maybe for the whole panel or each row, but probably just a background
image rather than the full button control of now.
You said tablet, so are you using a Win8 Rt device or something? Curious.
Probably be developed for Win desktop first, but don't see why I can't do a
Win8 app too.
Original comment by winauth
on 25 Apr 2013 at 11:49
[deleted comment]
I use a Nexus tablet. I want to get my hands on a MS Surface Tablet for sure,
but yeah Desktop first and I would love to offer my services helping in any way
I can. I am currently learning C#, have experience with various other
languages. Just been a long time since I've done anything with programming. I
would be happy to try and help though!
Original comment by wil...@gmail.com
on 26 Apr 2013 at 12:17
I LOVE the way it looks. Would you be willing to let me help test it? I also
have a Surface Pro Tablet now so I would love to see how it runs on that.
Original comment by wil...@gmail.com
on 7 Jun 2013 at 8:52
Thanks. Still not quite ready for testing yet, but I'll definitely let you when
it is, so you can start trying it and can give some feedback.
Original comment by winauth
on 8 Jun 2013 at 3:05
Ah man, the waiting hurts!!! Can't wait lol.
Original comment by wil...@gmail.com
on 23 Jun 2013 at 10:22
Sorry, work and life just get in my sometimes! I am back on it and really hope
to have something you can play with by the end of the week.
Original comment by winauth
on 24 Jun 2013 at 11:47
Please see email I sent.
Original comment by winauth
on 28 Jun 2013 at 6:06
In case you didn't see the replies.... Holy you deserve a big ole wet slobbery
kiss... I'm trying to see if I can get some source code to show how Rift's
authenticator is done so you could have that and then this would be the
ultimate Game Authenticator...
Now let me donate some money for this kick ass wonderful program!
Original comment by wil...@gmail.com
on 29 Jun 2013 at 5:12
Aaaaaaand....we're done.
Original comment by winauth
on 4 Sep 2013 at 3:27
Original issue reported on code.google.com by
wil...@gmail.com
on 23 Apr 2013 at 5:04