Mike Saywell <[EMAIL PROTECTED]> wrote:
> Turns out the problem was not as Alan suspected. Seems that a return
> value got tweaked during a re-structuring of the code.
>
> Anyway here's the (very small) patch:
Added, thanks.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.fr
Mike Saywell <[EMAIL PROTECTED]> wrote:
> Turns out the problem was not as Alan suspected. Seems that a return
> value got tweaked during a re-structuring of the code.
Ah... that's probably my fault. Sorry.
> Anyway here's the (very small) patch:
The change results in the magic PEAP "succe
Hmm,
I guess Windows is just caching the details, I'm not sure though.
Infact that does seem to be the case:
See http://support.microsoft.com/default.aspx?scid=kb;en-us;828996
Article 823731 contains instructions on how to remove the cache, however
it sounds like you would have to do that every
Hello, Mike. Just a verification: So you replaced "rcode = RLM_MODULE_OK;"
with "rcode = RLM_MODULE_HANDLED;"? I tried that and the winxp supplicant
can indeed connect successfully. However, the user was not prompted for the
username and password on subsequent reboots and can still get access to
hi!
I would like to test your patch but I don't know where I must put it!
Should I have to create a file and put your patch inside? and the file
must be put in which directory?
thanks a lot!
renaud
> It took me a while to figure out what was going on here...
>
> Turns out the problem was not as A
5 matches
Mail list logo