Re: Vendor specific authentication protocol
- From: Unruh <unruh-spam@xxxxxxxxxxxxxx>
- Date: 25 Jul 2005 03:05:34 GMT
"GREG" <gsauseng@xxxxxxxxx> writes:
>Unruh schrieb:
>> "GREG" <gsauseng@xxxxxxxxx> writes:
>>
>> >Thank you for your answer!
>> >What want to do is exchange data in some way befor the authentication
>> >phase of ppp takes place. As I read about this vendor specific
>>
>> What kind of data?
>Well it is just text.
Why would you want to exchange text before the authentication phase rather
than afterwards. what will the machines do with that text? ppp
negotiationis a very specific set of negotiations, in which both sides have
to understand what is being negotiatiate. You can of course send anything
you want but that is useless if the other side does not understand what it
is.
You can hack ppp but then on windows you do not have source code so you
cannot. If you told us what it was you wre trying to accomplish, we might
be able to show how you could accompish that. Somehow" sending a message to
the remote machine which is trown away by that machine" does not sound like
what you actually want to accomplish.
>>
>> >authentication and the LCP Frame types which allow an additional amount
>> >of data to be included in the Data field whose use is not strictly
>> >described by the protocol i thought this could be a solution to my
>> >problem. But it seems to be quite dificult. Now I am thinking about
>>
>> No.
No, it is not a solution to your problem because both systems have to
understand what is being communicated and what is to be done with that
data. So let us say you hack machine A to send the data. What is B to do
with that data? It has no idea what this LCP frame is all about since the
writter of software had never heard about the use you want to put it to,
>What did you mean, by saying no? I don't understand...
>>
>> >using these .scp dial up scripts which are used for automatical login.
>>
>> What are ".scp dialup scripts"? if you mean chat type dialup scripts, then
>> they are well described in man chat
>Yes that scripts. What the chat script for linux are the .scp scripts
>for windows i would say. It's just for automatically authenticate with
Ah, yes, I only realised after you wrote thta .scp is probably a windows
thing, which makes your project even harder since you have no access to the
software. But I am certainly the wrong person to comment on what you can
with the windows script. Now,m you could use the authentication ( username,
password) to convey messages, but you would have to have much beter control
of one or the other sides to do that. Ie, if one side was a Linux machine
it could ask in the preliminary scripty for authentication and use what was
sent over the username and/of password to make decisions. That is of course
not part of ppp. It would happen before ppp ever got started on either
side.
But without a more detailed description of what you want to do, of why you
want to exchange this data, noone is going to be able to help you.
>username and password used in windows. I read the man page for chat and
>chat can do more than i can do with an .scp script. chat offers a
>option -E, and with that it is possible to use an environment variable
>$xxx, i don't find that possibility with .scp scripts. So from my point
>of view, i can transmit anything written in an environment variable
>with a chat script, by using the -E option. This is something i can't
>do with .scp scripts, there i can only use a few system variables
>($userid,$password,$success,$Failure) and no other. i can transmit
>strings but i can not use any other variables.
.
- References:
- Vendor specific authentication protocol
- From: GREG
- Re: Vendor specific authentication protocol
- From: James Carlson
- Re: Vendor specific authentication protocol
- From: GREG
- Re: Vendor specific authentication protocol
- From: Patrick Klos
- Re: Vendor specific authentication protocol
- From: GREG
- Re: Vendor specific authentication protocol
- From: Unruh
- Re: Vendor specific authentication protocol
- From: GREG
- Vendor specific authentication protocol
- Prev by Date: Re: Vendor specific authentication protocol
- Next by Date: remote IP address not being sent
- Previous by thread: Re: Vendor specific authentication protocol
- Next by thread: Re: Vendor specific authentication protocol
- Index(es):
Relevant Pages
|