<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/pamsshagentauth/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/pamsshagentauth/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Thu, 23 Mar 2023 17:15:31 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/pamsshagentauth/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>sk-ed25519 support</title><link>https://sourceforge.net/p/pamsshagentauth/feature-requests/11/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Now that &lt;a href="https://sourceforge.net/p/pamsshagentauth/feature-requests/10/"&gt;https://sourceforge.net/p/pamsshagentauth/feature-requests/10/&lt;/a&gt; is fixed, would it not be easy to add support for 'sk-ssh-ed25519@openssh.com' keys as well?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Martin Jørgensen</dc:creator><pubDate>Thu, 23 Mar 2023 17:15:31 -0000</pubDate><guid>https://sourceforge.netc975c9e921942350fff9d632bfcce8b5e5d7802e</guid></item><item><title>#10 support ecdsa and ed25519 keys</title><link>https://sourceforge.net/p/pamsshagentauth/feature-requests/10/?limit=25#2070</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jakub Jelen</dc:creator><pubDate>Mon, 17 Sep 2018 08:10:51 -0000</pubDate><guid>https://sourceforge.net0cf1bc310361409aed907b90207efdbd6698c5c3</guid></item><item><title>#10 support ecdsa and ed25519 keys</title><link>https://sourceforge.net/p/pamsshagentauth/feature-requests/10/?limit=250#ed9b</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Should be closed as ecdsa and ed25519 keys are supported, right?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">sergio</dc:creator><pubDate>Sun, 16 Sep 2018 23:27:47 -0000</pubDate><guid>https://sourceforge.net644350e6de1925a73513510c2a264f841f1021be</guid></item><item><title>#8 suggestions from debian packaging</title><link>https://sourceforge.net/p/pamsshagentauth/feature-requests/8/?limit=25#0d1f</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Since this issue is still open, I guess it's as good a place as any to mention that the project is removed from testing and thus risk getting being dropped by Debian unless action is taken.&lt;/p&gt;
&lt;p&gt;Relevant links:  &lt;a class="" href="https://bugs.debian.org/859548" rel="nofollow"&gt;Please migrate to openssl1.1 in buster&lt;/a&gt;, &lt;a class="" href="https://packages.qa.debian.org/p/pam-ssh-agent-auth/news/20171130T043931Z.html" rel="nofollow"&gt;pam-ssh-agent-auth REMOVED from testing&lt;/a&gt;, &lt;a href="https://packages.debian.org/libpam-ssh-agent-auth" rel="nofollow"&gt;https://packages.debian.org/libpam-ssh-agent-auth&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Actually covering the possible migration to openssl 1.1 is likely a topic for a separate issue. However, a relevant question could be whether targeting the newer openssl version or completely replacing the package with the code from &lt;a class="" href="https://github.com/jbeverly/pam_ssh_agent_auth-2.0" rel="nofollow"&gt;pam_ssh_agent_auth-2.0&lt;/a&gt; is be the better path to take?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nospam5022</dc:creator><pubDate>Mon, 11 Jun 2018 17:43:08 -0000</pubDate><guid>https://sourceforge.net9d3013265614e7f6a1ba2fdcd3822a2a8600c7c4</guid></item><item><title>#8 suggestions from debian packaging</title><link>https://sourceforge.net/p/pamsshagentauth/feature-requests/8/?limit=25#25fd</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The project is now packaged in Debian, please file packaging related bugs/suggestions to Debian's BTS.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://tracker.debian.org/pkg/pam-ssh-agent-auth" rel="nofollow"&gt;https://tracker.debian.org/pkg/pam-ssh-agent-auth&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Balint Reczey</dc:creator><pubDate>Sun, 08 Jan 2017 19:05:07 -0000</pubDate><guid>https://sourceforge.net691cc581796434bcf8003c557c18e3554dd9b423</guid></item><item><title>#10 support ecdsa and ed25519 keys</title><link>https://sourceforge.net/p/pamsshagentauth/feature-requests/10/?limit=25#ee1a</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;As far as I know, what we do for Fedora is opensource and contribution to upstream projects is encouradged. So feel free to pick up what we have in &lt;a class="" href="http://pkgs.fedoraproject.org/cgit/rpms/openssh.git/tree/" rel="nofollow"&gt;dist-git&lt;/a&gt;. Or let me know if there is something unclear or anything I can do for you in this way.&lt;/p&gt;
&lt;p&gt;We build the &lt;code&gt;pam_ssh_agent_auth&lt;/code&gt; this way for years, but I did rebase to the current version of &lt;code&gt;pam_ssh_agent_auth&lt;/code&gt; just recently, which was basically only removing most of your prefixes and cheching that I don't miss any symbols and functionality against your sources.&lt;/p&gt;
&lt;p&gt;Moving to github would be great news since I really struggled with the SVN repository last time I had to dig up something from there.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jakub Jelen</dc:creator><pubDate>Fri, 25 Mar 2016 09:39:05 -0000</pubDate><guid>https://sourceforge.net4385193c5c45eca3c10671441e215bf6802ae47d</guid></item><item><title>#10 support ecdsa and ed25519 keys</title><link>https://sourceforge.net/p/pamsshagentauth/feature-requests/10/?limit=25#225d</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;@Jakub Any objections if I "borrow" that work. I have been porting to 7.2 myself to add certificate and the new curves. Had no idea fedora had done some of that work already. I plan on migrating source to github also, if that helps with future contributions.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jbeverly</dc:creator><pubDate>Thu, 24 Mar 2016 17:39:20 -0000</pubDate><guid>https://sourceforge.nete96673ec393b7dd77c5850cf49d41cbc3b0419f4</guid></item><item><title>#10 support ecdsa and ed25519 keys</title><link>https://sourceforge.net/p/pamsshagentauth/feature-requests/10/?limit=25#8fa3</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;@Jakub: I just built from the F23 sources, and it does indeed look a lot better. It'd still be great to upstream that work, though...&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">roguelazer</dc:creator><pubDate>Wed, 23 Mar 2016 00:02:26 -0000</pubDate><guid>https://sourceforge.net290b7c825576ef04420622cce1e8f55f588af75c</guid></item><item><title>#10 support ecdsa and ed25519 keys</title><link>https://sourceforge.net/p/pamsshagentauth/feature-requests/10/?limit=25#2473</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Check pam_ssh_avent_auth package in Fedora/RHEL/CentOS. We rebase to current openssh libraries (and build against them). It is sometimes painful if there are extensive refactorization, but these keys are supported natively.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jakub Jelen</dc:creator><pubDate>Tue, 15 Mar 2016 13:10:14 -0000</pubDate><guid>https://sourceforge.net6c43ff04c8d85721422582720bffaadee678119f</guid></item><item><title>support ecdsa and ed25519 keys</title><link>https://sourceforge.net/p/pamsshagentauth/feature-requests/10/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;OpenSSH 5.7 added support for ECDSA keys; OpenSSH 6.5 added support for Ed25519 keys. EC keys in general are quite convenient on constrained devices like mobile. The key-handling code in pam-ssh-agent-auth seems to predate them by a few years. What would it take to get support? It looks like &lt;code&gt;key.c&lt;/code&gt; and &lt;code&gt;key.h&lt;/code&gt; were pretty much copied wholesale from OpenSSH 5.1; is it just a matter of copying in &lt;code&gt;key.c&lt;/code&gt; and &lt;code&gt;key.h&lt;/code&gt; from a more modern release and renaming calls to &lt;code&gt;fatal()&lt;/code&gt; to &lt;code&gt;pamsshagentauth_fatal()&lt;/code&gt; instead?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">roguelazer</dc:creator><pubDate>Wed, 02 Mar 2016 21:34:27 -0000</pubDate><guid>https://sourceforge.net9ead0cec7068921824d0d3f68dd96bda35a39fb2</guid></item></channel></rss>