@mega-yfue/eufy-sdk 0.2.0-beta.15 → 0.2.0-beta.16

package/dist/transport/http/mega-client.d.ts

@@ -179,6 +179,13 @@ export declare class MegaHttpClient {
     private sessionKey?;
     /** Per-host ECDH session keys for non-mega gateways (e.g. eufylife) keyed by host. */
     private readonly sessionKeys;
+    /**
+     * The held credential. `userId` is the login reply's `ap_cloud_user_id` where it has one — the Anker
+     * Passport cloud's id — while `accountUserId` is the eufy account's own `user_id`.
+     *
+     * The `gtoken` header is hashed from `accountUserId`: that is the id the gateway recomputes the header
+     * from, rejecting a disagreement with `"gtoken not equal userid error"`.
+     */
     private auth_?;
     /** captcha_id of an in-flight challenge, held between login() and solveCaptcha(). */
     private pendingCaptchaId?;
@@ -246,7 +253,14 @@ export declare class MegaHttpClient {
      */
     private baseHeaders;
     /**
-     * The account-credential headers every authed call carries — `x-auth-token` + `gtoken` (`md5(userId)`).
+     * The id `gtoken` is hashed from — the account's own `user_id`, which is what the gateway recomputes the
+     * header from. One place so the two header paths cannot drift on which of the session's ids that is.
+     *
+     * Call only where `auth_` is already established; every header path guards it.
+     */
+    private gtokenUserId;
+    /**
+     * The account-credential headers every authed call carries — `x-auth-token` + `gtoken`.
      * One place so the signed path, the key-exchange and the bearer path can't drift on what "authed" means.
      */
     private authTokenHeaders;

package/dist/transport/http/solix-client.d.ts

@@ -121,6 +121,11 @@ export declare class SolixClient {
      * Turn a decrypted `/passport/login` payload into an `ok`/`2fa` result, establishing the session on
      * `ok`. The passport marks a pending 2FA with a non-empty `fa_info.info`, and empties it once the code
      * has been satisfied.
+     *
+     * `gtoken` is hashed from `ap_cloud_user_id` where the reply carries one, `user_id` otherwise. Whether
+     * this gateway recomputes the header from `user_id` specifically — as the mega gateway does, rejecting a
+     * disagreement with `"gtoken not equal userid error"` — is unverified here: no Solix response has been
+     * observed refusing the header, which is consistent with the two ids agreeing on the accounts seen.
      */
     private classifyLogin;
     /** Decrypt a login envelope's `data` (base64 `IV(16)||AES-128-CBC`, keyed by the share key). */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mega-yfue/eufy-sdk",
-  "version": "0.2.0-beta.15",
+  "version": "0.2.0-beta.16",
   "description": "One typed TypeScript client for the Anker eufy v6 cloud — capability-driven devices, realtime events over P2P/MQTT/push, and live media",
   "license": "Apache-2.0",
   "author": "mega-yfue",