Repository navigation
LinkProven v2.4.1
Exact pairing between a test-point session and the reports of its test
points, and the Server's serial number is now opt-in. The control protocol
is unchanged, and the sidecar keeps schema 13 (see below).
Security
- A Windows Server no longer sends its serial number to every Client.
With cable validation on, a Client asks the Server to describe its laptop
for the report. The Windows Server has no login, so any device on the test
network that connected could read the laptop's serial number this way. It
is now sent only when Send this laptop's serial number to the Client is
ticked on the Server page (off by default). Make, model, network card and
link state still reach every Client's report. The setting applies to the
next Client without restarting the listener. The Linux agent and the phone
Server also withhold the serial, except from a Client that proved their
agent token.
Changed
- A session now records each test point's own run id. With "Also save
each segment as its own report" (the default), the session's.jsonlists,
for every test point, the run id its own report carries. The run history,
campaign status and cable history use it to count each test point once.
Before this, the pairing went by campaign, test point and exact start time,
so a session whose test points had no label counted each one twice, and so
did a label corrected in one file only. Saving the last test point again
with Save report now stays paired, even with "Also save each segment"
off. Reports saved before 2.4.1 still pair the old way. - "Save report now" after a session files the last test point under its
own label and cable, not whatever the Run tab's Test point field held. - A re-issued report keeps the run ids, and an anonymised copy drops them, as
it already drops the run's own id. - The sidecar's
schema_versionstays 13. The new field is optional, so
older versions of LinkProven read the new files unchanged. Cloud sync holds
back a schema newer than 13 until the server is updated, so a new number
would have held every new run in the outbox. The cloud doesn't use the run
ids yet, so the portal dashboard still counts a session and its test points
separately.
Fixed
- A damaged session report no longer shifts its test points. If one
entry in a session's list of test points couldn't be read, the history
showed every later test point with the next one's results. Each point is
now read from its own entry.