research(ubiquiti): the Early Access storefront is live and login-gated - the one surface that could hide a Pro Dream Wall (#130) #2188
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2188
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-1752"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #130 - records evidence, does not close it. No spec change.
The one Ubiquiti surface that is gated rather than empty. Ten passes concluded "absent"; this pass found the channel that could hide the SKU, and it cannot be read anonymously.
ea.store.ui.com(Early Access storefront) fails TLS verification, and that is a certificate gap, not a dead host: it presentsCN=*.ui.com, SANs*.ui.com, unifi.ui.com, beta.unifi.ui.com- a single-label wildcard that cannot match a two-label subdomain (store.ui.comcorrectly presents*.store.ui.com). It resolves to CloudFront.Behind
-kthe app is deployed and globally gated:/account.ui.com/login?redirect=...%2F/us/en...%2Fus%2Fen/us/en/products/udw-pro...%2Fus%2Fen%2Fproducts%2Fudw-pro/nonexistent-xyz(control)...%2Fnonexistent-xyz/_next/static/...%2F_next%2Fstatic%2F/favicon.icoimage/vnd.microsoft.icon, md59fe014bbdbd4d12c3312fcbc41b0c436The junk-path control is what makes it evidence: a missing page would 404 with content, a retired host would not serve a built favicon. Every path redirects to the login with the path preserved, and
account.ui.com/loginis 200, 1,634 B,<title>Ubiquiti Account. So the bundle that would name the EAstoreIdis behind the same wall.Why it matters for this SKU: the UDW's own commerce row carries
historicalSlugs ["dream-wall","dream-wall-ea","udw","unifi-dream-wall"]- the Wall began in the EA storefront under an EA slug. A console announced but not yet public is what that channel carries, so its silence is not citable, unlike every other surface already recorded.Backend cannot reach it either: store ids
ea,ea-us,us-eaeach answer exactly one maskedINTERNAL_SERVER_ERRORfor theudwcontrol as well asudw-pro- under the recorded oracle, one error on the control means the id is rejected, not that the product is missing. Reproduce:node scripts/ubiquiti-storefront-catalogue.js --slug udw,udw-pro --store ea --json.Reconfirmed, negative unchanged:
uk.store.ui.com/uk/en/category/all-cloud-gateways- 200, 483,934 B, 16 embeddedStorefrontProductrecords,udw-pro/UDW-PROzero occurrences; UDW recorddisplaySku "UDW (420W)".4gon.co.uk/...p-10111.html, is 403 (Cloudflare interstitial, 5,626 B) andarchive.org/wayback/availablereturns{"archived_snapshots": {}}- the page the port list was "inferred from" was never archived, so the premise cannot be re-derived.Files:
research/ubiquiti-udw-pro-absent-from-vendor-catalogue.md(new section),research/open-device-requests.json(entry 130missing+ 5 sources),docs/DEVICE_REGISTRY.md(regenerated).Gates: syntax 461 OK; audit-port-types clean; audit-devices no hard defects; audit-poe-budget 407 PSEs / 0 budget-without-PSE; hardware invariants 26/0;
regen-registry-doc.js --checkcurrent (2,355 models / 258 vendors); doc-citations 358, no judged citation out of range; control-bytes clean.Unblock, narrowed: a credentialed read of
ea.store.ui.com(a Ubiquiti account - impossible for this anonymous worker), or the requester confirming the intended SKU is the catalogued UDW or the UDM-Pro.The Dream Wall Pro is absent from every anonymous Ubiquiti surface, but one channel was never read: `ea.store.ui.com`, which is where an announced but unpublished console would sit - and the UDW's own commerce row already carries `dream-wall-ea` as a historical slug, so the Wall itself started there. Measured 2026-11-19 17:5x UTC. The host fails TLS verification, which is a certificate gap and not a dead host: it presents `CN=*.ui.com` with SANs `*.ui.com, unifi.ui.com, beta.unifi.ui.com`, a single-label wildcard that cannot cover the two-label name (`store.ui.com` correctly presents `*.store.ui.com`). Behind `-k` the application is deployed and globally gated: `/`, `/us/en`, `/us/en/products/udw-pro`, `/_next/static/` and a junk control path all answer 302 to `account.ui.com/login` with the requested path preserved, while `/favicon.ico` is 200, 5,430 B (`image/vnd.microsoft.icon`). So its silence is not citable, unlike every other surface in this file. The commerce backend cannot reach it either: store ids `ea`, `ea-us` and `us-ea` each answer one masked validation error for the `udw` control, i.e. the id is rejected rather than the product missing. Reconfirmed in the same pass, no change to the negative: the UK gateway grid (200, 483,934 B) carries 16 product records and zero `udw-pro`, and the 4gon listing the request's port list was "inferred from" is Cloudflare-403 and has never been archived (`archived_snapshots: {}`). No spec change: devices/ubiquiti/udw.json is untouched. Records evidence for #130; does not close it.