Trolino Dec 7, 2013 @ 8:42pm
Authorized Device help
Okay so when it says put in the name of the computer I do ("My real name" "PC") but it doesint work can anyone help.
< >
Showing 1-15 of 15 comments
WhereIsBusmin Dec 7, 2013 @ 8:43pm 
What message do you get?
Trolino Dec 7, 2013 @ 8:45pm 
Originally posted by WhereIsBusmin:
What message do you get?
Failed to Send Authorized Request (Pending)
~/beather.cz/ Dec 8, 2013 @ 12:00am 
it must be longer than 8 symbols i guess
Bad 💀 Motha Dec 8, 2013 @ 12:24am 
What I always do is, I give my computer a unique name in Computer Properties > Network

like UserName-SystemName

For example; Mike-GamingDesktop; Mike-SchoolLaptop

Something along those lines. Then I use that same name for the unique system name for Steam. So it makes it easier for me to tell the difference.
Trolino Dec 8, 2013 @ 8:27am 
Okay I'm gonna see if it works
Bad 💀 Motha Dec 8, 2013 @ 8:30am 
Originally posted by Trolino:
Okay I'm gonna see if it works

It can technically be any name u want. But if ever use your Steam account on multiple systems, then each system should be given a different name. The reason for different names (a unique name for each system) is that should u do any Download Queuing via Steam Mobile App of Steam via Browser, the queue system will show u the unique system names u've used and ask which one u want the download to queue for.
Last edited by Bad 💀 Motha; Dec 8, 2013 @ 8:31am
Homcias. Dec 8, 2013 @ 8:30am 
Did it work ?
Trolino Dec 8, 2013 @ 8:36am 
Okay I went into the Computers Properties and I change my name to something simple and I reset my computer to change it, and it still doesn't work I left the beta Yesterday. So it must be a bug or doesn't work in Canada who knows.
Trolino Dec 9, 2013 @ 5:36pm 
Still not working...
Originally posted by Trolino:
Okay I went into the Computers Properties and I change my name to something simple and I reset my computer to change it, and it still doesn't work I left the beta Yesterday. So it must be a bug or doesn't work in Canada who knows.
Dude, it could give a crap what the name of your PC is. This name is just to remind you what PC you authorized. The name you type in there can be anything as long as it is 8 digits or more. Anyway, sounds like you might have other issues.
Bad 💀 Motha Dec 9, 2013 @ 8:07pm 
Yea the names DO NOT matter, at all to anyone but u.
So don't make a fuss over it. But u can't edit the names from the authorized listing. The way you would apply and/or change a system name is when u are asked to re-verify your login, at the screen where u enter your SteamGuard code, there is a selection box to name the machine; and this is where u do that.

The list of Authorized Devices is just to let u keep track of systems that u've logged into before and/or still have the login info access.

So for example it might look something like this...

DEVICE NAME | SHARING STATUS | LIBRARY LAST ACCESSED
Your-Win8-Desktop | Authorized (revoke) | Dec 9, 2013
Your-Win7-Desktop | Authorized (revoke) | Dec 9, 2013
Your-Work-Laptop | Authorized (revoke) | Dec 9, 2013
Mom-Laptop | Authorized (revoke) | Dec 8, 2013
Brother-Desktop | Authorized (revoke) | Dec 7, 2013

If I no longer want access on a certain system, then I would click the REVOKE text button.

If u should ever sign into Steam using your account on a new/different system not already in your listing, it should ask you to name that system. Should u ever redo your OS, this should also come up and ask u. Another reason it might come up is if your ISP Host IP# changes (which it usually does at some point) then it may ask u to re-verify your login.

If u do not already, please ensure you have SteamGuard enabled for your account.
Last edited by Bad 💀 Motha; Dec 9, 2013 @ 8:11pm
Red Eagle LXIX Feb 11, 2014 @ 9:44am 
Actually, I find it most often comes up due to web browsers and I wish there was a way to actually list the authorized devices.
I love when if you've browsed Steam community too much, you start getting : Error 413 Request Entity Too Large
At which point you must clear the cookies and cache from the browser as related to Steam (or the Steam client if you get that while using it). Thus causing the browser and/or the Steam client to need to be re-authorized.

Every one of those fake bad authorizations is another potential risk that your account can get stolen via hash collision.

Worse, since Steam fails to provide any way to eliminate them except completely de-authorizing all devices (which give trade and market temp bans) the risk is essentially a permanent and ever increasing risk the more one uses Steam.

Red Eagle LXIX Feb 11, 2014 @ 9:52am 
Originally posted by Muppet among Puppets:
Originally posted by Red Eagle LXIX:
Every one of those fake bad authorizations is another potential risk that your account can get stolen via hash collision.
An authorisation is made on a specific request. You cant use an old number for another computer.....
Try it yourself. Use the code for your client for your browser. Later.
HASH collision.
Not code reuse.
Steam service stores a hash of the Authorized device, that is part of how it recognizes authorized devices.
One can in theory create a response that would have the same HASH value as that of a machine for which you've already typed the code and created an authorization storage.

The more authorized devices one has against their account, the greater the potential to have the account compromised via the hash collision method.
Red Eagle LXIX Feb 11, 2014 @ 10:07am 
Originally posted by Muppet among Puppets:
Originally posted by Red Eagle LXIX:
HASH collision.
Not code reuse.
Steam service stores a hash of the Authorized device, that is part of how it recognizes authorized devices.
One can in theory create a response that would have the same HASH value as that of a machine for which you've already typed the code and created an authorization storage.

The more authorized devices one has against their account, the greater the potential to have the account compromised via the hash collision method.
Is it based on sources, or your guessing?
And describe a practicable scene that would let us lose our accounts.

And what keeps you from deauthorize other attempts you made?
Based on the already published information from Steam.
Do I think hash collision is a viable attack method, no. Bad passwords and social engineering would be much more simple and easier.

Yes, it is possible to remove authorized devices from Steam, by de-authorizing all devices.
That puts a temporary usage ban on Trading and Marketplace though. As such people are less inclined to use it and clear the building list of "authorized devices".

If there was a method, whereby one could revoke devices as suggested by the post a few above, then there wouldn't be a problem. Nor would there be a problem if de-authorizing all devices didn't impose the temporary trade and market bans. I do understand and agree to the temp trade and market bans though to prevent compromised accounts from losing their stuff by having everything de-authorized and then trading their stuff away while they cannot gain access.

Steam should implement such a system as the one mocked up above with the ability to see and revoke single devices.

Trolino Feb 21, 2014 @ 5:16pm 
The Bug stopped after a while you guys dont need to comment anymore
< >
Showing 1-15 of 15 comments
Per page: 1530 50

Date Posted: Dec 7, 2013 @ 8:42pm
Posts: 15