Skip to content

Releases

LinkProven v2.5.1

Choose a tag to compare

@mhmd2520 mhmd2520 released this 21 Nov 21:55

A Server no longer waits for ever on a Client that connects and then goes
quiet. Reports, sidecars (schema 13) and the control channel's messages are
unchanged; this release also lists two cloud fixes that went live today.

Security

  • A quiet Client no longer holds the Server. Anything that could reach the
    Server could connect, say hello and then send nothing, and the Server (on
    Windows, also its test network adapter) stayed taken until someone stopped
    it, so the real Client was told it was busy. Now the Server lets a Client
    go after 3 minutes without a step of the sweep, says so in its window, and
    is free for the next one at once. A real Client is never that quiet: each
    test point is its own connection, and moving the cable between points
    happens with no connection open. The Linux agent does the same. Only real
    steps count: a heartbeat, a repeated sweep start or a malformed case does
    not keep a Client connected. This stops a Client that goes quiet; what
    keeps other devices off the Server is the agent token with --allow-from.
  • The Server only runs case lengths the Config page allows (1 s to 1 h).
    The Client names each case's length, and a case keeps the Server until it
    ends, so a made-up length of years held it just the same; a big enough one
    could also leave a stray iperf3 server running. Such a case is now refused.
  • A Client the Server lets go is told why, when the message reaches it.
    If it ever happens mid-sweep, the Server window reads it as a sweep cut
    short (with the disconnect sound) rather than as housekeeping, and a
    Client that receives the reason stops at once and shows it.
  • Cloud: one team member can no longer hide another's test point. In a
    team workspace a session's test point is counted once when its own report
    is also uploaded. Before, any sweep with the same id counted as that
    report, so a member could upload a fake sweep that hid a colleague's FAIL
    from the campaign status, the Dashboard and the campaign trends, and kept
    the real report from ever uploading. Now the two are paired only when the
    same account uploaded both, for the same campaign and test point, and the
    cloud refuses a sweep that reuses a test point id from someone else's
    session. Cloud-only: the desktop app is unchanged.
  • Cloud: only the uploader or a workspace owner can re-save a run. Saving
    a run again (corrected details, another report format) adds a new version
    in the cloud. Before, any team member could re-upload a colleague's run
    with the technician, customer or serial number edited, and that version
    became the one everyone saw (the results themselves could never change).
    Now the cloud accepts a re-save only from the member who uploaded the run
    or from a workspace owner. Cloud-only: the desktop app is unchanged.

LinkProven v2.5.0

Choose a tag to compare

@mhmd2520 mhmd2520 released this 21 Nov 19:22

Both ends of a Linux agent connection now prove the agent token (ADR 0003).
Only set-ups that use the agent token are affected: without a token the
control channel is exactly as before, byte for byte. Reports, sidecars
(schema 13) and the cloud are unchanged.

Security

  • The Linux agent proves the token to this laptop. Before, only the
    laptop proved it, so anything answering on the server's address could run
    the whole sweep and send back made-up Server-side results (loss, NIC
    counters, the server's own details) that went into the report. Now the
    agent proves the token first, and LinkProven stops with its own message
    before a case runs if the proof is wrong or missing. The proof also covers
    the laptop's opening message, so nothing on the way can quietly switch
    off the Server-side evidence a sweep asks for.
  • Every message after the token check is signed. Each control message
    carries a code made from the token and this connection only. A message
    that was changed, replayed or reordered on the way ends the sweep at once,
    and both ends say it was tampered with (never "connection lost"), so no
    one on the test network can change a result in transit. Results are not
    encrypted.
  • A recorded sign-in to the agent can't be replayed. The agent used to
    remember used codes only until it restarted, and a fake server could
    collect a fresh code from a laptop and replay it straight away. Each
    connection now has to answer a fresh challenge from the agent, and the
    agent keeps no list to lose.
  • The web portal sends a Content-Security-Policy. It names everything
    the portal may load: its own files, Flutter's renderer and fonts from
    Google's CDN, and the LinkProven cloud. A script injected from anywhere
    else would not run. It ran in report-only mode on the live portal first;
    a signed-in session logged no violation, so it is now enforced.

Changed

  • Update the Linux agent together with LinkProven. Once a token is in
    use, the agent and every laptop that uses it must all be on 2.5.0 or
    later: an older laptop and a 2.5.0 agent refuse each other. There is no
    fallback to the old check, because a fallback would let the old attacks
    back in. After updating, run the Linux server set-up (Setup →
    Server is Linux…) again to update the agent. A laptop with a token saved
    also refuses a Server that can't prove it, including a Windows LinkProven
    Server at the same address: clear the token in that dialog to use one. Both
    cases say so in plain words when you connect.
  • The phone app's Server code follows the same rules, ready for when it
    offers a token.

Fixed

  • The Windows Server never listens on every network. A Server address
    of 0.0.0.0 (any network) is refused with a message instead of opening
    the control port to the whole LAN, as the Linux agent already did.
  • Error banners and the Multi-Client PDF never treat text as markup. An
    iperf3 error message containing < could stop a Multi-Client PDF from
    saving; the app-wide warning banner now always shows plain text.
  • A malformed number from the Server no longer loses the sweep. A
    number too long or too large to read in a Server's reply (for example
    1e999 packets) used to stop the sweep and throw away every finished
    case. Now that reply is treated as a bad message and the cases already
    measured are kept.

LinkProven v2.4.2

Choose a tag to compare

@mhmd2520 mhmd2520 released this 21 Nov 13:13

A build-security patch, plus the cloud's half of 2.4.1's session pairing.
Nothing changes in how the app runs or what its reports say. The sidecar
keeps schema 13.

Security

  • Every package inside the app is now pinned by its SHA-256 at build
    time.
    The release build used to take PyInstaller and every library it
    bundles (Qt, matplotlib, reportlab, ...) from a development environment
    installed without fixed versions. It now builds from its own environment,
    installed only from a list of exact versions and file hashes, from
    ready-made packages (nothing is compiled), and checked for completeness.
    A package that changed on the download server cannot reach a release. The
    pinned list is also checked against known vulnerabilities before every
    release (none found).

Changed

  • The cloud counts a session's test point once. The portal's dashboard,
    campaign status and campaign trends now pair each test point of a session
    with that point's own report (the run id 2.4.1 records), so a three-point
    session saved with "Also save each segment as its own report" counts as
    three runs, not four. This is live on the cloud for every app since 2.4.1;
    sessions saved by older versions are counted as before. The app's own
    index of a run now carries each test point's run id the same way.

LinkProven v2.4.1

Choose a tag to compare

@mhmd2520 mhmd2520 released this 21 Nov 10:18

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 .json lists,
    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_version stays 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.

LinkProven v2.3.9

Choose a tag to compare

@mhmd2520 mhmd2520 released this 20 Nov 15:02

A whole-application security and correctness review (not just the latest
changes), plus a dependency audit. The sidecar schema (13) and the control
protocol are unchanged.

Security

  • The Server window no longer renders text from an unauthenticated
    Client.
    A sweep id containing markup was shown as rich text in the
    Server's title; it is now plain text, and a sweep id keeps only letters,
    digits and ._:-. The phone Server filters it the same way.
  • LinkProven's PowerShell calls load only Windows' own modules. A module
    placed in the user's Documents folder could otherwise run with
    administrator rights the next time LinkProven read the network adapter.
  • Qt plugin-path settings from the user's environment are ignored in the
    installed app, so a planted plugin can't load into it.
  • Updates download inside the install folder (_update\download), which
    only administrators can change, instead of the user's AppData folder.
  • Test-only folder settings for photos and campaigns are ignored in the
    installed app.
  • The team invite email uses nodemailer 10.6.0 (was 7.0.13, which has
    published advisories), and every Edge Function dependency is pinned to an
    exact version.
  • Only workspace owners can delete a campaign or remove a laptop in the
    cloud workspace. Either delete strips that link from every synced run, so
    it now needs the same role as deleting a run.
  • The portal always uses HTTPS (HSTS), and its share dialog states that
    the shared PDF and Word reports include IP addresses and computer names.

Fixed

  • A case is no longer PASS when one of its reference limits could not be
    checked
    (for example latency with ICMP blocked). It reads "not checked"
    until every limit that applies could be judged. Jitter and UDP loss limits no
    longer apply to a TCP run.
  • NIC power saving that is on no longer reads "Disabled" on non-English
    Windows.
    The readiness check uses the driver's own setting, not the
    translated text, and says it can't tell rather than guessing.
  • Importing a config file that is not UTF-8 shows the import error instead
    of crashing, and a UTF-8 file saved with a byte-order mark (PowerShell,
    Notepad) imports.
  • A finished update's download is removed at the next start. Versions
    2.3.8 and older downloaded to %APPDATA%\LinkProven\update; LinkProven no
    longer touches that folder, and you can delete it.
  • Closing or switching roles right after a sweep stopped waits (up to 8
    seconds) for the sweep to finish shutting down.
  • The Detail and per-segment sheets of the Excel report format numbers as the
    Summary sheet does
    , so one value no longer reads 10 on one sheet and 10.00
    on another.
  • A save that wrote no report document says what it did write (data,
    photos or charts) and in which folder.
  • A report with a long name close to Windows' 260-character path limit
    saves
    (the temporary file now has a fixed 15-character name instead of the
    report's name plus 13 characters).
  • Hint text follows the Light / Dark / Low light theme, and Config's Apply
    button uses the app's button style.

Internal

  • New tools/audit_dependencies.py checks every shipped dependency set
    against the OSV vulnerability database (through Google's osv-scanner when
    it is installed). It separates what the app ships from developer tools, and
    a failed or partial read counts as "not checked", never as clean. /finish
    and /publish now run it, and /finish adds a periodic whole-repository
    security review.
  • Reference verdicts record the judging rules they were made by, so a run
    saved before 2.3.9 keeps its verdict in Analysis and when its report is
    re-issued. Each report type now states which metrics apply to it.
  • Help and website screenshots are re-shot. The header's network adapter
    and the Multi-Client core count are now fixed demo values rather than
    this PC's, and two captures of the same code match byte for byte again.

LinkProven v2.3.8

Choose a tag to compare

@mhmd2520 mhmd2520 released this 19 Nov 15:37

The sidecar schema (13) is unchanged, and so is the control protocol: the
Client's FINISH may now carry an optional stopped: true. It is sent only to
a 2.3.8 or newer Server; an older one sees the hang-up, as before.

Fixed

  • A Stop pressed on the Client no longer looks like a lost connection on
    the Server.
    The Client now tells the Server it was stopped before it
    hangs up, from the end of the handshake on, between cases or in the middle
    of one, and so does closing the Client mid-run. The Server says "Stopped
    by the Client", drops the unfinished case, ends it in the live view, and
    raises no orange connection banner and no sound. A real drop still raises
    the banner (a pulled cable also plays the disconnect sound). The phone
    Server reports the same stopped finish.
  • The stop is not lost on a Windows Server. The Client keeps reading
    until the Server has hung up (2 seconds at most) instead of closing at
    once: closing under a message still coming in resets the connection, and
    Windows then throws away the stop it had not read yet.

Internal

  • The control channel writes one message at a time, so the Client's Stop
    (sent from the window) can never split a message the sweep is writing.
  • A Server starts each connection's counts from zero.

LinkProven v2.3.7

Choose a tag to compare

@mhmd2520 mhmd2520 released this 19 Nov 13:35

The sidecar schema (13) and the control protocol are unchanged from 2.3.6: a
busy Server still answers HELLO with the ERROR code busy, now with a known
reason in its message. The items deferred at the 2.3.6 close-out:

Changed

  • One owner of the network adapter at a time. A sweep, a Multi-Client
    run, a screening run, a Setup fix, Reset and an update install now each
    claim the test NIC, and only the one holding it can give it back. Before,
    one tab finishing could clear another's hold: a Client connecting to a
    Server laptop that was running a Multi-Client test released that test's
    lock when it hung up.
  • A busy Server says why. A Client turned away now hears the reason: a
    Setup fix is changing the Server laptop's network adapter, it is installing
    an update, or it is running its own test. Only LinkProven's own reasons are
    repeated, never text from the other end.
  • Installing an update on a Server no longer waits for a later click. The
    install takes the network adapter first, so a Client connecting while the
    update prepares is refused with that reason. If a test is already running,
    the downloaded update is kept and Install says what it is waiting for.
  • The Server shows "Client connected" only once the Client has passed the
    handshake.
    A silent connection (a port probe) or a refused Client no
    longer shows as connected and then disconnected. The phone Server does the
    same.
  • Filename patterns: only {date}, {time}, {tp}, {campaign},
    {train} and {cable} are special.
    A :format or !conversion inside
    one is ignored, and {{ / }} are a single { / } in every pattern (a
    pattern with an unknown token used to keep them doubled).

Fixed

  • Cloud uploads read the waiting list fresh. Only the Cloud panel's
    summary line is cached now, so an upload or backfill never works from a
    cached copy of the list (one could be up to 30 s old on a coarse-clock
    disk).
  • Fix all keeps the network adapter until its last fix is done. It let go
    between fixes, so a Client could connect to the Server in between and the
    remaining fixes failed, leaving the laptop half-fixed.
  • A Setup fix or Reset waits for the laptop readiness fixes. Either could
    start while those were restarting the network adapter.
  • Restarting the Server listener no longer upsets the new session. A slow
    old listener's late "disconnected" could end the new session's keep-awake
    hold.

Internal

  • One modal busy loop behind both background helpers, one loop for every
    report document save, and the outbox read says when it skipped a busy note.

LinkProven v2.3.6

Choose a tag to compare

@mhmd2520 mhmd2520 released this 19 Nov 09:33

The sidecar schema and the control protocol are unchanged from 2.3.5. The
items deferred at the 2.3.5 close-out:

Changed

  • Campaign files keep the names they always had. 2.3.5 saved a campaign
    called "A - B" as A-B.json; 2.3.6 goes back to A---B.json, the name every
    version before 2.3.5 used. Any file 2.3.5 wrote is moved back when
    LinkProven starts (unless a file already has that name).

Fixed

  • Renaming a campaign to a name that only differs in punctuation or case no
    longer deletes it.
    "Train #1" renamed to "Train 1" (or "unit 7" to
    "Unit 7") saves to the same file, which the rename then deleted as the old
    one.
  • Updating the Server no longer closes it under a sweep. Preparing an
    update takes a few seconds, and a Client could start a sweep in that time;
    the app then closed to install. The install now waits: press Install when
    the sweep has finished, and the prepared update starts at once.
  • The Server refuses a sweep while a Setup fix is running on it. A Client
    that connects while the Server is changing its network adapter is told
    "The Server is busy" and can start again when the fix has finished. It is
    shown as a refusal, not as a connection error, and a soak stops with that
    reason. The other way round, the Server counts as busy from the moment a
    Client connects, so a Setup fix, Reset or update can't start while the two
    laptops are still handshaking.
  • Analysis opens without a pause on a full Reports folder. Eight or more
    new reports are read in the background; a report saved during the session
    still appears at once. The page no longer says "No reports yet" while they
    load, and opening or closing the demo data doesn't wait for them.
  • The Cloud panel no longer re-reads every queued upload each time it
    repaints
    , which it did after every upload.
  • The Analysis Cables list catches up when you come back to the tab. A
    cable saved while the page was hidden only appeared after the next save.
  • Editing a test point's label on the Plan page saves the campaign once,
    not twice.
  • A report name with an empty field is built from the pattern itself. The
    result is unchanged ("Test2-{train}-{tp}" with no train gives "Test2-TP3");
    a value with its own dashes or underscores is never trimmed.

LinkProven v2.3.5

Choose a tag to compare

@mhmd2520 mhmd2520 released this 18 Nov 19:54

The sidecar schema and the control protocol are unchanged from 2.3.4.

Fixed

  • Numbers no longer wrap in report tables. The cover's Table-2 printed a
    loss of 0.000 as "0.00" over "0" in the PDF. The cover's Table-2 and the
    cable-validation tables (PDF and Word), and the PDF's other auto-sized
    tables, now give each column at least the width of its longest word.
  • "Use last run" says where an earlier run comes from. After a restart there
    is no last run, so the button is now greyed out until a sweep finishes, and it
    points at Load from report… instead. Setting a baseline is confirmed on
    screen. If the last sweep was recorded as one of the campaign's test points,
    you are asked whether it really was the bench run.
  • An empty field no longer leaves a double separator in a report name. With
    no train set, Test2-{train}-{tp} now gives Test2-TP3, not Test2--TP3.
  • A campaign name with " - " gets a clean file name. "A - B" is saved as
    A-B.json, not A---B.json. Campaigns saved under the old name are still
    found, and two campaigns never share a file.
  • The Plan page no longer overwrites changes made to the campaign file outside
    LinkProven.
    It reloads the file when you open the page. If you edit on the
    page after the file has changed, it asks whether to reload the file or
    overwrite it. A file that can't be read leaves the campaign active.
  • Save Options shows the file name a save will use. When the campaign's
    report template names a pattern, the page says so, and says which pattern wins.

From a whole-app review:

  • Sweeps and sessions
    • The Server laptop now stays awake for a whole sweep, so it can't fall asleep
      mid-session and read on the Client as a disconnect.
    • The verdict shown between test points now matches the saved session report.
      Before, a link drop could read PASS on screen and FAIL in the report.
    • A case whose iperf3 client never connects no longer waits an extra 10 s, on
      the Server or in Loopback.
    • A Client that vanishes without closing the link no longer holds the Server
      forever.
    • The Server's "Cases received" count no longer counts a retried case twice.
    • A low-battery warning is listed once per session, not once per test point.
  • Saved reports and history
    • Each test point of a session saved with "Save each test point" now counts as
      one attempt, not two. Before, the Plan page showed "attempt 2" and a retest's
      report named attempts that never happened.
    • A run copied into the Reports folder, or a record edited in place, now
      appears without restarting the app.
    • A save into a newly chosen destination is no longer dropped from the list.
    • Runs that leave the Reports folder also leave the Analysis list.
    • One unreadable record no longer empties the Analysis list.
    • The Analysis export no longer fails at its default settings. Before, it
      tried to write a CSV it can't make.
    • The export now includes only the runs the filter shows, and says when
      "Only runs with failed cases" is on.
    • If one file of an export or a soak summary fails, the rest are still written.
    • Issuing a certificate later no longer makes untouched reports verify as
      altered.
    • A test point retried within a session keeps both verdicts on the cover and
      in its QR code.
    • The Excel "Run info" sheet now states the real number of cases, not "all 20".
  • Numbers
    • Loss read from iperf3's text output is now worked out from the packet counts.
      Before, it used iperf3's rounded percentage, so a 1.04 % loss could read
      MARGINAL against a 1 % limit.
    • A TCP Multi-Client run no longer shows jitter and loss as 0.000 / 0.00. It
      did not measure them.
    • A case that received nothing is no longer drawn as a clean 0 % cell.
    • NIC error counters that were not recorded now read "not recorded", not
      0 errors in green.
    • Analysis Stats shows sub-0.01 % loss as the reports do. Old records'
      missing values no longer count as "better".
    • The threshold line is hidden when the runs offer different rates at the
      same case number.
    • The Multi-Client load figures for TCP now add up, and UDP payloads above
      1472 B count their IP fragments.
  • Setup, Plan and Multi-Client
    • Setup fixes, Fix all and Reset now run without freezing the window, and
      refuse to run while a test is running.
    • A Reset whose network restore fails keeps the markers that let the next
      launch retry the restore.
    • A cable pulled during a check, or while the Setup tab was hidden, now
      triggers a re-check.
    • One check that crashes now shows a FAIL row instead of leaving the tab stuck
      on "Running checks…".
    • Firewall rules are now detected, and removed by Reset, on non-English Windows.
    • The Ping summary now reads non-English Windows output.
    • The close-time DHCP revert now undoes an address LinkProven set on an
      override subnet or on a second Ethernet adapter.
    • A blank or repeated test-point label on the Plan page is refused, instead of
      the row being dropped from the saved plan.
    • Check connectivity and a Multi-Client run no longer run at the same time.
    • A Multi-Client run against the test subnet is blocked while Wi-Fi is on that
      subnet, as a sweep is.
    • The Distribution and extra ping destinations are now remembered.
    • A screening that never connected now says "Could not run" instead of "Worth
      a full sweep".
  • Speed
    • Report charts are drawn once per save instead of three times.
    • The first report of a session no longer freezes while the tool versions are
      read.
    • Anonymised copies, certificates, update installs and queuing past reports
      for upload now run without freezing the window.
    • Closing the app no longer re-reads every record.
    • The Analysis and Save Options pages read the shared Reports index instead of
      walking the folder themselves.
  • Updates, cloud and safety
    • An update that finishes downloading during a sweep now waits for you to
      press "Install now", instead of closing the app mid-run.
    • The update check can no longer get stuck on "Checking for updates…".
    • Sign-in no longer refreshes on every call on a laptop whose clock is wrong.
    • Google and Apple sign-in buttons are asked for again if the first try was
      offline.
    • A stray keystroke in the agent token field no longer replaces the saved
      token. A typed change is confirmed first.
    • The Config page opens folders through the pinned Explorer.

From the /finish review:

  • The NIC counters table no longer reads green when a case recorded no
    counters at all. When some cases did not record an error counter but others
    counted errors, it shows "≥ N" and fails, as criterion 4 does.
  • A user Stop on the Server no longer reads as a Client disconnect, with no
    banner and no disconnect sound.
  • The Linux agent now notices a vanished Client within about 40 s, as the
    Windows Server does, instead of after the 2-hour system default.
  • A campaign named with " - " keeps its own file when that file is renamed or
    broken outside LinkProven. Renaming a campaign in its file to another
    campaign's name no longer overwrites that campaign: the name is kept.
  • A fix or Reset started on the Server is refused if a Client starts a sweep
    while its confirmation is open.
  • Closing the app while a fix, a save or an update is being prepared no longer
    risks a crash: the work finishes first.

LinkProven v2.3.4

Choose a tag to compare

@mhmd2520 mhmd2520 released this 08 Nov 10:35

Reports, records, the sidecar schema and the control protocol are unchanged from
2.3.3.

Fixed

  • A run's .json record and a soak summary are written more safely. The app
    writes each one through the file it just created, and never opens that file
    again by name, so nothing can swap it in between. LinkProven runs as
    administrator, which makes this matter.
  • A session certificate that can't be written is named cleanly. When the run
    has no test point, the message no longer starts with a stray space.
  • Leftovers are logged. If a temporary file can't be deleted after a failed
    report write, the log names it so it can be removed by hand. A failed
    anonymised copy now records its full error in the log too.