PC Authenticator - A free WoW Authenticator

[Sednogmah]

There are more of these around I see

I had developed a native Windows version a while back, so have tidied it up and put in on Google code if anyone is interested. winauth - Project Hosting on Google Code

It is open-source so you can look it over and check there is nothing fishy going on. There is a pre-built exe, but feel free to build it yourself. It auto-refreshes the key as needed, time syncs and encrypts the secret authenticator key with a password - unlike the Mobile Authenticator, which just XORs the data with a hard coded key.

It also can load the key used by the Android Blizzard Mobile authenticator, so I use it as a backup and sometimes more convenient version.

Wow. That's pretty clean source! Respect.

[Deapno]

What happened to the EU download version?

[Tewpac]

Thanks, this is working fine

[cdm]

Wow. That's pretty clean source! Respect.

Thanks....if only my work code were that neat ;p

[Skalla]

i need to know,

can i get banned for this?
What should i input for username/pass when i create a backup?

[cdm]

They have not said anything against software emulators, but have at least acknowledged they exist, so a ban is unlikely. You aren't breaking any ToS.

From Blue Tech Support: forums.worldofwarcraft.com/thread.html?sid=1&topicId=23140265046

technically* you can run an authenticator on a PC but it requires fancy emulation plus a lot of loops and it isn't supported at all

Of course, for you own peace of mind, I would look at using an open-source version so at least you know exactly what it does and don't download a malicious version of a pre-built one.

*plugs own open-source version

winauth - Battle.net Authenticator for Windows and Windows Mobile

[sed-]

idk i cant get his import feature to work. for example i hit export, than del than i hit import put in the info and says not valid

[aribehn]

EU download link isn't working :<

EDIT: No worries. Filebeam is just being a bitch :<

[dethfalcin]

Jadd, you mentionned earlier you didn't know why it was popping an error message while registering the "fake" authenticator. Although you don't know, I think there are reasons to believe THEY DO KNOW. I disabled authenticator after trying it. I don't know if that's why, but my core hound is now gone (1 day after.. not immediately after I disabled). I got no ban though. They might be aware.

Core hound disappears after you remove any authenticator, real or fake.

[frozty96]

When i try to use backup, i get this error:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
at System.Net.HttpWebRequest.GetResponse()
at PC_Authenticator.GetWebpage.Fetch(String webpage)
at PC_Authenticator.frmRestore.btnRestore_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
PC Authenticator
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/PC%20Authenticator.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
BlizzAuthenticator
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/BlizzAuthenticator.DLL
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
g7dwdf5c
Assembly Version: 1.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[earthFlower]

LOL at this, why would anyone use a virtual authenticator?

[Tobblish]

LOL at this, why would anyone use a virtual authenticator?

why would anyone use a real authenticator? :P

[Copperman67]

Nice, thanks !

[LegionGuard3000]

Confirmed! 1+ rep!


From: The WoW Dev Team
Subject: Core Hound Pup

As a thank you for attaching an authenticator to your Battle.net account, we'd like to present you with this fiery, friendly core hound pup.

Please give him a warm welcome!

The WoW Dev Team

[jackdryden123]

Downloaded this last night, worked for like half an hour, then i tried to log into WoW, put my password in as always, then opened up the authenticator, got the code, put it in WoW, and BAM! Wrong password, i tried it over and over, around 40 times, so i mailed Blizz and got the authenticator taken off my account...i was really happy i got this tool as i was hacked about a month ago. But i darnt risk trying another incase i have to mess about waiting for blizz to take that one off my account aswell...they told me, the key i used to attach the authenticator the one that starts with EU, had changed, so the version of the authenticator i was using was running with a different key, thus meaning was giving me wrong codes, which led up to the problem with it saying i had typed wrong password...has this happened to anyone else?