Jump to content
McKay Development

Disparency between recentSteam Logins and teh Authorized devices


Recommended Posts

Posted

I am seeing a weird pattern the logins are all in the right place but steam shows authorized devices sometimes way off target and issues the your steam account was accessed by some one else y is that hapening any clue we use trading sites also so they collect our steam token too.

Screenshot_2563.png

Screenshot_2564.png

Screenshot_2565.png

Screenshot_2566.png

Screenshot_2567.png

Screenshot_2568.png

14 minutes ago, TheMaster said:

I am seeing a weird pattern the logins are all in the right place but steam shows authorized devices sometimes way off target and issues the your steam account was accessed by some one else y is that hapening any clue we use trading sites also so they collect our steam token too.

Screenshot_2563.png

Screenshot_2564.png

Screenshot_2565.png

Screenshot_2566.png

Screenshot_2567.png

Screenshot_2568.png

@Dr. McKay

Posted

i prompted cursor to find the reason can you take a look at this response and see if its useful ?
 

Bug confirmed

The issue is that steam-user does not pass the httpProxy option to LoginSession, even though steam-session supports it.

The bug

File: E:\Bots\node_modules\steam-user\components\03-messages.js (lines 738-750) Current code (broken):_getLoginSession() {
    if (!this._loginSession) {
        let options = {
            transport: new CMAuthTransport(this),
            machineId: this._logOnDetails?.machine_id
        };
        
        let customMachineName = this._logOnDetails?.machine_name || '';
        if (customMachineName.length > 0) {
            options.machineFriendlyName = customMachineName;
        }
        
        this._loginSession = new LoginSession(EAuthTokenPlatformType.SteamClientoptions);
        //  Missing: httpProxy is NOT passed!
    }
    
    return this._loginSession;
 

What should happen

steam-session's LoginSession accepts httpProxy in its options (see interfaces-external.ts line 46), and uses it to create a proxied HTTP client (see LoginSession.ts lines 116-117 and 122-125).

The fix

Pass the proxy from steam-user's options:_getLoginSession() {
    if (!this._loginSession) {
        let options = {
            transport: new CMAuthTransport(this),
            machineId: this._logOnDetails?.machine_id
        };
        
        //  ADD THIS:
        if (this.options.httpProxy) {
            options.httpProxy = this.options.httpProxy;
        }
        
        let customMachineName = this._logOnDetails?.machine_name || '';
        if (customMachineName.length > 0) {
            options.machineFriendlyName = customMachineName;
        }
        
        this._loginSession = new LoginSession(EAuthTokenPlatformType.SteamClientoptions);
    }
    
    return this._loginSession;
}

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...