Steam 설치
로그인
|
언어
简体中文(중국어 간체)
繁體中文(중국어 번체)
日本語(일본어)
ไทย(태국어)
Български(불가리아어)
Čeština(체코어)
Dansk(덴마크어)
Deutsch(독일어)
English(영어)
Español - España(스페인어 - 스페인)
Español - Latinoamérica(스페인어 - 중남미)
Ελληνικά(그리스어)
Français(프랑스어)
Italiano(이탈리아어)
Bahasa Indonesia(인도네시아어)
Magyar(헝가리어)
Nederlands(네덜란드어)
Norsk(노르웨이어)
Polski(폴란드어)
Português(포르투갈어 - 포르투갈)
Português - Brasil(포르투갈어 - 브라질)
Română(루마니아어)
Русский(러시아어)
Suomi(핀란드어)
Svenska(스웨덴어)
Türkçe(튀르키예어)
Tiếng Việt(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
This is a very strange statement as it's a function of how the API is used by the client, not the key at all. Again, this is so far off the topic of Steam authentication I don't know what to say.
Steam Guard Mobile IS 2fa.
Secondly as pointed out by Reboot it is directly tied to trading on Steam as well as securing your Steam account.
Op's issue is the lack of an alternative to Steam Guard for use sans-phone, a fairly reasonable request and point of discussion for many reasons.
Normally one would simply use a but API compatible 2FA system, as many others systems do, including banks but Valve does not allow that currently. Futher, they allow no other 2FA implementations despite there being industry standards and that their tool is definitely using one of them.
@ReBoot pointed out another example used for banking primarily in Germany, which is more than a bit unrelated, but notably a good example of how a published standard allows multiple organizations to interoperate.
This is the exactly right statement. The SGMA fulfils 2 functions:
1. Login codes
2. Transaction confirmation
What you're talking about, all this key-exchange-stuff, matters for 1. What happens during 2FA setup is the server & the authenticator exchanging secret information from which (& the time stamp) the generator then generates codes. The point of the system is this secret exchange being required once and only once, during setup.
None of this matters for 2. For obvious reasons, exchanging all the secrets neccessary for later transactions during setup is impossible. I mean, do you know every single trade you'll do on Steam EVER, after setting up the SGMA? Right, you don't. Neither do I. That's why, for market/trade confirmations, the authenticator has to get the current state from the server, the current information about the current transaction. Feel free to show me one 2FA standard covering this scenario. I don't know of any. This doesn't mean there's none, but so far, you aren't talking about one. You're talking about the standard 2FA process of exchanging secrets during set up and then never again.
None of which alters Steam Guard Mobile is for trading and securing your Steam account and Valve do not need to allow other 2fa solutions until and if ever Gabe Newells account is compromised.
To avoid further confusion, let's go back to the basics:
Some relevant notes:
Nothing to clarify.
Valve does not need to add additional 2fa for niche users who fail to grasp, Gabe Newell's account remains uncompromised because he did not give away the key to the door, the Steam Guard Mobile code, even though those wanting change claim it is not secure.
If you want to explain me how an existing 2FA solution would cover market/trading, shoot. Don't make things complicated, just show me, how exactly Yubikey or another standard solution would cover the scenario of market/trading confirmations.
Plain and simple explain me how this would work.
Create a request in suggestions and ideas. It would be like having whatapp to dektop... maybe
Jessecar96 version github. Rest are hacks....
Deactivating it gives you a 15 day restriction.
Using the same number and transferring it correctly...
https://help.steampowered.com/en/faqs/view/7EFD-3CAE-64D3-1C31#transfer
2 day holds on trades for the following 2 days.
2 day holds on Market listings for about the following ~36 hours.