Package Details: authenticator-rs-bin 0.8.4-1

Git Clone URL: https://aur.archlinux.org/authenticator-rs-bin.git (read-only, click to copy)
Package Base: authenticator-rs-bin
Description: MFA Authenticator. TOTP-MFA application written in Rust and GTK3.
Upstream URL: https://github.com/grumlimited/authenticator-rs
Keywords: 2fa authenticator aws gnome google mfa security
Licenses: GPL3
Submitter: gr211
Maintainer: gr211
Last Packager: gr211
Votes: 6
Popularity: 0.20
First Submitted: 2020-06-25 21:54 (UTC)
Last Updated: 2024-07-23 08:40 (UTC)

Latest Comments

1 2 Next › Last »

jacobgkau commented on 2021-06-30 03:35 (UTC) (edited on 2021-06-30 03:35 (UTC) by jacobgkau)

@gr211 Sorry for the delay (again), but it's working great! I'm now being prompted for the keyring password when I open the application for the first time after booting. Thank you for implementing that!

gr211 commented on 2021-05-18 20:48 (UTC) (edited on 2021-05-18 20:49 (UTC) by gr211)

@jacobgkau I did try something to "ask" for keyring unlocking if locked in v0.6.8. Same story though, can't really test on KDE. Could you let me know how it goes for you ?

jacobgkau commented on 2021-05-18 02:31 (UTC)

@gr211 Sorry, I went a while without checking this page! The latest version no longer crashes, which is a big improvement. It now displays "Ouh la la!" followed by "keyring_locked", requiring me to open up Seahorse, click Unlock within Seahorse, then relaunch authenticator-rs. An Unlock button directly within authenticator-rs would still be nice (and logical, I think), but the error message is far clearer than a silent crash.

gr211 commented on 2021-03-28 19:57 (UTC)

@jacobgkau Finally found the time to make the changes you suggested. Please let me know how these go for you.

jacobgkau commented on 2021-02-16 02:53 (UTC) (edited on 2021-02-16 02:56 (UTC) by jacobgkau)

@gr211

Thank you for the pointers! I had already made sure that libsecret was installed and rebooted. After installing Seahorse, it also told me the keyring was locked, but it had a button to unlock it (and I was able to check the "unlock when I log in" option at that time.) I can use authenticator-rs again now that the keyring's been unlocked.

It might be worth trying to handle a locked keyring within the app (e.g. prompting to unlock instead of crashing) if it's going to depend on the keyring being unlocked.

Thanks again! Still the best authenticator app, even on KDE.

gr211 commented on 2021-02-15 21:08 (UTC) (edited on 2021-02-19 16:36 (UTC) by gr211)

@jacobgkau

could you install also libsecret (beside gnome-keyring). You might need to logout then log in again to let PAM do its magic.

I am hoping this will fix the 'Locked' message.

Also, to test further, if still not working, installing seahorse (which uses secret-service) should tell you whether your (gnome) keyring is working.

gr211 commented on 2021-02-15 21:02 (UTC) (edited on 2021-02-15 21:03 (UTC) by gr211)

@jacobgkau

I suppose the remark is fair. I did not want to make it too gnome-specific. But I guess it kind of is. I'd like it to work just as-is with KDE, but not using it myself, I can't really test it. And I did not want to force users to install gnome-related packages. I was kind of hoping KDE would come with some equivalent implementation. Looking at it again, seems like it's still work in progress :-(

https://community.kde.org/KDE_Utils/ksecretsservice

jacobgkau commented on 2021-02-15 18:32 (UTC)

Hmm, I had the same issue after updating, and after installing gnome-keyring (I'm using KDE Plasma, but I already have kwallet installed and I don't see what would provide ksecretsserviced), I'm now getting this:

thread 'main' panicked at 'Locked', src/main.rs:35:19

Is there further setup that should be required? (You might want to add gnome-keyring as a dependency, or gnome-keyring and whatever KDE package I'm evidently missing as optional dependencies.)

gr211 commented on 2021-01-29 17:20 (UTC) (edited on 2021-01-29 23:01 (UTC) by gr211)

Hey @schimicata, you might need gnome-keyring or ksecretsserviced. authenticator-rs now uses the secret-service api to securely store totp secrets.

schimicata commented on 2021-01-29 16:29 (UTC)

I can't start authenticator-rs since v0.6.x. At startup I alwalys get the following message in terminal:

thread 'main' panicked at 'Dbus(D-Bus error: The name org.freedesktop.secrets was not provided by any .service files (org.freedesktop.DBus.Error.ServiceUnknown))', src/main.rs:35:19 note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

The program won't start up at all.

With variable RUST_BACKTRACE=1 set, I get:

thread 'main' panicked at 'Dbus(D-Bus error: The name org.freedesktop.secrets was not provided by any .service files (org.freedesktop.DBus.Error.ServiceUnknown))', src/main.rs:35:19 stack backtrace: note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.

And with variable RUST_BACKTRACE=full I get:

thread 'main' panicked at 'Dbus(D-Bus error: The name org.freedesktop.secrets was not provided by any .service files (org.freedesktop.DBus.Error.ServiceUnknown))', src/main.rs:35:19 stack backtrace: 0: 0x5617e8e42120 - <unknown> 1: 0x5617e8e64eec - <unknown> 2: 0x5617e8e3e612 - <unknown> 3: 0x5617e8e44775 - <unknown> 4: 0x5617e8e44418 - <unknown> 5: 0x5617e8e44f11 - <unknown> 6: 0x5617e8e44a57 - <unknown> 7: 0x5617e8e425dc - <unknown> 8: 0x5617e8e449b9 - <unknown> 9: 0x5617e8e4496b - <unknown> 10: 0x5617e8b163cd - <unknown> 11: 0x5617e8b0a5b3 - <unknown> 12: 0x5617e8b0a5c9 - <unknown> 13: 0x5617e8e45427 - <unknown> 14: 0x5617e8b17612 - <unknown> 15: 0x7fc74f762152 - __libc_start_main 16: 0x5617e8aa5cfa - <unknown> 17: 0x0 - <unknown>

Last working version was v0.5.5.

1 2 Next › Last »