Skip to content

Security: keep the stored Unsplash key when the wallpaper is saved - #500

Merged
SandObserver merged 1 commit into
mainfrom
security/unsplash-key-editor
Oct 19, 2026
Merged

SandObserver merged 1 commit into
mainfrom
security/unsplash-key-editor

Conversation

@SandObserver

Copy link
Copy Markdown
Owner

Summary

  • Open the Unsplash API key inline editor empty, as a password field with autocomplete="new-password", instead of copying the row label into it.
  • Post the key from saveWallpaper only when one was typed, then clear the input and show the row as configured.
  • Read the configured state from /api/settings/unsplash-key and remove the unused #bg-apikey input from the admin page.

Testing
All green. Added 2 e2e tests: opening and saving sends no key, and a typed key is sent once.

Changelog

Security

  • Saving the wallpaper no longer replaces the stored Unsplash key with the field's label.

Checklist

  • Stays within the project constraints: one container, no runtime dependencies, no build step (see CONTRIBUTING.md).
  • Tests added or updated for new logic, and the full suite, lint, and typechecks pass.
  • Docs updated if behavior or configuration changed.

Open the API key field empty as a password input and send the key only when one is typed. Opening the field and saving no longer replaces the stored key with the row's label.
@SandObserver SandObserver added the security Security fix label Oct 19, 2026
@SandObserver
SandObserver merged commit aad8f0d into main Oct 19, 2026
6 checks passed
@SandObserver
SandObserver deleted the security/unsplash-key-editor branch October 19, 2026 01:57
stackyard-release Bot pushed a commit that referenced this pull request Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

security Security fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant