From: Boky Gmail <verynotbad@gmail.com>
To: linux-ppp@vger.kernel.org
Subject: Authentificating with certificates ("unknown authentication type 13; Naking")
Date: Wed, 27 Jul 2005 21:26:06 +0000 [thread overview]
Message-ID: <e8666cf9050727142635284b29@mail.gmail.com> (raw)
Hi all.
I was wondering if it is possible to use certificates instead of
passwords for authentification over PPTP?
Google turned up nothing usefull.
When logging the connection this is what PPP says("pppd call work
logfd 1 nodetach debug dump"):
---snip---
rcvd [LCP EchoRep id=0x0 magic=0x110e4d94]
rcvd [EAP Request id=0x12 TLS 20]
EAP: unknown authentication type 13; Naking
sent [EAP Response id=0x12 Nak <Suggested-type 13>]
rcvd [LCP TermReq id=0x4 11 0e 4d 94 00 3c cd 74 00 00 02 b3]
LCP terminated by peer (^Q^NMM-^T^@<M-Mt^@^@^BM-3)
sent [LCP TermAck id=0x4]
Terminating on signal 2.
---snip---
Now, I know for a fact that our administrator has certificate-only VPN
login policy in place.
I am suspecting that "EAP: unknown authentication type 13; Naking"
means that the server requested certificate-based authentification but
the client does not have any implementation to handle this and
therefor the conection terminated.
Is my hunch correct?
If it is, will certificate authentification be ever possible? If so,
is there an ETA? A feature-request, perhaps?
If no, can someone please explain to me how to enable authentification
by certificate?
PS: This question was first posted to the pptpclient-dev mailing list
and I was told it is a PPP issue.
Sniplets (reply by James Cameron):
--snip--
It has nothing to do with PPTP, because at the stage that
this happens only pppd has anything to do with the task. Ask the PPP
mailing list.
--snip--
He also suggested looking here:
http://marc.theaimsgroup.com/?l=linux-ppp&m\x112177308427341&w=2
But that did not help, either.
Thank you all,
Bojan
next reply other threads:[~2005-07-27 21:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 21:26 Boky Gmail [this message]
2005-07-28 17:00 ` Authentificating with certificates ("unknown authentication type 13; Naking") Boky Gmail
2005-07-28 17:33 ` James Carlson
2005-07-28 17:40 ` Boky Gmail
2005-10-20 10:42 ` Authentificating with certificates ("unknown authentication type Jan Just Keijser
2005-10-20 10:56 ` Authentificating with certificates ("unknown authentication type 13; Naking") Boky Gmail
2005-10-20 11:42 ` Authentificating with certificates ("unknown authentication type Jan Just Keijser
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=e8666cf9050727142635284b29@mail.gmail.com \
--to=verynotbad@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 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).