Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Bug in xbps-create when a relative symlink point to an absolute symlink

Offen
#435 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
38/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
c
Bereich
cli, tooling

Rechercherichtung

Start by running the supplied reproduction script and inspect xbps-create's symlink handling around readlink and realpath. Compare the generated files.plist with the package contents, then verify that the corrected metadata lets xbps-remove remove both symlinks without truncating the target path.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug

Simple script to reproduce

#! /bin/sh

set -e

PKGVER=bug-1_1
ARCH=x86_64
DESC="Package to show a bug in xbps-create"

DESTDIR=/tmp/bug-1

mkdir -p $DESTDIR/etc/A
ln -s /etc/os-release $DESTDIR/etc/abs
ln -s ../abs $DESTDIR/etc/A/rel

xbps-create --arch "$ARCH" --desc "$DESC" --pkgver "$PKGVER" $DESTDIR

After running this script you'll end up with a badly formed package. Contents are ok:

$ tar tvf bug-1_1.x86_64.xbps
-rw-r--r-- root/root       503 1969-12-31 21:00 ./props.plist
-rw-r--r-- root/root       744 1969-12-31 21:00 ./files.plist
lrwxrwxrwx 0/0               0 2021-11-28 20:06 ./etc/abs -> /etc/os-release
lrwxrwxrwx 0/0               0 2021-11-28 20:06 ./etc/A/rel -> ../abs

But files.plist is wrong:

$ tar xOf bug-1_1.x86_64.xbps ./files.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>dirs</key>
	<array>
		<dict>
			<key>file</key>
			<string>/etc</string>
		</dict>
		<dict>
			<key>file</key>
			<string>/etc/A</string>
		</dict>
	</array>
	<key>links</key>
	<array>
		<dict>
			<key>file</key>
			<string>/etc/A/rel</string>
			<key>mtime</key>
			<integer>1638140801</integer>
			<key>target</key>
			<string>lease</string>
		</dict>
		<dict>
			<key>file</key>
			<string>/etc/abs</string>
			<key>mtime</key>
			<integer>1638140801</integer>
			<key>target</key>
			<string>/etc/os-release</string>
		</dict>
	</array>
</dict>
</plist>

What is going on I think is:

  • the file in destdir /etc/A/rel is a symlink and readlink gives ../abs which is understood to be relative since it starts with .
  • the filename is then canonicalized (using realpath) to /etc/os-release
  • since the symlink was thought to be relative, this is expected to be inside destdir
  • hence we drop the destdir prefix /tmp/bug-1, that's 10 characters so /etc/os-release minus 10 characters gives lease

This actually bit us in the wip sagemath package. The net result is that those symlinks that are badly reported in files.plistare not removed by xbps-remove.

I've since made a workaround in the sagemath package so this won't affect us, but it'd be nice to fix this logic (whiich is kind of hard to understand), at the very least check that the prefix for the link is indeed the destdir before droping it naively and complain if not.

All of this is affected by whether the canonicalized path is actually an existing file; that's why I chose /etc/os-release which should always exist (if this file is not there, the bug doesn't trigger).

Vorherrschende Sprache
C
Sterne
1.2k
Forks
152
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus void-linux/xbps

Alle Issues in void-linux/xbps

Ähnliche Issues

Weitere Issues zu C

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.