From: Greg <gregborbonus@gmail.com>
To: linux-ppp@vger.kernel.org
Subject: PPPD plugin development
Date: Mon, 10 Mar 2014 12:31:14 +0000 [thread overview]
Message-ID: <531DB092.3040404@gmail.com> (raw)
In-Reply-To: <531BEBF2.3020508@gmail.com>
hey guys,
as stated before, I'm trying to write a plugin to authenticate against
an external script. So far, I've only managed to get it to write a bit
information to a log file on the server.
I'm trying to use the digest->code to determine the type of digest used.
I figured that if I can find out which type it's using then I could then
move forward with converting it or determining how to store the
encrypted password to do a comparison.
I've also made it return 1 so that no matter what I enter, it should
show authenticated.
digest->code writes as blank.
When using it as a switch->case scenario, it goes to default:
switch (digest->code) {
case CHAP_MICROSOFT:
{
codemess = "MIC";
}
case CHAP_MICROSOFT_V2:
{
codemess = "MV2";
}
default:
codemess = "Default";
}
The return 1 appears to work, but then I get the message:
MPPE required, but keys are not available. Possible plugin problem?
I REALLY wish this was a documented better. Though I code in other
scripting languages, C is not something I'm used to coding. So please
feel free to give me a hard time, I'm muddling my way through C just to
get the basics right.
--
Thank you,
Greg Borbonus
*Nix Server administrator
next prev parent reply other threads:[~2014-03-10 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 4:20 pppd plugin development Greg
2014-03-09 14:14 ` Greg
2014-03-10 12:31 ` Greg [this message]
2014-03-10 14:01 ` PPPD " James Carlson
2014-03-10 14:23 ` Greg
2014-03-10 15:14 ` James Carlson
2014-03-11 4:56 ` Greg
2014-03-11 9:55 ` Greg
2014-03-11 16:56 ` James Carlson
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=531DB092.3040404@gmail.com \
--to=gregborbonus@gmail.com \
--cc=linux-ppp@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.