[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #50927] Invalid EFI file path for TFTP?
From: |
Kolbjørn Barmen |
Subject: |
[bug #50927] Invalid EFI file path for TFTP? |
Date: |
Wed, 3 May 2017 06:13:03 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/603.1.30 (KHTML, like Gecko) Version/10.1 Safari/603.1.30 |
URL:
<http://savannah.gnu.org/bugs/?50927>
Summary: Invalid EFI file path for TFTP?
Project: GNU GRUB
Submitted by: kolla
Submitted on: Wed May 3 10:13:02 2017
Category: Network
Severity: Major
Priority: 5 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release:
Release: 2.02~beta1
Reproducibility: None
Planned Release: None
_______________________________________________________
Details:
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.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50927>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #50927] Invalid EFI file path for TFTP?,
Kolbjørn Barmen <=