@synapticon/motion-master-client 6.0.0-alpha.59 → 6.0.0-alpha.61

package/dist/generated/Api.d.ts

@@ -137,6 +137,11 @@ export declare class Api<SecurityDataType = unknown> extends HttpClient<Security
          * @example "local.motion-master.synapticon.com"
          */
         subject: string;
+        /**
+         * The certificate's subjectAltName DNS entries — the hostnames it is valid for, and what a browser actually checks (the CN is legacy and ignored). The bundled certificate covers both the loopback name and the `*.ip.…` wildcard used by off-loopback deployments, so one file serves either. Empty for a certificate with no SAN extension.
+         * @example ["local.motion-master.synapticon.com","*.ip.motion-master.synapticon.com"]
+         */
+        dnsNames?: string[];
         /**
          * Issuer common name (CN).
          * @example "R10"

package/dist/index.d.ts

@@ -4,6 +4,7 @@ export * from './generated/Api.js';
 export * from './constants.js';
 export * from './web-socket-connection.js';
 export * from './client.js';
+export * from './lan.js';
 export * from './hex.js';
 export * from './sdo.js';
 export * from './somanet.js';

package/dist/index.js

@@ -9,7 +9,9 @@ export * from './constants.js';
 export * from './web-socket-connection.js';
 export * from './client.js';
 // Pure, framework-agnostic helpers (no DOM/React): hex formatting, CoE SDO value
-// encode/decode, and SOMANET file-list parsing.
+// encode/decode, SOMANET file-list parsing, and the LAN hostname mapping that lets a browser
+// reach a server on another machine under a name the bundled certificate covers.
+export * from './lan.js';
 export * from './hex.js';
 export * from './sdo.js';
 export * from './somanet.js';

package/dist/lan.d.ts

@@ -0,0 +1,4 @@
+export declare const LAN_DOMAIN = "ip.motion-master.synapticon.com";
+export declare function isIpv4(value: string): boolean;
+export declare function lanHostname(host: string): string;
+export declare function lanAddress(host: string): string | null;

package/dist/lan.js

@@ -0,0 +1,59 @@
+// Reaching a Motion Master that runs on another machine (an appliance on the workshop LAN, say)
+// over TLS, from a page served at https://motion-master.synapticon.com.
+//
+// The obvious address — https://192.168.1.50:61447 — cannot work: no public CA will issue a
+// certificate for a private IP, and a cross-origin fetch() offers no click-through for a
+// self-signed one. The way out is a real, publicly-trusted name pointing at the private address.
+// Names under `ip.motion-master.synapticon.com` write the address into their leftmost label, and
+// the certificate every server ships carries the `*.ip.motion-master.synapticon.com` wildcard, so
+// any such name validates with nothing to install.
+//
+// These names are resolved on the client machine by a hosts-file entry, not by public DNS — which
+// is sufficient, because TLS checks a certificate against the name and never against how the name
+// was resolved.
+//
+// The mapping is *offered* to the user, never applied behind their back: connecting straight to the
+// IP address is a legitimate second path. It works once that origin has been opened in a tab and its
+// certificate warning accepted, and it is the only path when the Console is being viewed from a
+// phone or tablet — those cannot edit a hosts file, and it is the *browser's* machine that needs
+// the entry, not the one running Motion Master. So these helpers convert on request; the caller
+// decides.
+// The subdomain whose leftmost label encodes an IPv4 address.
+export const LAN_DOMAIN = 'ip.motion-master.synapticon.com';
+// True when `value` is a dotted-quad IPv4 literal (each octet 0-255). Hostnames, IPv6 literals,
+// and anything with a port or scheme attached are not.
+export function isIpv4(value) {
+    const octets = value.trim().split('.');
+    if (octets.length !== 4) {
+        return false;
+    }
+    return octets.every((octet) => /^\d{1,3}$/.test(octet) && Number(octet) <= 255);
+}
+// Map a host to the name the bundled certificate covers: an IPv4 literal becomes its dashed form
+// under LAN_DOMAIN (192.168.1.50 -> 192-168-1-50.ip.motion-master.synapticon.com); anything else
+// is already a hostname and is returned trimmed but otherwise untouched — so a user who types
+// `local.motion-master.synapticon.com`, or the dashed name itself, is left alone.
+//
+// Loopback is not special-cased: 127.0.0.1 maps to 127-0-0-1.ip.… which the same certificate
+// covers. For a same-machine server the shorter `local.motion-master.synapticon.com` is still the
+// better answer, since it is a public A record and so needs no hosts entry at all.
+export function lanHostname(host) {
+    const trimmed = host.trim();
+    if (!isIpv4(trimmed)) {
+        return trimmed;
+    }
+    return `${trimmed.split('.').join('-')}.${LAN_DOMAIN}`;
+}
+// The inverse of lanHostname: recovers the address a LAN hostname encodes, or null if the host is
+// not one of ours. Used to build the hosts-file line the user needs, since these names resolve
+// nowhere until they add it.
+export function lanAddress(host) {
+    const trimmed = host.trim().toLowerCase();
+    const suffix = `.${LAN_DOMAIN}`;
+    if (!trimmed.endsWith(suffix)) {
+        return null;
+    }
+    const label = trimmed.slice(0, -suffix.length);
+    const address = label.split('-').join('.');
+    return isIpv4(address) ? address : null;
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@synapticon/motion-master-client",
-  "version": "6.0.0-alpha.59",
+  "version": "6.0.0-alpha.61",
   "description": "Isomorphic TypeScript client for Motion Master: the generated HTTP API client, the WebSocket connection, and helpers.",
   "license": "MIT",
   "repository": {