I am using linux mint and have the nextclound desktop application installed. After each login, I get another login screen: > Authentication required. > The login keyring did not get unlocked when you logged into your computer. Then I can enter my login password again and nextcloud starts without issue. When I open "Passwords" and Keys, Everything looks fine for me: nextcloud is part of the login keyring: How can I configure this, so that the nextcloud can access its keys without me entering the password twice. Edit: I just noticed that if I cancel the "Authentication required" dialog, the keyring is in the locked status:

Gnome Keyring (Seahorse / Passwords & Keys GUI app) resets the default Login keyring's password when updating its associated package. This is especially an issue on distributions with frequent updates as the keyring password has to be manually updated by the user after each update. As I have full-disk encryption (FDE) and auto-login enabled, my Login keyring password is set to empty/blank value so that Gnome doesn't ask the keyring to be manually unlocked on each login. How to fix this issue so that Gnome Keyring respects the existing password on package updates and not reset the password back to its original value?

I am unsure if I did the whole procedure right, so let's start with what I've done: $ ssh-keygen -vvv -o -a 1000 -t ed25519 -f ~/.ssh/id_ed25519 -C "$(whoami)@$(hostname)--$(date -I)" with some real strong password. I successfully logged into my Debian machine using that key (-i /path/to/private/key). I thought that's a success, so I've rebooted both machines and now my GNOME Keyring is empty on both Mint and Debian with me being unable to manually import the private key, I tried it: I have found that Seahorse (GNOME Keyring) currently does not handle Ed25519 on ArchWiki : The following citation was edited to be more up-to-date and to have various links to the Wikipedia and to be more readable. > As of January 2018, seahorse (GNOME Keyring) doesn't handle **ECDSA** {Bugzilla (*RESOLVED FIXED*), Wiki }, nor Ed25519 {Bugzilla (*NEW*), Wiki } keys. You can turn to other SSH agents if you need support for those. (Source - look at the bottom ). ------------------------------------ Do I need to wait for a bug fix / enhancement, or is there an alternative approach for me not to have to enter the complex password or enter it maybe once upon login? I don't honestly know, what my choices are at the moment. ------------------------------------ EDIT #1 ----------- I don't want to switch back to the ECDSA or RSA keys. EDIT #2 ----------- I have installed Linux Mint 19.1 (clean install, no upgrade), which is based on Ubuntu 18.04, but the issue in the same manner persists. The ed25519 does not show up in the Seahorse 3.20.0: ed25519 does not show up in the Seahorse" class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> ----------------- Listing keys: for key in ~/.ssh/id_*; do ssh-keygen -l -f "${key}"; done | uniq - Server: 256 SHA256:SMeBXPSluFwGBub/brKUy4/m8/DLim8Aw7zMmcdyEPs root@backup-server--2019-02-22 (ED25519) 8192 SHA256:JKKvLs+LXOdgv5nr00YFGjywqGANEFwCjXnzcjJ87og root@backup-server (RSA) - Client: 256 SHA256:WOj0Nl4svbiSxayTOCUC9LlI5nPQDyls9qV65u/0WwE vlastimil@dell-7577--2019-02-22 (ED25519) 8192 SHA256:GWPe50O7U0xq3DsRaQewz4WhOLrZ64Vf4x5bKnelrX4 vlastimil@dell-7577 (RSA)

This is the message that pops up - **Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer.** From what I've read online, it's a security measure. But if you enter your password on login, this won't pop up since the keyring is unlocked when that password is entered. But now when I use my fingerprint reader to log into my laptop, it asks for the password after. I should also add that this wasn't the case initially. It only started doing this after a couple of months or so - I'm not sure if an update to Fedora prompted this or not. It's not the end of the world, but annoying. I can just use my password, but then the fingerprint reader is less useful. I read that you can manage this in Passwords and Keys (formerly Seahorse), but it's not installed natively on Fedora, apparently it is on Ubuntu. If I install Seahorse now, could I use it to manage this? Or is there something in Fedora other than Seahorse, that could do the same thing? I saw a similar post about this here - https://unix.stackexchange.com/q/671075/585410 - My fingerprint reader does let me into my computer, I just still have to use my password to unlock the keyring. It works fine for everything else (making changes, sudo commands in terminal, etc). Thank you in advance, and I apologize in advance - still learning Linux.

I am on Linux Mint 17.3 and have the auto-login enabled. I have my SSH key in gnome-keyring. I would like the keyring not to ask me for my password upon login. I am aware the auto-login itself may seem to pose a security risk, but this question is not about that.

Passwords and Keys alias seahorse won't run if clicked on. When launched from terminal, I get this error:

seahorse: error while loading shared libraries: libldap_r-2.4.so.2: cannot open shared object file: No such file or directory

When trying to find such package and possibly install it I get:

$ apt-cache policy 'libldap*'
libldap2:
  Installed: (none)
  Candidate: (none)
  Version table:
libldap-common:
  Installed: 2.5.13+dfsg-0ubuntu0.22.04.1
  Candidate: 2.5.13+dfsg-0ubuntu0.22.04.1
  Version table:
 *** 2.5.13+dfsg-0ubuntu0.22.04.1 500
        500 http://archive.ubuntu.com/ubuntu  jammy-updates/main amd64 Packages
        500 http://archive.ubuntu.com/ubuntu  jammy-updates/main i386 Packages
        100 /var/lib/dpkg/status
     2.5.11+dfsg-1~exp1ubuntu3.1 500
        500 http://security.ubuntu.com/ubuntu  jammy-security/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu  jammy-security/main i386 Packages
     2.5.11+dfsg-1~exp1ubuntu3 500
        500 http://archive.ubuntu.com/ubuntu  jammy/main amd64 Packages
        500 http://archive.ubuntu.com/ubuntu  jammy/main i386 Packages
libldap-ocaml-dev:
  Installed: (none)
  Candidate: 2.4.2-1build3
  Version table:
     2.4.2-1build3 500
        500 http://archive.ubuntu.com/ubuntu  jammy/universe amd64 Packages
libldap-dev:
  Installed: 2.5.13+dfsg-0ubuntu0.22.04.1
  Candidate: 2.5.13+dfsg-0ubuntu0.22.04.1
  Version table:
 *** 2.5.13+dfsg-0ubuntu0.22.04.1 500
        500 http://archive.ubuntu.com/ubuntu  jammy-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.5.11+dfsg-1~exp1ubuntu3.1 500
        500 http://security.ubuntu.com/ubuntu  jammy-security/main amd64 Packages
     2.5.11+dfsg-1~exp1ubuntu3 500
        500 http://archive.ubuntu.com/ubuntu  jammy/main amd64 Packages
libldap-ocaml-dev-vpsg7:
  Installed: (none)
  Candidate: (none)
  Version table:
libldap-2.3-0:
  Installed: (none)
  Candidate: (none)
  Version table:
libldap-2.4-2:
  Installed: (none)
  Candidate: (none)
  Version table:
libldap-2.5-0:
  Installed: 2.5.13+dfsg-0ubuntu0.22.04.1
  Candidate: 2.5.13+dfsg-0ubuntu0.22.04.1
  Version table:
 *** 2.5.13+dfsg-0ubuntu0.22.04.1 500
        500 http://archive.ubuntu.com/ubuntu  jammy-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.5.11+dfsg-1~exp1ubuntu3.1 500
        500 http://security.ubuntu.com/ubuntu  jammy-security/main amd64 Packages
     2.5.11+dfsg-1~exp1ubuntu3 500
        500 http://archive.ubuntu.com/ubuntu  jammy/main amd64 Packages
libldap-java:
  Installed: (none)
  Candidate: 5.0.0+dfsg1-1
  Version table:
     5.0.0+dfsg1-1 500
        500 http://archive.ubuntu.com/ubuntu  jammy/universe amd64 Packages
        500 http://archive.ubuntu.com/ubuntu  jammy/universe i386 Packages
libldap2-dev:
  Installed: 2.5.13+dfsg-0ubuntu0.22.04.1
  Candidate: 2.5.13+dfsg-0ubuntu0.22.04.1
  Version table:
 *** 2.5.13+dfsg-0ubuntu0.22.04.1 500
        500 http://archive.ubuntu.com/ubuntu  jammy-updates/main amd64 Packages
        500 http://archive.ubuntu.com/ubuntu  jammy-updates/main i386 Packages
        100 /var/lib/dpkg/status
     2.5.11+dfsg-1~exp1ubuntu3.1 500
        500 http://security.ubuntu.com/ubuntu  jammy-security/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu  jammy-security/main i386 Packages
     2.5.11+dfsg-1~exp1ubuntu3 500
        500 http://archive.ubuntu.com/ubuntu  jammy/main amd64 Packages
        500 http://archive.ubuntu.com/ubuntu  jammy/main i386 Packages
$ sudo apt-get --simulate install libldap-2.4-2
[sudo] password for vlastimil:                
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package libldap-2.4-2 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  libldap-common

E: Package 'libldap-2.4-2' has no installation candidate
$ sudo apt-get --simulate install libldap-2.4
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'libldap-2.4-2' for regex 'libldap-2.4'
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

$ which seahorse 
/usr/local/bin/seahorse
$ whereis seahorse
seahorse: /usr/bin/seahorse /usr/local/bin/seahorse /usr/libexec/seahorse /usr/share/seahorse /usr/share/man/man1/seahorse.1.gz

so naturally I tried /usr/bin/seahorse and I got it up and running: seahorse up and running" class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> So, I digged in Downloads directory, found:

/home/vlastimil/Downloads/seahorse/seahorse-3.31.91

with timestamp 2019-Feb-23. Built by meson, but how to remove it?

I have some libreoffice documents stored with "encrypt with gpg key" option. Today I was quite surprised when the document opened without requesting a passphrase. Eventually I found an entry for my gpg key in the system key and password manager, Seahorse, where the passphrase could be displayed. I conclude that I must have accidentally checked the "save in password manager" box in the pinentry dialog when I logged in the last time. A small mistake exposed a confidential document and my most important password. This appears to be the same problem as here: but in my case free access to the document and the Seahorse entry survive beyond the timeout defined in gpg-agent.conf, after echo RELOADAGENT | gpg-connect-agent and even after a reboot. I tried gnupg.conf no-allow-external-cache option, which causes a different pinentry dialog without the checkbox, but then the private key password is not accepted. Is there a way to remove or disable that checkbox in the pinentry dialog? My system: MX-linux 18.3_x64 December 15 2017 base: Debian GNU/Linux 9 (stretch) gpg (GnuPG) 2.1.18

I am using the bitwarden password manager add on for firefox. If I set "remember password" for the master password, bitwarden warns me that the password will be stored in plain text on my pc which is insecure. My question is; **is it possible to store my bitwarden master password in seahorse (linux Passwords and Keys), so I will be able to automatically login to bitwarden every time I open my browser in a secure way.** Thanks.

Like this question , I am looking for a password repository and that I can use to feed my programs and scripts with those passwords. I found seahorse which seems to have what I need under the "Login" folder but I am not quite sure where the passwords are stored (for backup) and I don't know how to get the passwords in shell so I can pipe them into my scripts. I was under the impression that I can use gpg to access those passwords, but I don't quite know how. Is it possible to access (and create) those passwords in terminal?

I'm trying to change the passphrase of my GPG's secret key. I actually changed it using seahorse (Also tried gpg --edit-keys and passwd, but when I tried to export my private key it asks me for two passphrase now (Both new and old one) and uses the old one for sub secret key. Now I have to remember two complicated password! What is the correct way to change the passphrase of GPG's secret key?

What does the "Certificates" / "System Trust" section of seahorse do? I am [trying to sign a document in LibreOffice](https://ask.libreoffice.org/en/question/224355/no-certificates-show-up-when-trying-to-sign-a-document/) and the menu there uses the word "Certificate", so I am thinking that I need to have something here. I already have my GPG key imported into the "PGP Keys" -> "GnuPG keys" menu and its trust is set to ultimate. Is there a way I can make the system trust the key or make the key into a certificate so that I can use it to sign my document? Or is this part of the menu for something completely different (if so, how do I get LibreOffice to use my GPG key?).

I forgot my login password. So I booted into recovery mode and used passwd command to change the password. I can now login but I obviously didn't update my Gnome keyring password. I know my old password close enough to brute force it if need be, but I can't figure out how to do this on the command line. Is it possible to login to the Gnome keyring (Seahorse) on the command line? (Or something similar)? My setup is Debian 9, Gnome 3.22.2.

Here’s a Yet Another Question about the clash between ssh and gnome-keyring-daemon, since after spending hours and hours on the Internet I finally gave up. Environment ----------- - OS: openSUSE 15.0 - DE: XFCE - gnome-keyring-daemon version: 3.20.1 - seahorse version: 3.20.0 - git version: 2.16.4 - ssh version: OpenSSH_7.6p1, OpenSSL 1.1.0i-fips 14 Aug 2018 Situation --------- Trying to git pull a repo leads to a message sign_and_send_pubkey: signing failed: agent refused operation , even though for years I was getting a neat GUI prompt which remembered the typed password throughout the current session. (AFAIU, this prompt was shown by Seahorse?). After doing a killall gnome-keyring-daemon, successive attempts to do a git pull lead to a terminal prompt Enter passphrase for key '/home/user/.ssh/id_rsa': which does not store the password anywhere (AFAIU, this means that ssh-agent is not working?). The same effect can be achieved by adding SSH_AUTH_SOCK=0 in front of git pull. What I want ----------- - Doing a git pull caches my SSH password over the course of my current login session (like it was before). Neat GUI prompt is optional. - Ed25519 keys are supported. (Apparently GNOME Keyring has (had?) some problems with them). What I tried ------------ - Disabling “SSH Key Agent” in XFCE settings → Startup Applications - Copying /etc/xdg/autostart/gnome-keyring-ssh.desktop to ~/.config/autostart and then appending the line Hidden=true to the copied file Neither of the above prevented gnome-keyring-daemon from starting up on boot, since I still can see it in ps. - Creating ~/.pam_environment then adding GSM_SKIP_SSH_AGENT_WORKAROUND DEFAULT=1 there - Reverting back to RSA - Playing with ssh-add - Installing git-credential-libsecret then doing git config --global credential.helper /usr/lib/git/git-credential-libsecret - Toying with the thought of obliterating the gnome-keyring package altogether, which was abandoned because apparently several important packages depend on it