Parabola Issue Tracker: Issueshttps://labs.parabola.nu/https://labs.parabola.nu/favicon.ico?15367742552024-02-16T01:30:49ZParabola Issue Tracker
Redmine Packages - Bug #3584 (forwarded upstream): armv7h packages fail to install - signing key is "unkn...https://labs.parabola.nu/issues/35842024-02-16T01:30:49ZGNUtooGNUtoo@cyberdimension.org
<p>In <a class="external" href="https://repo.parabola.nu/sources/parabola/">https://repo.parabola.nu/sources/parabola/</a> there is no archlinuxarm-keyring-20140119.tar.gz, though there are other packages in libre like hyperbola-keyring.</p>
<p>Unfortunately that source file is not upstream anymore either and Arch Linux ARM doesn't seem to have upgraded its keyring.</p>
<p>So I don't know what to do here.</p> Packages - Bug #3561 (info needed): wp-cli not built from source (but source code is provided)https://labs.parabola.nu/issues/35612023-12-26T11:59:52ZGNUtooGNUtoo@cyberdimension.org
<p>The pkp-cli recipe consists in the following:</p>
<pre>
build() {
cd "$_archive"
composer install --no-interaction --prefer-dist --no-scripts
php -dphar.readonly=0 utils/make-phar.php wp-cli.phar
}
</pre>
<p>After installing php-cli I can get the source code in this way:</p>
<pre>
# cd $(mktemp -d)
# phar extract -f /usr/bin/wp
# find > wp-cli-files.txt
</pre>
<p>wp-cli-files.txt is attached</p>
<p>I've looked at a random file (usr/bin/wp/vendor/wp-cli/wp-config-transformer/src/WPConfigTransformer.php) and the source code is perfectly readable so it does not look transformed in any way.</p>
<p>It is possible to build wp-cli from source, and there is a tutorial for that here: <a class="external" href="https://make.wordpress.org/cli/handbook/contributions/pull-requests/#setting-up">https://make.wordpress.org/cli/handbook/contributions/pull-requests/#setting-up</a></p>
<p>Do we need to remove wp-cli because it's not built from source or is the fact that it provide source code sufficient?</p> Packages - Bug #3470 (confirmed): arduino: Has a package managerhttps://labs.parabola.nu/issues/34702023-04-15T13:49:16ZGNUtooGNUtoo@cyberdimension.org
<p>The package manager is available in "Tools" -> "Board: [...]" -> "Boards Manager".</p>
<p>I've no idea of it's policies, so we need to look if the repository is fully free software. If it's fully free it might be OK FSDG wise.</p>
<p>I've also added an entry in the Libreplanet Wiki about it: <a class="external" href="https://libreplanet.org/wiki/Group:Software/research/ExternalRepositories">https://libreplanet.org/wiki/Group:Software/research/ExternalRepositories</a></p> Packages - Bug #3469 (confirmed): arduino-avr-core contain binaries (but also their source code)https://labs.parabola.nu/issues/34692023-04-15T13:39:22ZGNUtooGNUtoo@cyberdimension.org
<p>The arduino package isn't useful alone: it needs some extra software to support specific microcontroller boards.</p>
So I know two options so far:
<ul>
<li>Use the builtin package manager to install code to support these boards</li>
<li>Use the Arch Linux / Parabola packages for that</li>
</ul>
<p>The advantage of the later is that it is patched to use Arch Linux packages like avrdude. In contrast the arduino-avr-code installed through the Arduino package manager pulls an avrdude binary for instance (and it more limited than the one build by Arch Linux).</p>
The Arch Linux packaged arduino-avr-core consist of source code that is copied as-is, but it also contains the following bootloaders binaries:
<ul>
<li>Arduino-COMBINED-dfu-usbserial-atmega16u2-Mega2560-Rev3.hex</li>
<li>Arduino-COMBINED-dfu-usbserial-atmega16u2-MegaADK-Rev3.hex</li>
<li>Arduino-COMBINED-dfu-usbserial-atmega16u2-Uno-Rev3.hex</li>
<li>Arduino-usbserial-atmega16u2-Mega2560-Rev3.hex</li>
<li>Arduino-usbserial-atmega16u2-MegaADK-Rev3.hex</li>
<li>Arduino-usbserial-atmega16u2-Uno-Rev3.hex</li>
<li>Arduino-usbserial-mega.hex</li>
<li>Arduino-usbserial-uno.hex</li>
<li>ATmegaBOOT_168_atmega1280.hex</li>
<li>ATmegaBOOT_168_atmega328_bt.hex</li>
<li>ATmegaBOOT_168_atmega328.hex</li>
<li>ATmegaBOOT_168_atmega328_pro_8MHz.hex</li>
<li>ATmegaBOOT_168_diecimila.hex</li>
<li>ATmegaBOOT_168.hex</li>
<li>ATmegaBOOT_168_ng.hex</li>
<li>ATmegaBOOT_168_pro_8MHz.hex</li>
<li>ATmegaBOOT.hex</li>
<li>ATmegaBOOT-prod-firmware-2009-11-07.hex</li>
<li>Caterina-Circuitplay32u4.hex</li>
<li>Caterina-Esplora.hex</li>
<li>Caterina-Industrial101.hex</li>
<li>Caterina-LeonardoEthernet.hex</li>
<li>Caterina-Leonardo.hex</li>
<li>Caterina-LilyPadUSB.hex</li>
<li>Caterina-LininoOne.hex</li>
<li>Caterina-Micro.hex</li>
<li>Caterina-Robot-Control.hex</li>
<li>Caterina-Robot-Motor.hex</li>
<li>Caterina-Yun.hex</li>
<li>Caterina-YunMini.hex</li>
<li>Caterina-Yun-noblink.hex</li>
<li>Esplora-prod-firmware-2012-12-10.hex</li>
<li>gemma_v1.hex</li>
<li>Genuino-COMBINED-dfu-usbserial-atmega16u2-Mega2560-R3.hex</li>
<li>Genuino-COMBINED-dfu-usbserial-atmega16u2-Uno-R3.hex</li>
<li>Genuino-usbserial-atmega16u2-Mega2560-R3.hex</li>
<li>Genuino-usbserial-atmega16u2-Uno-R3.hex</li>
<li>Leonardo-prod-firmware-2012-04-26.hex</li>
<li>Leonardo-prod-firmware-2012-12-10.hex</li>
<li>LilyPadBOOT_168.hex</li>
<li>Mega2560-prod-firmware-2011-06-29.hex</li>
<li>MEGA-dfu_and_usbserial_combined.hex</li>
<li>Micro-prod-firmware-2012-11-23.hex</li>
<li>Micro-prod-firmware-2012-12-10.hex</li>
<li>optiboot_atmega168.hex</li>
<li>optiboot_atmega328.hex</li>
<li>optiboot_atmega328-Mini.hex</li>
<li>optiboot_atmega8.hex</li>
<li>stk500boot_v2_mega2560.hex</li>
<li>UNO-dfu_and_usbserial_combined.hex</li>
<li>wifi_dnld.hex</li>
<li>wifiHD.hex</li>
</ul>
<p>It doesn't seem to contain avrdude.</p>
<p>As the source code is also provided it's probably OK FSDG wise as long as the binaries match the source code. However there is a Parabola policy that requires to have everything built from source in the packages.</p>
So we have 2 options here that aren't mutually exclusive:
<ul>
<li>Remove all these bootloaders binaries (With rm -f)</li>
<li>Compile the bootloaders from source and replace the old binaries with the ones built.</li>
</ul>
<p>The bootloaders are also not needed for normal operation of the arduino program: they are just used to recover boards when the users erased the bootloader. So simply removing them will probably only break that functionality.</p> Packages - Bug #3451 (fixed): community/bass lacking source codehttps://labs.parabola.nu/issues/34512023-03-08T23:19:21ZGNUtooGNUtoo@cyberdimension.org
<p>The <a href="https://downloads.sourceforge.net/scummvm/bass-cd-1.2.zip" class="external">source code zip</a> has the following files:<br /><pre>
bass-cd-1.2/sky.dnr
bass-cd-1.2/sky.dsk
bass-cd-1.2/readme.txt
bass-cd-1.2/sky.cpt
</pre></p>
<p>And the license is the following (from readme.txt):<br /><pre>
1) You may distribute this game for free on any medium, provided this readme
and all associated copyright notices and disclaimers are left intact.
2) You may charge a reasonable copying fee for this archive, and may distribute
it in aggregate as part of a larger & possibly commercial software distribution
(such as a Linux distribution or magazine coverdisk). You must provide proper
attribution and ensure this readme and all associated copyright notices, and
disclaimers are left intact.
3) You may not charge a fee for the game itself. This includes reselling the
game as an individual item.
4) You may modify the game as you wish. You may also distribute modified
versions under the terms set forth in this license, but with the additional
requirement that the work is marked with a prominent notice which states that
it is a modified version.
5) All game content is (C) Revolution Software Ltd. The ScummVM engine is (C)
The ScummVM Team (www.scummvm.org)
6) THE GAMEDATA IN THIS ARCHIVE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING AND NOT LIMITED TO ANY IMPLIED WARRANTIES OF
MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
</pre></p>
<p>The same readme.txt has:<br /><pre>
Some time ago, we (ScummVM) had the good fortune to come in contact with Tony
Warriner at Revolution Software Ltd. With their blessing and support, we then
obtained the original source code for Beneath a Steel Sky and added support for
it to our adventure game interpreter, ScummVM. And now, on the eve of ScummVM
0.5.0 (the first release featuring B.A.S.S support), Revolution Software Ltd.
has decided to release Sky to the public as freeware!
</pre></p>
<p>So that is probably OK FSDG wise as this data could be considered as non-functionnal and that we get permissions to redisrtibute it even commercially.</p>
<p>However AFAIK Parabola has a free culture requirement, so even if we have the right to modify it, we might lack the information to do that (the source code).</p>
<p>Though maybe some people have more information about the game format and all, so maybe I'm mistaken?</p> Packages - Bug #3334 (confirmed): Make aarch64-linux-gnu-gcc work again on armv7hhttps://labs.parabola.nu/issues/33342022-08-28T10:28:42ZGNUtooGNUtoo@cyberdimension.org
<p>Before we had an aarch64-linux-gnu-gcc package on armv7h, but it was removed accidentally.<br />And if we build the PKGBUILD it fails, so we need to fix the build and to upload a new package.</p>
<p>NOTE: the main reason we want this, is to compile the aarch64 kernel and bootloaders in a armv7h librechroot</p> Packages - Bug #3132 (not-a-bug): libre: asciidoc: The 8.6.10 source package changed upstreamhttps://labs.parabola.nu/issues/31322021-11-21T04:49:24ZGNUtooGNUtoo@cyberdimension.org
<p>While building asciidoc I have:<br /><pre>
| ==> Validating source files with sha256sums...
| asciidoc-8.6.10.tar.gz ... FAILED
| ==> ERROR: One or more files did not pass the validity check!
| ==> ERROR: Could not download sources.
+ get_output x86_64 libre/asciidoc /home/parabola/packages/libre/asciidoc
</pre></p>
<p>The PKGBUILD has the following:<br /><pre>
sha256sums=('9e52f8578d891beaef25730a92a6e723596ddbd07bfe0d2a56486fcf63a0b983')
</pre></p>
<p>And instead what I have downloaded has:<br /><pre>
$ sha256sum asciidoc-8.6.10.tar.gz
22d6793d4f48cefb4a6963853212a214591a591ece1bcbc56af3c67c642003ea asciidoc-8.6.10.tar.gz
</pre></p>
<p>And here both tarballs are different, and the sha256sum that is in the PKGBUILD does correspond to the archive checksum at the time.</p>
This can be verified by downloading the asciidoc package source at:
<ul>
<li><a class="external" href="https://repo.parabola.nu/sources/parabola/asciidoc-8.6.10-2.parabola1-any.src.tar.gz">https://repo.parabola.nu/sources/parabola/asciidoc-8.6.10-2.parabola1-any.src.tar.gz</a></li>
<li><a class="external" href="https://repo.parabola.nu/sources/parabola/asciidoc-8.6.10-2.parabola1-any.src.tar.gz.sig">https://repo.parabola.nu/sources/parabola/asciidoc-8.6.10-2.parabola1-any.src.tar.gz.sig</a></li>
</ul>
<p>The signature matches:<br /><pre>
$ gpg --verify asciidoc-8.6.10-2.parabola1-any.src.tar.gz.sig
gpg: assuming signed data in 'asciidoc-8.6.10-2.parabola1-any.src.tar.gz'
gpg: Signature made lun. 20 juil. 2020 07:57:07 CEST
gpg: using RSA key FBCC5AD7421197B7ABA72853908710913E8C7778
gpg: Good signature from "bill-auger <bill-auger@peers.community>" [unknown]
gpg: aka "bill-auger <mr.j.spam.me@gmail.com>" [unknown]
gpg: aka "bill-auger <bill-auger@programmer.net>" [unknown]
gpg: aka "[jpeg image of size 6017]" [unknown]
gpg: Note: This key has expired!
Primary key fingerprint: 3954 A7AB 837D 0EA9 CFA9 7989 25DB 7D9B 5A8D 4B40
Subkey fingerprint: FBCC 5AD7 4211 97B7 ABA7 2853 9087 1091 3E8C 7778
</pre></p>
<p>And the checksum matches too:<br /><pre>
$ tar tf asciidoc-8.6.10-2.parabola1-any.src.tar.gz
asciidoc/
asciidoc/PKGBUILD
asciidoc/.SRCINFO
asciidoc/asciidoc-8.6.10.tar.gz
$ tar xf asciidoc-8.6.10-2.parabola1-any.src.tar.gz
asciidoc-8.6.10.tar.gz PKGBUILD .SRCINFO
$ sha256sum asciidoc/asciidoc-8.6.10.tar.gz
9e52f8578d891beaef25730a92a6e723596ddbd07bfe0d2a56486fcf63a0b983 asciidoc/asciidoc-8.6.10.tar.gz
</pre></p>
<p>So the source was clearly modified upstream between when the package was made and now.</p>
<p>So let's look at the differences. For reference we have the following files:<br /><pre>
$ sha256sum 9e52f8578d891beaef25730a92a6e723596ddbd07bfe0d2a56486fcf63a0b983_asciidoc-8.6.10.tar.gz asciidoc-8.6.10.tar.gz
9e52f8578d891beaef25730a92a6e723596ddbd07bfe0d2a56486fcf63a0b983 9e52f8578d891beaef25730a92a6e723596ddbd07bfe0d2a56486fcf63a0b983_asciidoc-8.6.10.tar.gz
22d6793d4f48cefb4a6963853212a214591a591ece1bcbc56af3c67c642003ea asciidoc-8.6.10.tar.gz
</pre></p>
<p>And I'll attach the output of:<br /><pre>
$ diffoscope 9e52f8578d891beaef25730a92a6e723596ddbd07bfe0d2a56486fcf63a0b983_asciidoc-8.6.10.tar.gz asciidoc-8.6.10.tar.gz > asciidoc-8.6.10.tar.gz-diff.txt
</pre></p> libretools - Bug #2936 (fixed): librestage not working with pacman-mirrorlisthttps://labs.parabola.nu/issues/29362020-11-23T00:34:38ZGNUtooGNUtoo@cyberdimension.org
<p>I have the following error:<br /><pre>
$ ls
mirrorlist-20201122.txt pacman-mirrorlist-20201122-1.parabola2-x86_64-package.log
pacman-mirrorlist-20201122-1.parabola2-any.pkg.tar.xz pacman-mirrorlist-20201122-1.parabola2-x86_64-prepare.log
pacman-mirrorlist-20201122-1.parabola2-any.src.tar.gz PKGBUILD
$ librestage
==> ERROR: Nothing was staged
</pre></p>
<p>How is it possible to librestage pacman-mirrorlist?</p>
<p>Denis.</p> libretools - Bug #2648 (info needed): libremakepkg failing on i686 with Operation not permitted o...https://labs.parabola.nu/issues/26482020-03-03T15:41:24ZGNUtooGNUtoo@cyberdimension.orgPackages - Bug #2141 (fixed): libremakepkg failing to build package due to read-only startdir in ...https://labs.parabola.nu/issues/21412019-01-18T14:34:15ZGNUtooGNUtoo@cyberdimension.org
<p>I've tried building it inside an i686 chroot with:</p>
<pre>$ sudo libremakepkg -n parabola-i686</pre><br />and this gives:<br /><pre>
INSTALL sound/usb/snd-usb-audio.ko
INSTALL sound/usb/snd-usbmidi-lib.ko
INSTALL sound/usb/usx2y/snd-usb-us122l.ko
INSTALL sound/usb/usx2y/snd-usb-usx2y.ko
INSTALL sound/x86/snd-hdmi-lpe-audio.ko
INSTALL virt/lib/irqbypass.ko
DEPMOD 4.19.8-gnu-1
-> Installing hooks...
/startdir/PKGBUILD: line 466: /startdir/linux.install.pkg: Read-only file system
==> ERROR: A failure occurred in package_linux-libre().
Aborting...
</pre>
<p>related: <a class="external" href="https://lists.parabola.nu/pipermail/dev/2019-May/007207.html">https://lists.parabola.nu/pipermail/dev/2019-May/007207.html</a></p> libretools - Bug #2103 (not-a-bug): [linux-libre] cannot build due to missing gpg keyhttps://labs.parabola.nu/issues/21032018-11-28T14:41:37ZGNUtooGNUtoo@cyberdimension.org
<p>Hi,</p>
<p>I was trying to improve the linux-libre PKGBUILD by trying to fix the bug <a class="issue tracker-1 status-5 priority-3 priority-default closed" title="Bug: [linux-libre] cannot build due to missing gpg key (not-a-bug)" href="https://labs.parabola.nu/issues/2103">#2103</a>, however I cannot build it:<br /><pre>
$ sudo libremakepkg -n parabola-armv7h
[...]
| ==> Verifying source file signatures with gpg...
| linux-libre-4.19-gnu.tar.xz ... FAILED (unknown public key BCB7CF877E7D47A7)
| patch-4.19-gnu-4.19.2-gnu.xz ... FAILED (unknown public key BCB7CF877E7D47A7)
| logo_linux_clut224.ppm ... FAILED (unknown public key 227CA7C556B2BA78)
| logo_linux_mono.pbm ... FAILED (unknown public key 227CA7C556B2BA78)
| logo_linux_vga16.ppm ... FAILED (unknown public key 227CA7C556B2BA78)
| rcn-libre-4.19.2-armv7-x5.patch ... FAILED (unknown public key 227CA7C556B2BA78)
| ==> ERROR: One or more PGP signatures could not be verified!
| ==> ERROR: Could not download sources.
</pre></p> libretools - Housekeeping #2102 (open): librechroot should use the winston mirror exclusivelyhttps://labs.parabola.nu/issues/21022018-11-28T14:38:13ZGNUtooGNUtoo@cyberdimension.org
<pre>
$ sudo librechroot -n parabola-i686 update
[...] # went fine
$ sudo librechroot -n parabola-i686 enter
# pacman -Sy
:: Synchronizing package databases...
repo is up to date
libre is up to date
core is up to date
extra is up to date
community is up to date
pcr is up to date
# pacman -S git
resolving dependencies...
looking for conflicting packages...
Packages (4) perl-error-0.17027-1.0 perl-mailtools-2.20-2.1 perl-timedate-2.30-5.1 git-2.19.1-1.1
Total Download Size: 5.29 MiB
Total Installed Size: 39.93 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
error: failed retrieving file 'perl-error-0.17027-1.0-any.pkg.tar.xz' from redirector.parabola.nu : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed retrieving file 'perl-timedate-2.30-5.1-any.pkg.tar.xz' from redirector.parabola.nu : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed retrieving file 'perl-mailtools-2.20-2.1-any.pkg.tar.xz' from redirector.parabola.nu : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed retrieving file 'git-2.19.1-1.1-i686.pkg.tar.xz' from redirector.parabola.nu : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
[root@parabola /]# pacman -S perl-error
resolving dependencies...
looking for conflicting packages...
Packages (1) perl-error-0.17027-1.0
Total Download Size: 0.02 MiB
Total Installed Size: 0.10 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
error: failed retrieving file 'perl-error-0.17027-1.0-any.pkg.tar.xz' from redirector.parabola.nu : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
</pre> Documentation - Bug #1867 (open): Warn users about arbitrary execution of code with full disk enc...https://labs.parabola.nu/issues/18672018-07-03T00:43:36ZGNUtooGNUtoo@cyberdimension.org
<p>Users using full disk encryption without /boot in clear typically expects that it's harder to gain arbitrary execution of code inside the distribution that resides in it.</p>
An attacker would then need to temper with the non-encrypted code that runs before or during the opening of the encrypted partition. For instance:
<ul>
<li>If the user uses GRUB_ENABLE_CRYPTODISK=y the attacker would need to temper with the tiny GRUB code that is embedded on the internal disk.</li>
</ul>
However there are some cases where the attacker might need to reflash the boot software (BIOS, UEFI, etc):
<ul>
<li>If the user uses an external USB key to boot and the internal computer storage is fully encrypted</li>
<li>If users are using Libreboot or Coreboot with GRUB to open the encrypted partition with the internal storage fully encrypted<br />This can be mitigated by adding seals on the laptop screws (such as with nail polish or glue with glider)</li>
</ul>
<p>An other way for an attacker would be to try to temper with the storage device content and/or firmware: Authenticated encryption is pretty new in cryptsetup, and the commonly used encryption algorithms are not authenticated. So there may be ways to gain arbitrary execution of code either by injecting content by manipulating encryption parameters or by trying to implement some way to recover the key by using an oracle (as fsck may correct the corrupted data) but it's probably far from trivial to attempt any of that.</p>
<p>However there is an easier way with Parabola: if the attacker can guess the root= kernel parameter for instance root=/dev/laptop-rootfs, the attacker could stick an SD card with the same vg and lv.</p>
I can reproduce it with:
<ul>
<li>A thinkpad under Coreboot that has an SD card slot</li>
<li>The same VG/LV than the rootfs on a SD card</li>
<li>The encryption key being inside the initramfs</li>
</ul>
<p>I'll try to gather more information on the conditions necessary to trigger that problem (I had the issue several weeks ago).</p>
<p>This probably affects Libreboot too as there is documentation about such setup there too.</p> Installation Media - Feature Request #1780 (open): [armv7] do not set user/root password in futur...https://labs.parabola.nu/issues/17802018-05-02T11:11:24ZGNUtooGNUtoo@cyberdimension.org
<p>The <a class="external" href="https://repomirror.parabola.nu/iso/arm/LATEST/ParabolaARM-armv7-LATEST.tar.gz:"lastest">https://repomirror.parabola.nu/iso/arm/LATEST/ParabolaARM-armv7-LATEST.tar.gz:"lastest</a>" (at the time of writing) tarball release has a password set.</p>
<p>After booting the user can't log in.</p>
<p>Having no passwords in the next tarball release (and optionally adding the password to the <a class="external" href="https://wiki.parabola.nu/ARM_Installation_Guide#Change_or_set_the_root_password:"ARM">https://wiki.parabola.nu/ARM_Installation_Guide#Change_or_set_the_root_password:"ARM</a> installation guide" for this release would fix it.</p> Documentation - Bug #872 (fixed): Duplicated standalone installation instructions need to be mergedhttps://labs.parabola.nu/issues/8722015-11-22T18:06:11ZGNUtooGNUtoo@cyberdimension.org
<p>Move <a class="external" href="https://wiki.parabola.nu/User:Isacdaavid/Sandbox">https://wiki.parabola.nu/User:Isacdaavid/Sandbox</a> the the main namespace, like <a class="external" href="https://wiki.parabola.nu/Parabola_ARM_installation">https://wiki.parabola.nu/Parabola_ARM_installation</a></p>