The steam-py-lib from failspy

[Discussion] protobuf fields

Regarding

Lines 105 to 137 in 3db3cfe

    
               IMPORTANT: 
        
                   Actually, at real login page 
        
                   steam handles function little bit different. 
        
                   e.g. https://api.steampowered.com/IAuthenticationService/BeginAuthSessionViaCredentials/v1 
        
                   can handle multipart/form-data; with something like. 
        
                   { 
        
                       input_protobuf_encoded: EgxhbmFjb25kYXJ0dXIa2AJodHgzZzlJaWY4dGE4RGxqR2VWbncwZWpxdi9uNDByRkZxaFduVk12VFFhRm1ZU1F4MHlrYUlJNmFURlVJWEQ5Z2VXMTlObWJDc3pydmNQZ1RTVllyOWl0SW5EWjgzMVh0YWtOaHJaUk9JN1lvMzhpb2xHRmdHdVBZT3NsekErTHZNZlJoQ3YzL1JFaEpNQlhjaXhzNklRRTZjbnM4d1JWbGI0TVA1Nzd0MHpGajRpcWF4U21KbnVjRDh5YzVIVkYvMERlMnFKd3dGTG0vR3B4SEdreFFlQURzZi9OTXJMTUszcWxnR3NLZm4ycGxNOGhkMzF3YnErSUlCZkNJb3dFZWExaUpJcmVjYkdLT0EvRlJ5VFpSQlVoVitLQmt6TGk3THY1UjVNYVRJSzNPTCtCMUZnZ2xWSG94c0ErTm5BMHVqSVZWZ0ZRdGpDL2tMTjd0SmhYamc9PSCA+aCT0ggoATgBQgVTdG9yZUqBAQp9TW96aWxsYS81LjAgKFdpbmRvd3MgTlQgMTAuMDsgV2luNjQ7IHg2NCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzExNi4wLjAuMCBTYWZhcmkvNTM3LjM2IE9QUi8xMDIuMC4wLjAQAlgI 
        
                   } 
        
                   it's protobuf encoded value. You can decode it here: 
        
                       https://protobuf-decoder.netlify.app 
        
                   some fields I can understand: 
        
                       2) string - steamlogin 
        
                       3) string - encrypted password 
        
                       4) timestamp to map to a key - STime 
        
                       5) some INT (probably it's always 1) it's DEPRECATED 
        
                       7) whether we are requesting a persistent or an ephemeral session 
        
                       8) (EMachineAuthWebDomain) identifier of client requesting auth. 
        
                          e.g. "Store" 
        
                       9) Protobuf of device type (see CAuthentication_DeviceDetails): 
        
                           9.1) string - User-Agent 
        
                           9.2) Int - platform identifier e.g. 2 (means Web Browser) 
        
                               (See EAuthTokenPlatformType protobuf). 
        
                           9.3) os_type (MOSTLY NOT PRESENTED IN REAL REQUESTS) 
        
                           9.4) gaming_device_type (MOSTLY NOT PRESENTED IN REAL REQUESTS) 
        
                       11) UNDOCUMENTED AT ALL: Some number (like 8) 
        
                       FIELD NUMBERS I SKIPPED MEANS THEY ARE NOT PRESENTED IN REAL REQUEST 
        
                   We currently uses basic multipart/form-data and "key-value" 
        
                   data presentation. 
        
                   But I  Think, it's important to know, that real steam works differently, 
        
                   and maybe we can once upon a time simulate it's REAL behavior.

Perhaps you could take a look at:

failspy / steam-py-lib Goto Github PK

steam-py-lib's People

Stargazers

Forkers

steam-py-lib's Issues

[Discussion] protobuf fields

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

	IMPORTANT:
	Actually, at real login page
	steam handles function little bit different.
	e.g. https://api.steampowered.com/IAuthenticationService/BeginAuthSessionViaCredentials/v1
	can handle multipart/form-data; with something like.

	{
	input_protobuf_encoded: EgxhbmFjb25kYXJ0dXIa2AJodHgzZzlJaWY4dGE4RGxqR2VWbncwZWpxdi9uNDByRkZxaFduVk12VFFhRm1ZU1F4MHlrYUlJNmFURlVJWEQ5Z2VXMTlObWJDc3pydmNQZ1RTVllyOWl0SW5EWjgzMVh0YWtOaHJaUk9JN1lvMzhpb2xHRmdHdVBZT3NsekErTHZNZlJoQ3YzL1JFaEpNQlhjaXhzNklRRTZjbnM4d1JWbGI0TVA1Nzd0MHpGajRpcWF4U21KbnVjRDh5YzVIVkYvMERlMnFKd3dGTG0vR3B4SEdreFFlQURzZi9OTXJMTUszcWxnR3NLZm4ycGxNOGhkMzF3YnErSUlCZkNJb3dFZWExaUpJcmVjYkdLT0EvRlJ5VFpSQlVoVitLQmt6TGk3THY1UjVNYVRJSzNPTCtCMUZnZ2xWSG94c0ErTm5BMHVqSVZWZ0ZRdGpDL2tMTjd0SmhYamc9PSCA+aCT0ggoATgBQgVTdG9yZUqBAQp9TW96aWxsYS81LjAgKFdpbmRvd3MgTlQgMTAuMDsgV2luNjQ7IHg2NCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzExNi4wLjAuMCBTYWZhcmkvNTM3LjM2IE9QUi8xMDIuMC4wLjAQAlgI
	}
	it's protobuf encoded value. You can decode it here:
	https://protobuf-decoder.netlify.app

	some fields I can understand:
	2) string - steamlogin
	3) string - encrypted password
	4) timestamp to map to a key - STime
	5) some INT (probably it's always 1) it's DEPRECATED
	7) whether we are requesting a persistent or an ephemeral session
	8) (EMachineAuthWebDomain) identifier of client requesting auth.
	e.g. "Store"
	9) Protobuf of device type (see CAuthentication_DeviceDetails):
	9.1) string - User-Agent
	9.2) Int - platform identifier e.g. 2 (means Web Browser)
	(See EAuthTokenPlatformType protobuf).
	9.3) os_type (MOSTLY NOT PRESENTED IN REAL REQUESTS)
	9.4) gaming_device_type (MOSTLY NOT PRESENTED IN REAL REQUESTS)
	11) UNDOCUMENTED AT ALL: Some number (like 8)

	FIELD NUMBERS I SKIPPED MEANS THEY ARE NOT PRESENTED IN REAL REQUEST
	We currently uses basic multipart/form-data and "key-value"
	data presentation.
	But I Think, it's important to know, that real steam works differently,
	and maybe we can once upon a time simulate it's REAL behavior.