Skip to content

Releases

v1.3.1: dropped connections are retried

Choose a tag to compare

@pwfauth pwfauth released this 12 Oct 09:58

When a request gets no reply at all, usually a connection closed on the way (Windows error 10054 or WinHTTP error 12030, "An existing connection was forcibly closed by the remote host"), the client now sends the same request once more on a new connection, 300 ms later. Before, the call failed with "Cannot reach the license server".

Only that case is retried: a reply (even an error reply), a reply that drops while it is read, and a timeout are never sent twice. Same signing key, same API.

Download the source below, or pull main. See the README for the details.

v1.3.0 — Customer accounts

Choose a tag to compare

@pwfauth pwfauth released this 12 Oct 00:39

Customer accounts for the native C++ client.

New

PwfClient can now work with customer accounts (a username and a password instead of a licence key), like the .NET package:

  • RegisterAccount(username, password, email): create an account.
  • RegisterAccountWithKey(username, password, licenseKey, email): create an account that takes a key's time and device limit (the key is used up).
  • AccountLogin(username, password): sign the account in on this PC. Call StartHeartbeat() afterwards, exactly as after Login: the kill switch works the same way.
  • ChangeAccountPassword(username, currentPassword, newPassword): change the password (every session of the account is signed out).
  • RedeemKey(username, password, licenseKey) and RedeemKey(licenseKey): add a key's time to an account, with its password or through the signed-in session.

Every reply is still checked against the server's signature. The README has a short example.

Upgrade

Replace PwfClient.h and PwfClient.cpp in your project and rebuild. ServerPublicKey.h and ProductionPolicy.h are unchanged from 1.2.0. Turn on Customer accounts for your app in the panel (Applications → edit the app → Rules).

This is a source release: build your own executable with your app secret. The package contains the public verification key only.

Validation

Release x64 build with no warnings at /W4. Every new function was run against the server: account creation (and a taken username refused), creation with a key (the key then refuses a plain key sign-in), account sign-in, heartbeat, adding a key through the session, sign-out, a wrong password refused, a password change and a sign-in with the new password.

v1.1.1 — Client security update

Choose a tag to compare

@pwfauth pwfauth released this 09 Oct 18:31

Security update for the native C++ client.

Security changes

  • Require an independent server signature bound to each request before accepting a response.
  • Reject forged, modified, unsigned, and replayed replies.
  • Lock the client to https://pwfauth.com with normal TLS certificate validation and no redirects.
  • Remove PWFAUTH_BASE_URL and PWFAUTH_SECRET runtime overrides in both Debug and Release.

Upgrade

Download the source, set APP_SECRET in main.cpp for your application, rebuild Release x64, and redistribute your executable. Existing executables do not update automatically. Include ProductionPolicy.h and ServerPublicKey.h when embedding PwfClient in your own application.

This is a source release: an application-specific executable must be built with your own app secret. The package contains the public verification key only, never the server private signing key.

Validation

Release x64 build, PHP/Windows CNG signature interoperability, tamper/replay rejection, and live production HTTPS tests for valid/invalid synthetic licenses, heartbeat, and logout passed. The original client reproduced the reported emulator bypass; the updated client ignored the emulator override and sent no requests to it.

This addresses the reported server-emulation path; it does not claim immunity to executable patching on an attacker-controlled computer.