[Bug 281740] [stand/cd9660] Paths including "." or ".." are not resolved

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281740

--- Comment #1 from Luc Techer <luc.techer64@gmail.com> ---
As a workaround I tried generating a manifest in each directory so as to avoid
the parent directory resolution, but the now the device ID from the manifest
and the file which is being verified do not match. I can't help to notice that
whilst loader.lua and manifest do not share the same device ID, they have the
same inode number ! As I am not too familiar with how the cd9660 filesystem
works, is any of this to be expected ?

Here are the new boot logs:

```
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
is_verified: dev=1073517184,ino=1040206231,status=-42
verify_signed: /boot/lua/manifest.rsig
verify_sig: /boot/lua/manifest.rsig
verify_signer: 1 certs in chain
verify_signer: 1 trust anchors
Verified /boot/lua/manifest signed by TEST
inserted 9 /boot/lua at head
add_verify_status: dev=1073517184,ino=1040206231,status=1
loaded: /boot/lua/manifest (null) (null)
looking for /boot/lua 9 loader.lua
at 9 /boot/lua
skipping dev=1073517184 != -1
looking for /boot 5 lua/loader.lua
at 9 /boot/lua
Ignoring prefix=/boot/lua
looking for / 1 boot/lua/loader.lua
at 9 /boot/lua
Ignoring prefix=/boot/lua
Unverified /boot/lua/loader.lua: no entry
add_verify_status: dev=1073517472,ino=1040206231,status=-2
ERROR: cannot open /boot/lua/loader.lua: no error.
```

-- 
You are receiving this mail because:
You are the assignee for the bug.