ssh component is not included

Description:

I noticed that in the latest version of the package v46.1-1, the ssh component is not present and this feature has been lost.

I have found an upstream commit that disables this feature by default and the new flag not present in PKGBUILD, but the openssh dependency is not removed.

The wiki details that you have two options to configure GNOME Keyring to work with SSH keys, I think the build should be made including this feature. For now the Fedora proposal is stalled and as other upstream issue suggests, it is a proposal for a specific distribution and it is not entirely clear the decision to remove it.

added priority3-normal severity4-low statusunconfirmed labels

assigned to @morganamilo, @toolybird, and @thurstylark

changed the description

The Wiki page might be slightly behind the times.. but it covers the solution going forward. Re-enabling the old option might be considered a backwards step, but of course it's a decision for the PM.

Edit: Wiki now updated

added scopefeature statusconfirmed labels and removed statusunconfirmed label

assigned to @heftig and unassigned @morganamilo, @toolybird, and @thurstylark

changed due date to March 19, 2024

All in all this is very wonky and a way to bad UX. Fedora also have reverted this change. Upstream does have a bug report here

This worked for me:

1. Install gcr-4: pacman -S gcr-4
2. Set the env for example: mkdir ~/.config/environment.d && echo 'SSH_AUTH_SOCK=$XDG_RUNTIME_DIR/gcr/ssh' > ~/.config/environment.d/SSH_AUTH_SOCK.conf
3. Enable the user socket: systemctl --user enable gcr-ssh-agent.socket
4. logout and login again

---

TBH, I'm not a fan of this as it is currently a unexpected change that is way to hard to track down.

Maybe we could import: https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/137 so at least the very annoying part to set the env var is not a problem. I'd love if we could default to enable the socket. Since that's how it was with gnome-keyrings implementation. But in my testing with # systemctl --global enable gcr-ssh-agent.socket the socket just never started the the service.

Thank you, this works. However, will there be any part of this that we have to remove once a proper fix is in place?

It depends how upstream will move forward. Best case would be that you can revert both changes at some point because everything is in place by default.

I had a hard time figuring out what was going on when this suddenly changed. It works with gcr-4, but having to set up the SSH_AUTH_SOCK manually is a bit of a hassle. The old solution was working ootb, although I don't know how. I tried the systemctl --user set-environment solution, but it didn't work and I hadn't expected it to, because this will only apply to systemd units started later. I guess what you'd need instead is a script in /etc/profile.d.

We're committed to using the agent in gcr-4. You just need to enable its socket manually (systemctl --user enable gcr-ssh-agent.socket or systemctl --global enable gcr-ssh-agent.socket); the environment will be applied with it.

I'm using gcr-4 and the socket starts gcr-ssh-agent.service correctly as expected.

I think the issue is being misunderstood. It's not a complaint about something not working any more. I was trying to ask about two situations that I encountered when the change was made and that caused me a lot of confusion to understand what decision the Arch team had taken.

• Is openssh a required dependency since the ssh functionality has been completely removed from gnome-keyring?
• Based on the wiki documentation at that time, if we can have two options to run the ssh agent, then why not add the flag to enable the ssh component if the dependency is still in the PKGBUILD.

As an arch user, I sometimes encounter such changes abruptly without any kind of notification that a restructuring has been applied and that it can break your system. This is something that would be interesting to work on, rather than publishing changes and leaving users to spend hours piecing together what has happened and why.

Thank you for taking the time to review the issue, you can close it on my end.

closed with commit a99f6073

mentioned in issue #4 (closed)

I just realized, that gui feature to ask for ssh keypass is not enabled by default on new installations. Is it possible to make it the default behavior in new installations?

Just found this issue for the proposed solution systemctl --global enable gcr-ssh-agent.socket, which worked for me. But I just knew that this feature was there. I wonder how the new users should learn about this feature.

I wonder how the new users should learn about this feature.

With good luck and a bit of wiki skills. Otherwise we still wait for upstream to move.

added resolutioncompleted label

mentioned in issue pipewire#10 (closed)