GNU GRUB - Bugs: bug #50927, Invalid EFI file path for TFTP?
You are not allowed to post comments on this tracker with your current authentication level.
bug #50927: Invalid EFI file path for TFTP?
Submitter: | Kolbjørn Barmen <kolla> | ||
Submitted: | Wed 03 May 2017 10:13:02 AM UTC | ||
Category: | Network | Severity: | Major |
Priority: | 5 - Normal | Item Group: | None |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | |
Open/Closed: | Open | Release: | 2.02~beta1 |
Release: | Reproducibility: | None | |
Planned Release: | None |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-d3ae.
Corresponding source code
I try to use grub as general PXE solution for UEFI systems, but fint it impossible to chainload to efi files located on Windows TFTP servers, since they operate with back slashes in their paths instead of forward slashes.
For example:
set root(tftp,192.168.2.3)
chainloader smsboot\\x64\\wdsmgfw.efi
or
chainloader (tftp,192.168.2.3)smsboot\\x64\\wdsmgfw.efi
both result in "error: invalid EFI file path".
Manual "get smsboot\\x64\\wdsmgfw.efi " with any tftp client works.
Moving the file over to a *ix server and use backslash works, it will load the file.
In general, I think it is wrong to validate path strings on TFTP servers.