From: quanstro@quanstro.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dsa keys.
Date: Sat, 11 Mar 2006 19:43:22 -0600 [thread overview]
Message-ID: <8ff8dae0ae840c59fec4de80d69a55c7@quanstro.net> (raw)
In-Reply-To: <20060312003429.GA39633@mero.morphisms.net>
true enough. but this can become chicken-and-egg logic.
as in: ssh doesn't support dsa because auth doesn't support dsa.
i thought that getting auth to support dsa keys would be a good start
on ssh support.
- erik
On Sat Mar 11 18:36:30 CST 2006, jkw@eecs.harvard.edu wrote:
> On Sat, Mar 11, 2006 at 07:20:19PM -0600, quanstro@quanstro.net wrote:
> > these days many places require dsa ssh keys.
>
> As Russ said:
>
> They don't exist in Plan 9 only because we don't have
> anything that actually uses dsa keys.
next prev parent reply other threads:[~2006-03-12 1:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 1:00 quanstro
2006-03-12 0:17 ` Russ Cox
2006-03-12 1:20 ` quanstro
2006-03-12 0:34 ` William Josephson
2006-03-12 1:43 ` quanstro [this message]
2006-03-12 1:02 ` Russ Cox
2006-03-12 2:07 ` quanstro
2006-03-12 1:03 ` William Josephson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8ff8dae0ae840c59fec4de80d69a55c7@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).