@patpat, see at that top of this page, the link that says:
auto-github-rhboot-shim #165
You can check the discussion there; I haven't tested any more recent
upstream binaries to see if they work now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is still unsolved.
where is "upstream" to politely request this fixed?
Even if shim is highly security sensitive it's TFTP requesting
the wrong server in a proxyDHCP environment.
thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The upstream bug is still unresolved, and shim is highly security
sensitive code. So we need to wait for an agreed upstream fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813541
Title:
Shim
Over 1 year and 2 Ubuntu versions later (one of them LTS) and this
problem is still not fixed. Even with googling this took me hours to
figure out today. :/
Please fix this finally.
I'd submit a patch, but I didn't write any C code, since I was around
21. If anything, I'd probably make things
** Changed in: shim (Ubuntu)
Status: New => Triaged
** Changed in: shim (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813541
Title:
Shim uses
** Changed in: shim
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813541
Title:
Shim uses wrong TFTP server IP in proxyDHCP mode
To manage notifications about this
** Bug watch added: github.com/rhboot/shim/issues #165
https://github.com/rhboot/shim/issues/165
** Also affects: shim via
https://github.com/rhboot/shim/issues/165
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Pseudocode for UEFI/BIOS firmwares:
If the DHCP server doesn't offer a boot filename,
and a proxyDHCP server is available,
then use the boot filename from the proxyDHCP offer,
and set TFTP=proxyDHCP.
Pseudocode for shim:
If UEFI reports that it used proxyDHCP, then use that one for the TFTP
*Actually you can use "boot filename = /path/to/shimx64.efi" just to
derive the /path/to/grubx64.efi if you want; but that's not very
important, just for TFTP directory organization.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The PXE specification, which also describes proxyDHCP, can be found for example
at:
http://www.pix.net/software/pxeboot/archive/pxespec.pdf
The "proof" that the proxyDHCP server should be used as the TFTP server,
is the fact that shimx64.efi was indeed downloaded by the UEFI firmware
from the
To be more clear (some times I'm not very confident about my English):
TFTP server = proxyDHCP server = where shimx64.efi is.
UEFI and BIOS and iPXE and all clients, use the proxyDHCP server as the TFTP
server.
Shimx64.efi on the other hand, tries to download grubx64.efi from the
real DHCP
By chance can you provide a reference to an RFC that explains the
"correct" interaction between proxy DHCP servers and DHCP boot file
option? Does the grub DHCP client implementation work the way you
describe?
** Changed in: shim (Ubuntu)
Status: New => Incomplete
--
You received this
Specifically, I think the issue is in
https://git.launchpad.net/ubuntu/+source/shim/tree/netboot.c#n293
memcpy(_addr.v4, pkt_v4->BootpSiAddr, 4);
There should be an "if proxy ... use that one for tftp ... else use
BootpSiAddr" at that point.
--
You received this bug notification because you
13 matches
Mail list logo
