9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Ashwin Ganti" <ashwin.ganti@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] p9cr support in p9p's factotum?
Date: Wed,  5 Sep 2007 14:51:37 -0500	[thread overview]
Message-ID: <a67e66b20709051251o261531cbtc24cc350240f186e@mail.gmail.com> (raw)

Hello,

As part of a PAM module implementation in Linux I need to authenticate
against p9p's factotum. The code basically does an
"auth_userpasswd(user, passwd)" to achieve this. Apparently I get a
response from the factotum saying that it does not understand p9cr.

I noticed that in p9p's 'libauth' sources the auth_userpasswd
internally calls auth_challenge("user=%q proto=p9cr role=server",
user). When I grepped the sources I could not find p9cr implemented in
src/cmd/auth/factotum. Although I could notice a file "p9cr.c" which
seems to be a partial port as the code is not the same as that of its
Plan9 counterpart but looks more like the other p9p's code ( p9sk1.c
etc. ).

I was wondering if p9cr is supported in p9p's factotum. If yes then am
I missing something here? If not then is it on somebody's plate to
complete it? I am willing to complete it but I am a newbie in the
p9p's factotum's code and would appreciate any guidance/help from
someone who is aware of this stuff to help me get it done.

I would also like to know if there is any workaround for this like
using another protocol may be?

Any information would be very much useful.

Thanks and regards,
Ashwin Ganti

"Impossibility is a relative concept"
www.cs.uic.edu/~aganti


             reply	other threads:[~2007-09-05 19:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05 19:51 Ashwin Ganti [this message]
2007-09-06 16:02 ` Enrico Weigelt
2007-09-06 20:25   ` Lyndon Nerenberg
2007-09-14  1:16 ` Russ Cox
2007-09-15 12:09   ` erik quanstrom

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=a67e66b20709051251o261531cbtc24cc350240f186e@mail.gmail.com \
    --to=ashwin.ganti@gmail.com \
    --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).