Skip to content

v1.5.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 14 Oct 21:51
· 11 commits to main since this release
v1.5.0
This tag was signed with the committer’s verified signature.
blak0p Alejandro
SSH Key Fingerprint: PavXwGZGV5WLmyQxRsrnIKTBDHwu+NdSxr7wQUq1mtI
Verified
Learn about vigilant mode.
5e3776c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Attack Shark Linux v1.5.0: Keyboard and Timed Macros

What’s New

v1.5.0 expands the X6 macro workflow with focused keyboard/mouse recording, local storage of timed takes, guarded upload of supported sequences, and assignment controls. These changes have source-CI and release-candidate pipeline evidence, but do not establish universal compatibility or exhaustive physical-device behavior. Keep a known-good installation available, and do not run the application as root.

Changes Since v1.4.0

Record and manage local keyboard takes

  • Record keyboard and mouse inputs while the capture area is focused. Delay policies preserve timing locally, and the library can retain or import/export keyboard identities beyond those currently eligible for assignment. Recording and saving do not themselves send reports to the mouse. (PR #159, #160; issue #158)
  • Review grouped key down/up events, press counts, and delay slots without rewriting the saved sequence. Local retention does not mean an identity is supported for upload. (PR #162)

Choose playback modes and apply eligible takes explicitly

  • Assignments offer fixed-repeat, continuous-toggle, and while-held modes. Choosing and confirming an assignment stages it locally; Apply is the explicit device-write step. (PR #155, #156; issue #154)
  • Upload validation checks supported keys and events, balance, delay and capacity bounds, destination, and assignment state. Unsupported takes are rejected rather than silently truncated or rewritten. A transport acknowledgement confirms a host-side transaction, not physical playback. (PR #159, #161; issue #158)

Device settings and packaging

  • Corrected X6 key-response/debounce encoding to use the selected milliseconds directly, including documented odd-millisecond values. (PR #148; issue #147)
  • Integrated captured factory-reset settings and reset-state handling. The linked report documents a user-confirmed physical reset, not complete memory erase or power-cycle persistence. (PR #150; issue #149)
  • Aligned the Wails beta.28 build and packaging chain and updated frontend dependencies. (PR #146; PRs #141–#144)

Limitations and Follow-up

Physical keyboard/macro playback, timing, firmware capacity, and device persistence have not been exhaustively verified. In particular, continuous stop-on-second-press and release-to-stop behavior are not established on hardware. Official-key exceptions, browser/OS-reserved inputs, and an explicitly inferential key alias are documented; local retention does not imply upload support.

A separate input-stack diagnostic observed rapid clicks reduced between evdev and libinput. It does not establish a Firefox-only defect or justify a global input-filter change or duplicate-upload workaround; that experiment is not included. See the input-stack notes.

The basic macro library was delivered in v1.4.0 and is not new in this release. Broader UI/text redesign is outside this release’s scope. No open linked follow-up issue was identified for the included macro work; the hardware and input-stack limitations above remain unverified, not claimed as fixed.

Installation and Distribution

Find the release and its attached assets on the GitHub Releases page. Verify the checksums provided with the release before installing. Do not run the application as root.

Community Testing

Useful areas to report include focused recording and focus-loss behavior, delay policies, local save/import/export, rejection of unsupported or oversized takes, assignment staging/cancellation and explicit Apply, and playback modes or persistence where physically tested.

Include your OS/distribution, application version, device and connection, exact steps, and observed results. Distinguish software/transport results from physical playback.

Validation

  • Source: 5e3776cbceb432291004fdaf1226e7ec771facac; 36 commits after v1.4.0.
  • Source Tests and Source CodeQL succeeded for this source SHA.
  • The published v1.5.0-rc.1 pipeline 38639037573 succeeded across its six jobs. These RC results do not verify a future stable-tag rebuild or publication.
  • The RC manifest identifies version 1.5.0-rc.1; its artifact URL and SHA match the downloaded artifact. OpenSSL reported “Signature Verified Successfully” against the installer key.
  • The RC executable was extracted successfully using the AppImage runtime’s reported offset (944632). go version -m could not read its build metadata, so the embedded executable version remains unverified. This does not establish artifact corruption; the maintainer explicitly accepted this verification limitation for stable publication.
  • Physical macro playback and hardware timing/persistence are not established by these checks. Stable-release artifact checks remain pending.

Distribution

The release workflow is configured to publish five assets. That configuration and the successful RC pipeline do not establish completion of a stable release. No Homebrew, Docker, or npm distribution claim is made.

What’s Next

Further device- and layout-specific testing can clarify behavior; no publication schedule or compatibility guarantee is implied.
-----BEGIN SSH SIGNATURE-----
U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgX2NaHGC5hCQmt33pGwJ9Qol/uM
b0mMXMNf+hgmeaGq4AAAADZ2l0AAAAAAAAAAZzaGE1MTIAAABTAAAAC3NzaC1lZDI1NTE5
AAAAQIBEcZCEif7qR9GxDn41gFVwKIICUHD98saGHXuBFQlkL9pEnjK5jlG0vQeiQCHatX
+3YFrTJPkmzkEgKXejNAs=
-----END SSH SIGNATURE-----

Assets 7
Loading