[gPXE] Fwd: Re:Re: why?username and password is right , but can't boot?
Andrew Bobulsky
rulerof at gmail.com
Wed Mar 17 09:16:17 EDT 2010
Micheal, Kevin, et. al.,
I forwarded the this thread regarding this issue to a support rep I had previously consulted at Starwind Software. He's taking a look to confirm the issue of base64 support and I've asked if he can potentially offer a workaround. I'll post back when I hear from him again.
-Andrew Bobulsky
On Mar 17, 2010, at 6:51 AM, Michael Brown wrote:
> 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
> _______________________________________________
> gPXE mailing list
> gPXE at etherboot.org
> http://etherboot.org/mailman/listinfo/gpxe
More information about the gPXE
mailing list