Skip to content

v0.1.13

Choose a tag to compare

View all tags
@ehstbr ehstbr released this 08 Aug 11:34
· 21 commits to main since this release
v0.1.13
461761e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

PyNextCloud Sync 0.1.13

Version 0.1.13 fixes credential access when the GNOME session is started using fingerprint authentication.

Fixed: GNOME Keyring after biometric login

When signing in using a fingerprint, GNOME may leave the default Login keyring locked because the login password was not entered. Previous versions attempted to find the Nextcloud credential before explicitly unlocking this collection. In this situation, the Secret Service could return no matching items, causing the application to incorrectly report that no credential was stored.

PyNextCloud Sync now:

  1. locates the default GNOME password collection;
  2. checks whether the collection is locked;
  3. requests the native GNOME unlock dialog;
  4. waits for the collection to be unlocked;
  5. searches for the stored Nextcloud credential only after the unlock operation;
  6. starts synchronization and notify_push automatically.

The keyring password is handled exclusively by GNOME. It is never received, processed, or stored by PyNextCloud Sync.

If the unlock dialog is canceled, the application remains in the Password keyring locked state instead of incorrectly reporting an account error.

Improved diagnostics

The application log now records the relevant stages of password-collection access, including:

  • whether the default collection was found;
  • whether it was locked;
  • whether an unlock request was initiated;
  • whether the collection was successfully unlocked;
  • whether the credential search returned a matching item.

Passwords and other sensitive credential data are never written to the log.

Other updates

  • Updated changelog and version information.
  • Updated About window, AppStream data, Debian metadata, documentation, and translations.
  • Retained the safe Debian upgrade process introduced in previous releases, which closes the running application before replacing its files and restarts it afterward.

Installation

Download pynextcloud-sync_0.1.13_all.deb and run:

sudo apt install ./pynextcloud-sync_0.1.13_all.deb

To verify the biometric-login fix, restart the computer, sign in using your fingerprint, and allow PyNextCloud Sync to start automatically. The native GNOME dialog should request the keyring password before synchronization begins.

The complete source package is available as PyNextCloud-Sync-0.1.13.zip.

Verification

This release passed 75 automated tests, including the scenario in which an initial credential search returns no items while the default collection is locked.

The final artifacts were also checked for:

  • correct for_alias_sync → unlock_sync → search_sync execution order;
  • Debian package metadata and internal checksums;
  • maintainer-script permissions;
  • AppStream XML validity;
  • reproducible builds;
  • tests executed again from the extracted source ZIP.

SHA-256

DEB:
f51bdeb33438b90347f11b0126fc10b19ae0fb8d018a3270aa44022727e07617

Complete source ZIP:
cf1ebbc535bd8cf641cef27a765c3f8cf38c1eaab9816699d6a0c68445c94112

Changed files ZIP:
3c8d8b5f5560e188c6f53c6d12e89a2df48270e1bfb3285fc2b4dd138eb7956e

Important notice

PyNextCloud Sync performs bidirectional synchronization. Changes and deletions may be propagated between the computer and the Nextcloud server.

Always maintain an independent backup of important data. See the complete [Terms of Use](https://github.com/ehstbr/PyNextCloud-Sync/blob/main/TERMS.md).

Links

PyNextCloud Sync is distributed under the [MIT License](https://github.com/ehstbr/PyNextCloud-Sync/blob/main/LICENSE).

Nextcloud is a trademark of Nextcloud GmbH. PyNextCloud Sync is an independent, unofficial project and is not affiliated with, endorsed by, or sponsored by Nextcloud GmbH.

Assets 4
Loading