v0.1.2

Reqeek v0.1.2 — UI Improvements and Update Check

This release introduces a shared UI component layer for a more consistent interface and simplifies the update mechanism.

UI Component Layer

Introduced reusable UI components and migrated views to the shared component layer:

• Added Icon, IconButton, Input, Select, Checkbox, Dialog, FormField, and Spinner.
• Standardized spacing, control heights, icon sizes, typography, and transition durations.
• Replaced text-based UI glyphs with SVG icons for more consistent rendering.
• Replaced the native confirm() dialog in Settings with a custom Dialog.
• Added inline validation for out-of-range port values.

Update Check

Replaced electron-updater with a version check against the official API.

• Compares the latest available version with the installed app version.
• Provides a link to the website when a newer version is available.
• Removed the download-and-install workflow, which could not reliably complete across macOS and Windows.
• Simplified update status handling and error reporting.
• Removed the electron-updater dependency and obsolete publishing configuration.

Note: Updates are no longer downloaded or installed automatically. When a newer version is available, download it from the website.

v0.1.1

Reqeek v0.1.1 — Updates and Improvements

The settings window can now check for updates. When an update is available, users can either download the installer or have the update installed when the app restarts.

Update Mechanism

Windows and macOS use different update implementations due to differences in code signing.

• Windows: electron-updater handles the entire update process, including checking for updates, downloading, verification, and installation on quit. It verifies downloads using the SHA-512 hash in latest.yml and does not require an Authenticode signature, so it works without a signing certificate.
• macOS: The app checks for new versions, downloads the DMG, and opens it so users can manually drag the updated app into place. Squirrel.Mac validates updates against the running app's designated requirement. Because this build is ad-hoc signed (identity: '-') with no signing certificate or Team ID, that requirement can only match the current build's code directory hash (cdhash), causing every new release to fail validation. This check runs inside Electron's own binary and cannot be bypassed through an electron-builder configuration setting.

macOS Update Discovery and Rate-Limit Handling

On macOS, version information is retrieved from the GitHub API, which also provides the actual release asset list. Unauthenticated requests are limited to 60 per hour per egress IP, making shared IP addresses in offices, campuses, and proxy environments particularly susceptible to rate limits.

When the API returns HTTP 403, the updater now falls back to the redirect from:

github.com/<owner>/<repo>/releases/latest

It extracts the release tag from the Location header and reconstructs the DMG URL using the artifactName template.

Because this fallback does not provide an asset list, it depends on the artifact naming template. Cross-references between the API-based and fallback paths help keep their behavior consistent.

Clearer Update Error Messages

Update failures are now classified instead of being reported through a single generic message:

• Rate limited: Wait before retrying.
• Host unreachable: Check the network connection.
• No release available: No action is needed.

The main process now reports the specific failure type, making it easier to determine the appropriate next step.

Multi-Architecture Release Builds

Release builds now produce both architectures in a single job per platform, ensuring that latest.yml includes both x64 and ARM64 artifacts.

Previously, separate jobs could overwrite each other's uploads, leaving one architecture without an update. Building both architectures in the same job prevents this issue.

Localization

Expanded UI localization from three languages to nine, adding:

• German (de)
• Spanish (es)
• French (fr)
• Korean (ko)
• Portuguese (pt)
• Russian (ru)

Version

Updated to v0.1.1.

v0.1.0

Reqeek v0.1.0 — First Release

A local HTTP/HTTPS traffic capture tool that starts a proxy at 127.0.0.1:8989 to record and inspect requests and responses.

Downloads

Platform | File -- | -- macOS (Apple Silicon) | reqeek-0.1.0-mac-arm64.dmg macOS (Intel) | reqeek-0.1.0-mac-x64.dmg Windows x64 | reqeek-0.1.0-win-x64-setup.exe Windows ARM64 | reqeek-0.1.0-win-arm64-setup.exe

Linux currently includes packaging configuration only. Traffic capture is not yet supported on Linux.

Installation

macOS: The installer is not notarized (ad-hoc signed). If macOS reports that the developer cannot be verified when you first open the app, right-click the app icon and select Open.

If macOS reports that the app is damaged, run:

xattr -dr com.apple.quarantine /Applications/Reqeek.app

Windows: The installer is unsigned, so Windows SmartScreen may block it. Click More info → Run anyway to proceed.

First-time setup: Install and trust the root CA certificate through the app's interface. On macOS, this will trigger a system authorization dialog.

Important Notes

• Protect your root CA private key. It is stored in the application data directory at ca/ca.key. Anyone who possesses this key can impersonate arbitrary HTTPS websites. Do not share it. Uninstall the certificate through the app's interface when you no longer need it.

• Certificate pinning limitations: Applications that use certificate pinning will reject decryption. Their traffic can only be recorded in tunnel mode.

• Authorized use only: Use this tool only with devices and network traffic that you own or are authorized to inspect.