<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: Re: Cipe for Windows
From: "Damion K. Wilson" <dkw,AT,rcm,DOT,bm>
Date: Wed, 18 Oct 2000 03:12:01 +0200
In-reply-to: <200010171247030374.00C02502@mail.sprint.ca>

You can look in the modules winsock.c and crypto.c. Beware though, I'm
rewriting the thing right now in C++ :-)

*********** REPLY SEPARATOR  ***********

On 10/17/00 at 6:11 PM chris wrote:

>Damion,
>
>Here is what I get between two Linux machines :
>
>KX: [NK_REQ] sending NK_IND E93E910E
>KX: [NK_IND] sending NK_ACK A93FC635
>KX: [NK_ACK] got  E93E910E
>
>So the ACK number matches the number sent under NK_IND
>and this is why the Linux CIPE keeps re-requesting a dynamic
>key when talking to the Win CIPE cause E93E910E would
>have ended up being 0000000E with only the last byte preserved.
>
>Where in your code does this get handled ? I'm about to dive into
>the source and start hacking :-)
>
>Chris
>
>
>
>
>
>
>*********** REPLY SEPARATOR  ***********
>
>On 10/17/00 at 6:07 PM Damion K. Wilson wrote:
>
>>I think so. The driver also takes the option cipe_debug or something like
>>that at load time. Look in the cipe.info documentation file.
>>
>>DKW
>>
>>*********** REPLY SEPARATOR  ***********
>>
>>On 10/17/00 at 4:44 PM chris wrote:
>>
>>>>Try two things: Setup another CIPE-Win32 instance and point it at the
>>first
>>>>and see if the same behaviour occurs. Turn on the logs in CIPE 1.4.2
and
>>>>see what causes it to initiate a key exchange.
>>>
>>>How do I do this ? In /etc/cipe/options ?
>>>
>>>
>>>Chris
>>>kohlhepp,AT,iosphere,DOT,net
>
>
>Chris
>kohlhepp,AT,iosphere,DOT,net





<< | Thread Index | >> ]    [ << | Date Index | >> ]