The v5.6 password change went down badly and broke the other ports: raising PBKDF2 to 600k changed the key recipe, so the SAME password produced a DIFFERENT key on 5.6 vs every other build (the iOS/TestFlight app, older desktops) — same password, no audio. Ed: back it out so the other ports can use it again; a password is still required, just suggest a strong one. Reverted: - PBKDF2 100k again (RemSoundCrypto) — the key recipe now matches the other ports, so the same password derives the same key and audio flows again. Pinned by a gate check so an accidental change can't silently re-break cross-port compat. - ForPlainPassword no longer refuses a weak password: ANY non-empty password derives a key (encryption stays mandatory — empty still means no audio). Strength is not enforced. - Removed every enforcement/nag: the streaming-tick force-strengthen, the startup weak-password dialog, the status-line weak warning, the app's weak-SERVICE-password launch + live nags, and the service-profile save-time block. The password dialogs just suggest a strong password in their hint now; PasswordStrength.cs deleted (now unused). Someone who set a strong password because of 5.6 feels no difference on update — their password still loads and works, no prompt (Ed's requirement). Kept (separate from "stronger passwords", not backed out): signed updates, password- sealed remote volume, service startup volume, the update time-window, the nonce widening, and the relay address-proof. NOTE: sealed remote-volume still needs both ends on 5.6+ — ordinary audio does not. Flagging in case full remote-volume interop with old ports is wanted too. Docs: About + readme + release notes rewritten for v5.7 (plain English, positive framing, no "must update"). MANUAL.md regenerated. Version 5.7. Gate 70/70 (dropped the now-moot streaming-strengthening step) + 7 relay tests. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
29 lines
1.8 KiB
Markdown
29 lines
1.8 KiB
Markdown
# RemSound v5.7
|
|
|
|
Stronger security, and it works with every version again.
|
|
|
|
This release puts the password handling back the way it was, so RemSound talks to older versions and the iPhone app again. You still set a password — your audio is always encrypted — RemSound just suggests a strong one now instead of requiring it. If you already use a good password, you won't notice any difference.
|
|
|
|
## Signed updates
|
|
|
|
Every release is now digitally signed, and the updater refuses anything that isn't genuinely from us — so even if the download page were ever tampered with, a fake update couldn't install itself on your machine.
|
|
|
|
## Remote volume, password-protected
|
|
|
|
The remote volume and mute controls are locked to your password, so only someone who shares it can use them. (Both ends need 5.6 or newer for the remote-volume feature; ordinary audio works with any version.)
|
|
|
|
## Set the machine's volume when the service starts
|
|
|
|
In the service's Additional options you can have an unattended machine unmute itself and set its Windows volume to a level you choose — on the first start after each boot, or on every service start.
|
|
|
|
## Updates on your schedule
|
|
|
|
In Preferences you can restrict automatic updates to a daily time range — say 1am to 6am — so an update never closes RemSound and interrupts you. Found outside the range, it quietly waits and installs the moment the range opens.
|
|
|
|
## Also in this release
|
|
|
|
- The app releases its high-priority and keep-awake settings when you're not actually streaming — kinder to laptops left idling in the tray.
|
|
- Diagnostic logs cap their own size on long sessions, and old crash reports are tidied automatically.
|
|
- The remembered-applications list explains itself when empty.
|
|
- A large amount of behind-the-scenes hardening from a full security audit.
|