https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281740
Bug ID: 281740
Summary: [stand/cd9660] Paths including "." or ".." are not
resolved
Product: Base System
Version: 14.1-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: luc.teche...@gmail.com
I came across a weird behaviour when trying to boot on an ISO image with the
LOADER_VERIEXEC option enabled, the manifest cannot be located from a
subdirectory. Using "ls" from the loader console, it seems like /boot/lua is
indeed a directory and not a link. Trying to access other parent directories
using ".." does not work either, neither does the "." to refer to the current
directory. Is this expected behaviour on the libstand implementation of the
cd9660 filesystem ?
```
Set ve_utc=1546329600
Set ve_utc=1727425532
Self tests...
Testing hash sha256 PASSED
verify_signer: 1 certs in chain
verify_signer: 1 trust anchors
Testing verify certificate: TEST PASSED
verify_prep:
caller=fopen,fd=1,name='/boot/lua/loader.lua',off=0,dev=1073517472,
ino=1040206231
is_verified: dev=1073517472,ino=1040206231,status=-42
looking for /boot/lua/manifest
looking for /boot/lua/../manifest
ERROR: cannot open /boot/lua/loader.lua: no such file or directory
Type '?' for a list of commands, 'help' for more detailed help.
OK ls /boot/manifest
/boot/manifest
OK ls /boot/lua/../manifest
open '/boot/lua/../manifest' failed: no such file or directory
OK ls -l /boot/
/boot
...
d 2048 kernel
d 4096 lua
7372 manifest
2053 manifest.rcerts
761 manifest.rsig
...
OK ls /sbin
/sbin
adjkerntz
bsdlabel
...
OK ls /sbin/..
open '/sbin/..' failed: no such file or directory
OK ls /.
open '/.' failed: no such file or directory
```
Here are the src.conf options related to VERIEXEC as they are compiled on my
image:
WITH_BEARSSL=YES
WITH_LOADER_VERIEXEC=YES
WITH_LOADER_VERIEXEC_VECTX=YES
WITHOUT_LOADER_EFI_SECUREBOOT=YES
WITHOUT_VERIEXEC=YES
--
You are receiving this mail because:
You are the assignee for the bug.
