<DIV>Hi,</DIV>
<DIV> </DIV>
<DIV>Has advancement which the password starts can start how? How long wants to be possible probably to complete? <BR></DIV>
<DIV></DIV>
<P>lsq726</P>
<P>Regards <BR></P><PRE><BR>ÔÚ2010-03-18 05:12:39£¬"Marty Connor" <mdc@etherboot.org> дµÀ£º
>Michael Brown wrote on 3/17/10 6:51 AM:
>> On Wednesday 17 Mar 2010 10:08:00 Kevin Tran wrote:
>>> Current code only handles challenge response that is string of hex numbers
>>> that started with either ¡°0x¡±. The challenge sent back by this target is
>>> in base64 format. I think we need to add base64 (per RFC 3720) format
>>> support in order to solve this problem.
>>
>> Exactly what I was going to say. gPXE does not currently support base64-
>> encoded CHAP challenges (or responses).
>>
>> We have base64 encoding support in core/base64.c, but no decoding support.
>>
>> Someone will need to add base64_decode() base64_decoded_len() functions, and
>> modify iscsi.c to be able to use them; this is probably best done by
>> abstracting out the two places that currently process large hex strings into a
>> single iscsi_decode_large_binary() function.
>> Michael
>
>Cool. Thanks for outlining a solution.
>
>Sounds like a relatively easy change. Anyone want to take a crack at
>it? I think you will definitely have a willing tester for your work ;-)
>
>/ Marty /
>
>_______________________________________________
>gPXE mailing list
>gPXE@etherboot.org
>http://etherboot.org/mailman/listinfo/gpxe
</PRE><br><br><span title="neteasefooter"/></span>