<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/pam-ssh/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/pam-ssh/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/pam-ssh/feature-requests/</id><updated>2021-07-02T08:29:59.061000Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>#4 support auto-adding ecdsa_sk and ed25519_sk keys</title><link href="https://sourceforge.net/p/pam-ssh/feature-requests/4/?limit=25#250b" rel="alternate"/><published>2021-07-02T08:29:59.061000Z</published><updated>2021-07-02T08:29:59.061000Z</updated><author><name>Stefan Winter</name><uri>https://sourceforge.net/u/kickdown/</uri></author><id>https://sourceforge.net0f938971c25e17e50d4c2e55e6367b899b0ba9da</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Looking at the code, I do see ed25519_sk, but not ecdsa_sk, so my feature request reduces to ecdsa_sk support. ("I don't have a security key supporting ed25519_sk, you insensitive clod!") ;-)&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>support auto-adding ecdsa_sk and ed25519_sk keys</title><link href="https://sourceforge.net/p/pam-ssh/feature-requests/4/" rel="alternate"/><published>2021-07-02T08:24:14.357000Z</published><updated>2021-07-02T08:24:14.357000Z</updated><author><name>Stefan Winter</name><uri>https://sourceforge.net/u/kickdown/</uri></author><id>https://sourceforge.neta96fc7d2d77f7d374b800284994bb0a91f9798e0</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;pam_ssh does not seem to support loading hardware-backed keys (ecdsa_sk and ed25519_sk). I have added such a key in both the .ssh/ and .ssh/login-keys.d/ directories along with three others of type id_rsa, id_ecdsa and id_ed25519. All four keys have the same passphrase.&lt;/p&gt;
&lt;p&gt;When logging in with pam_ssh, the three others are unlocked and added to the ssh-agent session, but the ecdsa_sk one is not.&lt;/p&gt;
&lt;p&gt;The key itself is in order, a manual "ssh-add id_ecdsa_sk" adds the key just fine.&lt;/p&gt;
&lt;p&gt;I believe the code would need to be(come) aware of *_sk keys first. Can you confirm  this is a missing feature?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#3 ED25519 key support</title><link href="https://sourceforge.net/p/pam-ssh/feature-requests/3/?limit=25#d0f9" rel="alternate"/><published>2015-05-06T08:11:56.277000Z</published><updated>2015-05-06T08:11:56.277000Z</updated><author><name>Wolfgang Rosenauer</name><uri>https://sourceforge.net/u/rosenauer/</uri></author><id>https://sourceforge.net0082fc65477227eb574ce023811a834d60b8010b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;assigned_to&lt;/strong&gt;: Wolfgang Rosenauer&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</summary></entry><entry><title>#3 ED25519 key support</title><link href="https://sourceforge.net/p/pam-ssh/feature-requests/3/?limit=25#42db" rel="alternate"/><published>2015-05-06T08:11:34.489000Z</published><updated>2015-05-06T08:11:34.489000Z</updated><author><name>Wolfgang Rosenauer</name><uri>https://sourceforge.net/u/rosenauer/</uri></author><id>https://sourceforge.net76b4f4c24ac009da30541357dfe02c6cf0dd0167</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;ED25519 key support released in 2.1&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#3 ED25519 key support</title><link href="https://sourceforge.net/p/pam-ssh/feature-requests/3/?limit=25#8c3f" rel="alternate"/><published>2015-01-18T05:54:32.287000Z</published><updated>2015-01-18T05:54:32.287000Z</updated><author><name>Siuchung Cheung (Clement)</name><uri>https://sourceforge.net/u/sccheung/</uri></author><id>https://sourceforge.net6b26ffeabea34ed1556dbf26d86ce4bc191a1cc3</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Looked into this problem a little further. It appears that ssh-add is produced like this in OpenSSH Makefile:&lt;br /&gt;
ssh-add$(EXEEXT): $(LIBCOMPAT) libssh.a ssh-add.o&lt;br /&gt;
    $(LD) -o $@ ssh-add.o $(LDFLAGS) -lssh -lopenbsd-compat $(LIBS)&lt;/p&gt;
&lt;p&gt;So the ugly but easy way out is to pick up the whole thing like ssh-add did and forget about getting rid of functions we don't need...&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>ED25519 key support</title><link href="https://sourceforge.net/p/pam-ssh/feature-requests/3/" rel="alternate"/><published>2015-01-18T05:26:05.073000Z</published><updated>2015-01-18T05:26:05.073000Z</updated><author><name>Siuchung Cheung (Clement)</name><uri>https://sourceforge.net/u/sccheung/</uri></author><id>https://sourceforge.netfe46e23d3bbca6499a5bbabee60cf04c8d31c212</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Pretty much the same as ECDSA support added in 2.0. Need another sync from OpenSSH to pick up the new code with EC25519 support.&lt;/p&gt;
&lt;p&gt;I can see in the TODO file that you're planning to switch to using ssh-add. That would avoid the need to do more syncs. But if we're not doing that, the OpenSSH code should probably be in a separate directory to facilitate further syncing. There seems to be more than 1 file that comes from OpenSSH. Thanks.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>ED25519 key support</title><link href="https://sourceforge.net/p/pam-ssh/feature-requests/3/" rel="alternate"/><published>2015-01-18T05:26:05.073000Z</published><updated>2015-01-18T05:26:05.073000Z</updated><author><name>Siuchung Cheung (Clement)</name><uri>https://sourceforge.net/u/sccheung/</uri></author><id>https://sourceforge.nete6332c5360e845ba2a9093e023ae833f15f8479a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Ticket 3 has been modified: ED25519 key support&lt;br /&gt;
Edited By: Wolfgang Rosenauer (rosenauer)&lt;br /&gt;
Status updated: u'open' =&amp;gt; u'closed'&lt;br /&gt;
Owner updated: None =&amp;gt; u'rosenauer'&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Re-add identity to already running agent</title><link href="https://sourceforge.net/p/pam-ssh/feature-requests/2/" rel="alternate"/><published>2009-09-24T18:53:41Z</published><updated>2009-09-24T18:53:41Z</updated><author><name>Robert Cernansky</name><uri>https://sourceforge.net/u/openhs/</uri></author><id>https://sourceforge.nete38cc2877fcbf7618d1a7e0f6b7a0299776a3526</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It would be usefull if pam_ssh will try to add identity if it finds already running agent for a user. This would handle situations like hibernation when identities are removed from agent and user is still logged in. The scenario would be following:&lt;/p&gt;
&lt;p&gt;1. User logs in.&lt;br /&gt;
2. ssh-agent is started. Identity is unlocked and added to the agent.&lt;br /&gt;
3. User suspends the system to disk. Suspend script deletes all identities from ssh_agent for security reasons.&lt;br /&gt;
4. User resumes and unlocks the screen(saver) with its password.&lt;br /&gt;
5. pam_ssh founds that ssh-agent for that user is already running so it tries to unlock and add the identity to that running agent.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Authentication against ssh-agent</title><link href="https://sourceforge.net/p/pam-ssh/feature-requests/1/" rel="alternate"/><published>2002-07-15T21:40:08Z</published><updated>2002-07-15T21:40:08Z</updated><author><name>Chip Marshall</name><uri>https://sourceforge.net/u/kyzoku/</uri></author><id>https://sourceforge.neta1976aa02a68381671bd90d54b4ca9b5f801536b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Would it be possible to make the module capable of&lt;br /&gt;
using an existing ssh-agent to authenticate the user?&lt;br /&gt;
This would be useful for commands like su and sudo.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>