James Carlson | 2 Jan 18:44

Re: Using an NTS instead of the local serial device ?

Paul Mackerras writes:
> wotuzu17 writes:
> 
> > If there was a -socket option, I'd like to try. But I can't find a -socket
> > option neither in the man pages nor in other documentation about pppd. 
> > 
> > # pppd: unrecognized option '-socket'
> 
> Sorry, it's "socket" (no dash) and it takes an argument which is
> host:port.  However, if the Lantronix really does the telnet protocol
> then it won't work properly since telnet interprets the 0xff character
> and CR (0x0d) characters specially.

Lantronix devices support both.  You connect to 2000+n to get TELNET
protocol (with the 0xff escapes), and 3000+n for a raw TCP connection.

So, for port 1, use this in pppd:

	socket ip-address:3001

(Most other terminal servers have similar features.  For example, the
equivalent ranges on Annexes are 5000+n for TELNET and 7000+n for raw
TCP.)

I would advise the original poster to avoid reverse telnet.  It may
work with some applications, but it's a frightening bit of hackery
that (at least in my experience) often fails in strange ways.

--

-- 
James Carlson         42.703N 71.076W         <carlsonj <at> workingcode.com>
(Continue reading)

Holger Eitzenberger | 10 Jan 18:08

pppd patches

Hi,

while searching for some PPP net_device recounting bug and PPPoE I
noticed that there are some bugs in pppd.

Is this list the correct place to post them?

Thanks.

  /holger

-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

James Carlson | 11 Jan 00:21

Re: pppd patches

Holger Eitzenberger writes:
> while searching for some PPP net_device recounting bug and PPPoE I
> noticed that there are some bugs in pppd.
> 
> Is this list the correct place to post them?

If it's specifically related to the code that supports PPP on Linux,
then yes.  If it's related to the portable ``pppd'' implementation
that works on many different platforms, then I'd suggest sending mail
to ppp-bugs <at> dp.samba.org instead.

(Many of us are on both lists even if we don't use Linux ...)

--

-- 
James Carlson         42.703N 71.076W         <carlsonj <at> workingcode.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

James Carlson | 11 Jan 14:26

Re: pppd patches

gaurav chowdhary writes:
>   Greetings!, I am new to this mail group, just wanted to know where I can find the trimmed version of pppd as we
have an stringent memory requirement for the same.

I know of several groups that have done this for commercial ventures,
but none that's made its work public.  Sorry.

--

-- 
James Carlson         42.703N 71.076W         <carlsonj <at> workingcode.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Charlie Brady | 11 Jan 18:11
Picon
Picon

Re: pppd patches


On Fri, 11 Jan 2008, James Carlson wrote:

> gaurav chowdhary writes:
>>   Greetings!, I am new to this mail group, just wanted to know where I can find the trimmed version of pppd as
we have an stringent memory requirement for the same.
>
> I know of several groups that have done this for commercial ventures,
> but none that's made its work public.  Sorry.

Let's all celebrate the true "freedom" which the BSD license furnishes! :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Nestor Urquiza | 20 Jan 17:48
Picon

RSA SecureId (RFC 4793) support

Hi guys,
I just wanted to understand if you have any plan to give support for
RSA SecureId (EAP-POTP) which corresponds to EAP type 15.

The specifications are publicly available as you see from IETF RFC
4793 ... The EAP Protected One-Time Password Protocol (EAP-POTP).

I posted some months ago a question asking for support at pptp mailing
list since by that time I had no idea about PPP and EAP and I was
guessing RSA SecureId authentication was something related to PPTP.

After some further reading I realized that the specs are publicly
available and someone has patched pppd to support EAP-TLS.  I guess
supporting EAP-POTP shouldn't be that hard since EAP-TLS and EAP-POTP
are just different types from the same rfc 3748.

Thanks in advance,

-Nestor
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Nestor Urquiza | 20 Jan 17:54
Picon

Re: RSA SecurId (RFC 4793) support

subject typo corrected...

On Jan 20, 2008 11:48 AM, Nestor Urquiza <nestor.urquiza <at> gmail.com> wrote:
> Hi guys,
> I just wanted to understand if you have any plan to give support for
> RSA SecurId (EAP-POTP) which corresponds to EAP type 15.
>
> The specifications are publicly available as you see from IETF RFC
> 4793 ... The EAP Protected One-Time Password Protocol (EAP-POTP).
>
> I posted some months ago a question asking for support at pptp mailing
> list since by that time I had no idea about PPP and EAP and I was
> guessing RSA SecurId authentication was something related to PPTP.
>
> After some further reading I realized that the specs are publicly
> available and someone has patched pppd to support EAP-TLS.  I guess
> supporting EAP-POTP shouldn't be that hard since EAP-TLS and EAP-POTP
> are just different types from the same rfc 3748.
>
> Thanks in advance,
>
> -Nestor
>
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Charlie Brady | 20 Jan 19:34
Picon
Picon

Re: RSA SecureId (RFC 4793) support


On Sun, 20 Jan 2008, Nestor Urquiza wrote:

> I guess supporting EAP-POTP shouldn't be that hard since EAP-TLS and 
> EAP-POTP are just different types from the same rfc 3748.

It's "not hard" compared to hard problems. But it's also a non-trivial 
amount of work. I wouldn't expect to see an implementation soon unless I 
was paying someone to make it.
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Bill Unruh | 20 Jan 21:23
Picon
Picon
Favicon

Re: RSA SecureId (RFC 4793) support

On Sun, 20 Jan 2008, Charlie Brady wrote:

>
> On Sun, 20 Jan 2008, Nestor Urquiza wrote:
>
>>  I guess supporting EAP-POTP shouldn't be that hard since EAP-TLS and
>>  EAP-POTP are just different types from the same rfc 3748.
>
> It's "not hard" compared to hard problems. But it's also a non-trivial amount 
> of work. I wouldn't expect to see an implementation soon unless I was paying 
> someone to make it.

Course the person to ask would be Carlson, since he implimented the EAP-SRP
into pppd.
Actually, pppd (2.4.4) does not seem to support TLS. Also EAP is just an
extention, so there need be no relation between the various ways the
various EAP  authentications do things.

pppd lists various types of EAP.
"Identity", "Notification", "Nak", "MD5-Challenge",
    "OTP", "Generic-Token", NULL, NULL,
    "RSA", "DSS", "KEA", "KEA-Validate",
    "TLS", "Defender", "Windows 2000", "Arcot",
    "Cisco", "Nokia", "SRP"

Of which probably only MD5 and SRP are actually implimented in pppd it
looks like to me.

-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
(Continue reading)

Nestor Urquiza | 21 Jan 14:35
Picon

Re: RSA SecureId (RFC 4793) support

Apparently there was a patch for EAP-TLS:
http://marc.info/?l=pptpclient-devel&m=119191642811483&w=2
According to what I see the current ppp just responds NACK when it
receives EAP type 15.

Thanks!

-Nestor

On Jan 20, 2008 3:23 PM, Bill Unruh <unruh <at> physics.ubc.ca> wrote:
>
> On Sun, 20 Jan 2008, Charlie Brady wrote:
>
> >
> > On Sun, 20 Jan 2008, Nestor Urquiza wrote:
> >
> >>  I guess supporting EAP-POTP shouldn't be that hard since EAP-TLS and
> >>  EAP-POTP are just different types from the same rfc 3748.
> >
> > It's "not hard" compared to hard problems. But it's also a non-trivial amount
> > of work. I wouldn't expect to see an implementation soon unless I was paying
> > someone to make it.
>
> Course the person to ask would be Carlson, since he implimented the EAP-SRP
> into pppd.
> Actually, pppd (2.4.4) does not seem to support TLS. Also EAP is just an
> extention, so there need be no relation between the various ways the
> various EAP  authentications do things.
>
> pppd lists various types of EAP.
(Continue reading)


Gmane