From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9P Cloud™
Date: Tue, 7 Jul 2015 15:11:01 -0700 [thread overview]
Message-ID: <adc649175e73a73fce11a7d7659785de@9netics.com> (raw)
In-Reply-To: <559C2818.1080406@ReliableID.com>
> Any prospects for certificate authentication as an alternative to oauth2?
yes; owing to 9P's design, authentication can be different. an early
version used authsrv. it is especially easy when there is a Go
package that implements the auth protocol. this is the case with
OAuth2 (it uses https://github.com/golang/oauth2)
-Skip
next prev parent reply other threads:[~2015-07-07 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 18:00 Skip Tavakkolian
2015-07-07 18:59 ` a.regenfuss at gmx.de
2015-07-07 19:27 ` Wes Kussmaul
2015-07-07 22:11 ` Skip Tavakkolian [this message]
2015-07-07 23:30 ` hiro
2015-07-08 0:53 ` Skip Tavakkolian
2015-07-08 1:05 ` hiro
2015-07-08 6:09 ` steve
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=adc649175e73a73fce11a7d7659785de@9netics.com \
--to=9nut@9netics.com \
--cc=9fans@9fans.net \
/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).