Releases: ray910408/Universal_Clipboard
v0.4.0 — Download, Extract, Run
-
Added
UniversalClipboard.exefor a simpler download → extract → run setup. -
Added runtime payload validation before startup.
-
Added automatic firewall rule check / repair with elevation prompt when needed.
-
Tray Exit now removes the app-created firewall rule during normal shutdown.
-
Updated README, setup docs, and release checksum output.
Same limits as before: trusted LAN only, self-signed HTTPS, no cloud relay, no mobile app.
v0.3.1 — Mobile Session & Browser Detection Fixes
Fixed
-
Fixed mobile session refresh failures after the browser was sent to the background.
-
Fixed Android Chrome being incorrectly displayed as Safari.
-
Improved mobile browser metadata detection.
Changed
-
Updated README and documentation to consistently describe bidirectional Android Chrome usage.
-
Aligned mobile browser support notes across the documentation and release smoke checklist.
Notes
Android Chrome already worked with the browser-based clipboard bridge, but this release fixes session/background behavior, corrects browser labeling, and updates the documentation to reflect the supported bidirectional flow more accurately.
The same security limits still apply: trusted LAN only, self-signed HTTPS, TOFU-style local trust, no cloud relay, and no mobile app.
v0.3.0 — Persistent HTTPS Identity & TOFU
-
Persisted the local self-signed HTTPS identity per selected IPv4 address.
-
Protected the stored HTTPS identity with current-user Windows DPAPI.
-
Added certificate short code / fingerprint display in the tray.
-
Added Reset HTTPS, which generates a new HTTPS identity and revokes existing pairings.
-
Updated security notes and troubleshooting.
Universal Clipboard still uses self-signed HTTPS. This improves identity stability after first trusted use, but it does not provide private CA trust or automatic browser certificate pinning. Use only on trusted Private networks.
v0.2.0 — Bidirectional Text Bridge & Device Permissions
v0.2.0 — Bidirectional Text Bridge
Added
- iPhone Safari → Windows text transfer
- Read / Write pairing permissions
- Pending incoming text approval flow
- Paired device details in tray
Changed
- Existing authorizations now migrate as Read only
- Documentation and release checks updated
Security
Incoming iPhone text is never applied automatically and remains pending until approved from the Windows tray.
First MVP: local Windows-to-iPhone text clipboard bridge
- Text only
- Same private LAN only
- Self-signed HTTPS certificate
- Safari may require manual copy fallback
- Unsigned Windows binary may trigger SmartScreen