On Tue, Feb 9, 2010 at 6:43 AM, Joshua Oreman <span dir="ltr"><<a href="mailto:oremanj@rwcr.net">oremanj@rwcr.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Tue, Feb 9, 2010 at 9:40 AM, Luca <<a href="mailto:lucarx76@gmail.com">lucarx76@gmail.com</a>> wrote:<br>
> So if I got it right, I would keep using the same gPXE image and I would<br>
> just change the gpxe script at every boot.<br>
><br>
> Problem is that script is generated by a central entity just before a<br>
> workstation is gPXE booted so I can't store the script on the workstation, I<br>
> need gPXE to contact a remote server and get it.<br>
<br>
</div>gPXE also supports loading boot scripts over the network, and it can<br>
download files over HTTPS if you enable that in config/general.h.<br>
Would that be sufficient for your purposes?<br>
<br>
-- Josh<br>
</blockquote></div><br>Hi Josh, thanks for replying.<br><br>I thought about the solution you proposed. But in my case it's kind of chicken-egg problem. I could definitely use HTTPS to get the file. But one of the parameter I need in gPXE is the server certificate so gPXE can be sure it's talking to the right HTTPS server. <br>