View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003008Kali LinuxGeneral Bugpublic2016-01-24 05:062025-07-14 09:14
Reportercyphergenetics Assigned Torhertzog  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Product Version2.0 
Summary0003008: Issue on Kali Rolling SSH - Could not open a connection to your authentication agent.
Description

I have added ssh keys from an old laptop. Ssh to my server and it keeps asking for password. Noticed when i did "ssh-add -l" it spits out - "Could not open a connection to your authentication agent" or "No identities" .. So i have to type password on every session. Noticed it could be a Xsession issue with gdm3 and ssh-add, but i was wrong. It was something to do with keychains and keyrings.

Did a "dpkg-reconfigure libpam-runtime" and unchecked "Authenticate using SSH keys and start ssh-agent" and rechecked to no avail.

Fixed it after copying /etc/xdg/autostart/gnome-keyring-ssh.desktop, /etc/xdg/autostart/gnome-keyring-sexrets.desktop, /etc/xdg/autostart/gnome-keyring-pkcs11.desktop -> ~/.config/autostart/

Steps To Reproduce

  • Ssh to server

  • Type password

  • Do a ssh-add "your keyfile"

  • reboot

  • Do a ssh-add -l and error will pop out of no identities or could not open authentication to agent

  • logout and logback in to somehow fix the issue

Activities

cyphergenetics

cyphergenetics

2016-01-24 05:11

reporter   ~0004591

Forgot to mention, i have edited /etc/gdm3/daemon.conf with Autologin lines to bypass the login manager.

[daemon]

Enabling automatic login

AutomaticLoginEnable = true
AutomaticLogin = root

Enabling timed login

#TimedLoginEnable = true
#TimedLogin = root
#TimedLoginDelay = 20

Reserving more VTs for test consoles (default is 7)

FirstVT = 9

[security]
AllowRoot = true
rhertzog

rhertzog

2016-01-24 08:19

administrator   ~0004595

With auto-login, this means that your GNOME user keyring is not unlocked at login.

Are you sure that you are not typing the password to unlock the user keyring?
cyphergenetics

cyphergenetics

2016-01-24 08:25

reporter   ~0004597

Last edited: 2016-01-24 08:31

Yes, i am sure there was no pop up for passphases for ssh keyfile. Checked again. Seems also could be

dhcpcd-gtk/unknown 0.6.0-1.1 amd64
GTK+ frontend for dhcpcd and wpa_supplicant

dhcpcd5/unknown 6.9.3-1 amd64
DHCPv4, IPv6RA and DHCPv6 client with IPv4LL support

fault.. Uninstalled and everything works per normal. After moving those gnome keyring, by relogin, nm-applet seems to stop working and so as DHCPCD. Only fix was to reboot. 1st login works fine. 2nd relogin, error was reproduced. Sadly now i will miss the pop up messages that keeps appearing when a new wireless network is found.
rhertzog

rhertzog

2016-01-24 08:42

administrator   ~0004598

Thanks, closing the ticket then.

Issue History

Date Modified Username Field Change
2016-01-24 05:06 cyphergenetics New Issue
2016-01-24 05:11 cyphergenetics Note Added: 0004591
2016-01-24 08:19 rhertzog Note Added: 0004595
2016-01-24 08:25 cyphergenetics Note Added: 0004597
2016-01-24 08:28 cyphergenetics Note Edited: 0004597
2016-01-24 08:28 cyphergenetics Note Edited: 0004597
2016-01-24 08:31 cyphergenetics Note Edited: 0004597
2016-01-24 08:42 rhertzog Note Added: 0004598
2016-01-24 08:42 rhertzog Status new => closed
2016-01-24 08:42 rhertzog Assigned To => rhertzog
2016-01-24 08:42 rhertzog Resolution open => no change required
2025-07-14 09:14 g0tmi1k Priority immediate => normal