[PATCH v3 2/4] build: get_source_date_epoch allow external repos

allows granular but still reproducible timestamps. As packages might be distributed over multiple repositories the check for `.git/` becomes unfeasible. Instead tell `git` and `hg` to change their working directories and automatically traverse the repo folder. Signed-off-by: Paul Spooren --- scripts

[PATCH v3 3/4] build: store granular timestamps in packages

SOURCE_DATE_EPOCH is used or as last resort the current time. The redundant checks for `.git/` and `.svn/` are removed. Signed-off-by: Paul Spooren --- include/package-ipkg.mk | 1 + scripts/ipkg-build | 12 +++- 2 files changed, 4 insertions(+), 9 deletions(-) diff --git a/include/package

[PATCH v3 4/4] build: store SourceDateEpoch in manifest

The usage of granular `SOURCE_DATE_EPOCH` for packages is an incrementing integer which could be useful for downstream tooling, therefore add it to the packages manifest. Signed-off-by: Paul Spooren --- include/package-ipkg.mk | 1 + package/Makefile| 2 +- 2 files changed, 2 insertions

[PATCH v3 1/4] build: Fix Shellcheck for get_source_date_epoch.sh

If a `cd` to `TOPDIR` fails the script should quit. Also unify `try_mtime` function by storing it in a variable. Signed-off-by: Paul Spooren --- scripts/get_source_date_epoch.sh | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/scripts/get_source_date_epoch.sh b

[PATCH v3 0/4] Granular timestamps in packages

on etc. building the same package sources might generate different binaries (this seems to be the lesser problem atm) Part 2 will be tackled in some later patches. [1]: http://logs.nslu2-linux.org/livelogs/openwrt-devel/openwrt-devel.20200807.txt Paul Spooren (4): build: Fix Shellc

[PATCH v6] treewide: use wpad-basic-wolfssl as default

-off-by: Adrian Schmutzler [rebase] Signed-off-by: Paul Spooren --- I'd suggest to have a "one package per line" policy. It's easier to sort alphabetically (e.g. vim :sort), better human parsable and would avoid these rebases. target/linux/apm821xx/image/sata.mk |

Re: [RFC] Policy for PKG_RELEASE bumps

On 17.08.20 20:55, Florian Eckert wrote: Hi team, * When anything inside the packages ipk file changes     Includes patch and so called "cosmetic" changes outside the Makefile, e.g. replace tabs with spaces. PKG_VERSION: This is the upstream version of the Project and this is the upstream

[PATCH] build: add whatdepends target to imagebuilder

can be fed into a SDK building all packages and warn if anything fails. Signed-off-by: Paul Spooren --- I'm currently running a CI which determines affected areas as first step, an example is here where the `fstools` packages was modified: https://gitlab.com/aparcar/openwrt/-/jobs/69671359

Re: [PATCH] build: SDK/IB reproducible and faster compression

As friends of reproducible builds please have a look at this patch. On 13.08.20 13:46, Paul Spooren wrote: Both IB and SDK now use the same logic for packing. This commit add reproducible multithread compression to the SDK and corrects the file mtime for both. Previously all files where just

Re: [PATCH] build: SDK/IB reproducible and faster compression

On 21.08.20 06:47, Matthias Schiffer wrote: Did you have a look at the zstd patches I sent a while ago? zstd is superior to xz in most cases - the only reason I didn't merge the patches yet was that all of our phase2 buildbots would need to have zstd installed to extract the new SDK before we ca

[PATCH v2] build: optionally disable target name in filenames

d by the option. Signed-off-by: Paul Spooren --- v2: Make it optional and keep everything as it is right now by default. include/image.mk | 13 + package/base-files/image-config.in | 11 +++ 2 files changed, 20 insertions(+), 4 deletions(-) diff --git a/inc

Re: [PATCH v2] build: optionally disable target name in filenames

The PKG_RELEASE must be bumped which I forgot in this patch! On 22.08.20 22:23, Paul Spooren wrote: The target/subtarget is included in all image filenames by default. This is useful if the same profile exists in multiple targets or developers/users want an obvious related of images to targets

Re: [PATCH] tools: always create $STAGING_DIR/usr/{include,lib}

On 19.08.20 20:06, Andre Heider wrote: rules.mk always passes these as -I/-L to the toolchain. Fixes rare errors like: cc1: error: staging_dir/target-aarch64_cortex-a53_musl/usr/include: No such file or directory [-Werror=missing-include-dirs] Signed-off-by: Andre Heider Acked-by: Paul

Re: [PATCH] tools: always create $STAGING_DIR/usr/{include,lib}

On 24.08.20 00:55, Jo-Philipp Wich wrote: Hi, rules.mk always passes these as -I/-L to the toolchain. Fixes rare errors like: cc1: error: staging_dir/target-aarch64_cortex-a53_musl/usr/include: No such file or directory [-Werror=missing-include-dirs] Signed-off-by: Andre Heider NAK - I'd

[PATCH] treewide: https for downloads.openwrt.org sources

Instead of using http and https for source downloads from downloads.openwrt.org, always use https for it's better security. Signed-off-by: Paul Spooren --- package/firmware/b43legacy-firmware/Makefile | 2 +- package/kernel/broadcom-wl/Makefile | 2 +- package/kernel/lantiq/ltq

Re: [PATCH 2/2] tools: mtd-utils: Update to version 2.1.2

On 25.08.20 12:23, Hauke Mehrtens wrote: The release notes says this: As already said, the changes since 2.1.1 are primarily bug fixes, addressing compiler warnings and issues reported by diagnostic tools, but also build failures for some configurations. https://lists.infradead.org/pipermail/linu

[PATCH v3] treewide: switch to HTTPS by default

From: Petr Štetiar As there is now wolfSSL included by default due to SAE/WPA3 we can finally switch to TLS/SSL in other parts as well. Tested-by: Paul Spooren Signed-off-by: Petr Štetiar [rebased, separate packages by newline and sort] Signed-off-by: Paul Spooren --- changed in v2

Re: [PATCH opkg] opkg: allow to configure the path to the signature verification script

place, both worked fine. The openwrt.git/opkg-key (not opkg.git/opkg-key) script uses currently a hard coded key position (`/etc/opkg/keys`) which should be patched next. Test-by: Paul Spooren Acked-by: Paul Spooren --- libopkg/opkg_conf.c | 4 libopkg/opkg_conf.h | 3

[PATCH] build: opkg-key variable key folder

set arbitrary key folder locations. Arbitrary key folder locations are useful to add signature verification to the ImageBuilders. Signed-off-by: Paul Spooren --- package/system/opkg/files/opkg-key | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/package/system/opkg

[PATCH] imagebuilder: add package signature verification

just a shell script. The keys folder is added to IBs TOPDIR to have an obvious place for users to store their own keys. The `option check_signature` is appended to the repositories.conf file. All of the above only happens if the Buildbot runs with the SIGNED_PACKAGES option. Signed-off-by: Paul

Re: [PATCH] build: opkg-key variable key folder

On 26.08.20 09:17, Baptiste Jonglez wrote: On 25-08-20, Paul Spooren wrote: The key folder is used by `opkg` and `usign` to store and retrieve trusted public keys. Using `opkg-key` outside a running device is unfeasible as the key folder is hard coded to `/etc/opkg/keys`. This commit adds a

[PATCH 1/2] imagebuilder: rename PKG_BUILD_DIR to IB_BUILD_DIR

This follow the SDK naming schema is and is more clear as no package is build. Signed-off-by: Paul Spooren --- target/imagebuilder/Makefile | 66 ++-- 1 file changed, 33 insertions(+), 33 deletions(-) diff --git a/target/imagebuilder/Makefile b/target

[PATCH 2/2] imagebuilder: improve reproducibility

The SOURCE_DATE_EPOCH is used to unify the mtime within created images, make it the same as the build system used during creation of the IB. The LINUX_VERMAGIC is used to create a reproducible IMG_PART_SIGNATURE, therefore make it available to the IB as well. Signed-off-by: Paul Spooren

[PATCH] imagebuilder: fix sstrip

Without an absolute path to staging_dir/host/bin/sstrip the Makefile tries to run a host installed version of sstrip, which is likely not available. Signed-off-by: Paul Spooren --- target/imagebuilder/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target

[PATCH 2/3] build: sort default packages and split by newlines

The line of default packages became very long and it is easier to read one package per line, therefore split it by newlines and sort it alphabetically. Signed-off-by: Paul Spooren --- include/target.mk | 35 --- 1 file changed, 32 insertions(+), 3 deletions

[PATCH 3/3] build: switch VERSION_REPO to HTTPS

The variable VERSION_REPO is used by opkg to download package(list)s. Now that the default installation support encrypted HTTP opkg should make use of it. Suggested-by: Petr Štetiar Suggested-by: Baptiste Jonglez Signed-off-by: Paul Spooren --- include/version.mk | 2

[PATCH 1/3] build: add libustream and certs to default pkgs

Suggested-by: Baptiste Jonglez Signed-off-by: Paul Spooren --- include/target.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/target.mk b/include/target.mk index 6ed6565bda..b0c563a0ef 100644 --- a/include/target.mk +++ b/include/target.mk @@ -13,7 +13,7

[RFC] self-signed certificates for LuCI

Hi team, I recently rewrote px5g[1] to use WolfSSL instead of MbedTLS, as the former will be included in OpenWrt 20.x per default. Both implementations support the generation of RSA and ECC keys, where uhttpd currently defaults to RSA with 2048 keys. The question came up if we really want R

Re: [RFC] self-signed certificates for LuCI

On 30.08.20 12:32, Michael Richardson wrote: Paul Spooren wrote: > I recently rewrote px5g[1] to use WolfSSL instead of MbedTLS, as the former > will be included in OpenWrt 20.x per default. > Both implementations support the generation of RSA and ECC keys, wher

[PATCH v3] dropbear: Enable Ed25519 for normal devices

cleaner than splitting `dropbear` into two packages like `dropbear` and `dropbear-ed25519`. Signed-off-by: Paul Spooren --- v3: * Add PKG_FLAGS:=nonshared to avoid trouble with legacy `tiny` targets package/network/services/dropbear/Config.in | 2 +- package/network/services/dropbear/Makefile

[PATCH] config: add KERNEL_LSM symbol

/selinux/config`. Signed-off-by: Paul Spooren --- config/Config-kernel.in | 14 +++--- 1 file changed, 3 insertions(+), 11 deletions(-) diff --git a/config/Config-kernel.in b/config/Config-kernel.in index 4eaaa4afae..1f677fd1f5 100644 --- a/config/Config-kernel.in +++ b/config/C

Re: [PATCH] ath79: drop Build/loader-kernel-cmdline

On 02.09.20 01:21, Adrian Schmutzler wrote: This is the same as loader-kernel since the KERNEL_CMDLINE parameter has been removed in [1] and not used at all anyway. Remove it. [1] f77db1a59036 ("ath79: cleanup image build code") Signed-off-by: Adrian Schmutzler Acked-by: Pa

[PATCH 1/2] build: ipkg-build add -r option for all-root

script with `fakeroot`. Signed-off-by: Paul Spooren --- scripts/ipkg-build | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/scripts/ipkg-build b/scripts/ipkg-build index e3a9a882cf..38149c4432 100755 --- a/scripts/ipkg-build +++ b/scripts/ipkg-build @@ -1,5 +1,7 @@ #!/bin

[PATCH 2/2] build: only use fakeroot for packages if required

MODES` is set. If it is not defined the newly added *all root* option `-r` is used. Signed-off-by: Paul Spooren --- include/package-ipkg.mk | 6 ++ 1 file changed, 6 insertions(+) diff --git a/include/package-ipkg.mk b/include/package-ipkg.mk index 0b7a561edc..362fa25307 100644 --- a/in

Re: [PATCH 1/2] build: ipkg-build add -r option for all-root

On Sat Sep 5, 2020 at 1:58 AM HST, Karl Palsson wrote: > > Paul Spooren wrote: > > > > diff --git a/scripts/ipkg-build b/scripts/ipkg-build > > index e3a9a882cf..38149c4432 100755 > > --- a/scripts/ipkg-build > > +++ b/scripts/ipkg-build > > @@ -1,

[PATCH] build: fix missing file handling for file_modes

* variant. This commit checks if the file/folder exists, if not a warning is printed but no longer a positive exit code produced. Also clean up indention of surrounding lines. Signed-off-by: Paul Spooren --- scripts/ipkg-build | 25 +++-- 1 file changed, 15 insertions(+), 10

[PATCH] build: create rootfs.tar.xz if BUILDBOT

multiple packages, QEMU is used inside another CI step run run OpenWrt rootfs containers in multiple architectures, install the create package and execute a runtime test. Signed-off-by: Paul Spooren --- This change would allow additional runtime tests for this PoC: https://github.com/openwrt

Re: [PATCH] imagebuilder: add package signature verification

Hi, On Tue Aug 25, 2020 at 10:24 PM HST, Paul Spooren wrote: > The ImageBuilder downloads pre-built packages and adds them to images. > This process uses `opkg` which has the capability to verify package list > signatures, as enabled per default on running OpenWrt devices. > > Unt

Re: [PATCH] imagebuilder: add package signature verification

Hi, On Mon Sep 14, 2020 at 12:27 PM HST, Baptiste Jonglez wrote: > Hi, > > Thanks for the patch, it looks good but comments below: > > On 25-08-20, Paul Spooren wrote: > > The ImageBuilder downloads pre-built packages and adds them to images. > > This process uses `opk

Re: HTTPS performance issue with opkg (Was: [PATCH 3/3] build: switch VERSION_REPO to HTTPS)

On Mon Sep 14, 2020 at 10:23 PM HST, Daniel Golle wrote: > On Tue, Sep 15, 2020 at 08:49:51AM +0200, Baptiste Jonglez wrote: > > On 27-08-20, Paul Spooren wrote: > > > The variable VERSION_REPO is used by opkg to download package(list)s. > > > Now that the default ins

[PATCH] conf: add src/{,gz}/trusted option

unsigned. The two new config options are: src/trusted src/gz/trusted Signed-off-by: Paul Spooren --- ImageBuilders offer a folder called "packages/" which includes at least the packages kernel_*.ipk and libc*.ipk, additionally packages provided by the user. It is not p

[PATCH v2] imagebuilder: add package signature verification

-by: Paul Spooren --- target/imagebuilder/Makefile | 10 +- target/imagebuilder/files/Makefile | 2 ++ 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/target/imagebuilder/Makefile b/target/imagebuilder/Makefile index ad19ab2b53..0cdc1f4d93 100644 --- a/target

Policy for adding new files to OpenWrt

Hi team, Based on PR#3427 on GitHub[0] I'd suggest we add a policy that every added file needs a SPDX header. This likely simplifies merging patches into mainline Kernel and probably makes some lawyers happy. There are fancy tools to do so, like the `reuse` project[1]. Best, Paul [0]: https://g

[PATCH 1/2] libopkg: remove support for "dist" config

The "dist" config option is legacy to imitate Debians repository structure. However this is never used within the OpenWrt ecosystem and can therefore be removed. Signed-off-by: Paul Spooren --- libopkg/opkg_conf.c | 32 +++- libopkg/opkg_conf.h | 1

[PATCH 2/2] libopkg: remove "extra_data" option

dummy__" it is cleaner to "comment out" the specific repository and Debian repository structure is nowhere used in the OpenWrt ecosystem, therefore it seem save to remove "extra_data". Signed-off-by: Paul Spooren --- libopkg/opkg.c | 17 - libopkg

Re: [PATCH] build, imagebuilder: Do not require compilers

cking for > the compilers if running as ImageBuilder. A similar change has been > made for libncurses-dev in 4a1a58a3e2d2. > > Signed-off-by: Sven Roederer Acked-by: Paul Spooren > --- > include/prereq-build.mk | 4 > 1 file changed, 4 insertions(+) > > diff --git

Re: [PATCH v2] imagebuilder: add package signature verification

On Tue Sep 15, 2020 at 3:24 PM HST, Paul Spooren wrote: > The ImageBuilder downloads pre-built packages and adds them to images. > This process uses `opkg` which has the capability to verify package list > signatures via `usign`, as enabled per default on running OpenWrt > devices. &

[RFC]Secure ImageBuilders

Hi, Over the last month I suggested two different approaches to improve the ImageBuilder security. The amount of feedback was fairly low, maybe partly because it's not trivial to understand the issue. I wrote a summary of the two approaches and the current problem, please spend the 5 minutes to re

[PATCH opkg] pkg_hash: don't suggest incompatible packages

the kmods archive and the target specific packages feed. This commit fixes the issue by dropping all package problematic candidates by checking if all their dependencies could be installed. Signed-off-by: Paul Spooren --- libopkg/pkg_hash.c | 20 +--- 1 file changed, 17

[PATCH buildbot] phase1: don't add kmod feed via buildbot

*hacked* into the images by the buildbot. Signed-off-by: Paul Spooren --- Patch for openwrt.git is here: https://github.com/openwrt/openwrt/pull/3425/commits/9343e7d65494b6b9fd7bf0d76b0d5371f7e6dbd2 phase1/master.cfg | 27 --- 1 file changed, 27 deletions(-) diff --git a

[PATCH opkg v2] pkg_hash: don't suggest incompatible packages

the kmods archive and the target specific packages feed. This commit fixes the issue by dropping all package problematic candidates by checking if all their dependencies could be installed. Signed-off-by: Paul Spooren --- v2: - Only resolve dependencies if architecture is selected and package

Meeting Notes February

Hi all, We had another meeting, please find the notes below: https://openwrt.org/meetings/20230124 Sunshine, Paul ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Anyone working on porting OpenSSL to v3.x?

Hey all, We’re still using OpenSSL 1.1.x within OpenWrt and during the last developer meeting we were wondering if anyone is working on porting it over to v3.x? If so please share your status, thanks! Best, Paul ___ openwrt-devel mailing list openwrt-

OpenWrt project mirrors on GitHub

Hi all, All project from git.openwrt.org are now mirrored over to GitHub to allow further use of the CI and better visibility. I’d like to get some opinions on enabling Issues (aka GitHub bug tracker). Right now issues are enabled since other “subprojects” like odhcpd and mt76 have their own b

Meeting notes 21st February 2023

Hi all, with a bit of a delay the notes of the last meeting. Nothing special came up, mostly a recap of what happened over the month. https://openwrt.org/meetings/20230221 Best, Paul ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http

Re: Docker is sunsetting Free Team organizations

Hi all, > > we don't mirror it elsewhere. > >> (gitlab/github) >> docker.io/openwrtorg/imagebuilder >> docker.io/openwrtorg/sdk >> docker.io/openwrtorg/rootfs I’d sunset openwrtorg and only use “openwrt”. > >> Do we want to apply for "Docker-Sponsored Open Source Program" >> https://www.docke

Re: Docker is sunsetting Free Team organizations

Hi, I requested sponsoring from Docker, let’s see how it goes. While at it, I’d remove openwrtorg entirely instead of not updating it. I don’t thing we get sponsoring for both orgs and it’s just confusing. Best, Paul > On 17. Mar 2023, at 12:00, Paul Spooren wrote: > > Hi all, >

Re: next OpenWrt 22.03 and 21.02 minor release

> On 28. Mar 2023, at 09:09, Joseph Mullally wrote: > >> If we should backport more changes please create a pull request on >> github, send a patch with the 22.03 or 21.02 prefix to the mailing list >> or send a mail with a link to the master commit we should backport as an >> answer to this ma

Meeting Notes March 2023

Hi, Another month, another developer meeting - short and sweet: https://openwrt.org/meetings/20230328 Best, Paul ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: next OpenWrt 22.03 and 21.02 minor release

Hi all, Last night we tagged two new point releases for the 22 and 21 releases. I’m traveling right now but will try to write the release notes later today. Best, Paul > On 7. Apr 2023, at 18:31, openwrt-de...@matthias-larisch.de wrote: > >  >> >> Mateusz Jończyk wrote on 06.04.23 14:18: >>>

Sunsetting the Docker `openwrtorg` org (not `openwrt` org)

Hi all, I’d like to disable the `openwrtorg` organization on Docker.io . It was initially created since some unknown entity registered `openwrt` without using it. After some clarification with the Docker team they thankfully granted us access to the account. By migrating th

OpenWrt 22.03.4 and 21.02.6 released

Hi all, As many of you already figured, two new stable releases are out! Please consider a timely update unless you’re running certain devices of the ipq40xx target[1]. -> 22.03.4 Release Notes: https://github.com/openwrt/openwrt/releases/tag/v22.03.4 Changelog: https://openwrt.org/releases/22.

Re: 22.03.4 and 21.02.6 were officially announced 3 days ago, but only partially.

Hi, > On one hand: >* two threads were posted in the "Release and security announcements” > section of the OpenWrt forum >* the OpenWrt.org front page has been updated with links to the new > versions >* the release notes are no longer WIP >* the firmware selector has the new ver

Re: [OT] Additional container registry mirror [Was: Re: Sunsetting the Docker `openwrtorg` org (not `openwrt` org)]

Hi all, >> I've not done any prior research about all viable options yet, but quay.io >> looks so far as my favorite option. Any objections/ideas? I added quay.io as a third registry (next to docker.io and ghcr.io ). By doing so I found that there seem to be

Mark lantiq and omap as source only

Hi all, I haven’t seen much progress happening regarding bringing the targets lantiq or omap to Kernel 5.15. That fact is currently the last blocker for branching another release. Instead of postponing another release I’d like to mark both targets as source-only and do the 23.05 branch, starti

Meeting Notes April 2023

Hi all, another month, another meeting -> https://openwrt.org/meetings/20230425 Happy first of May, Paul ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [VOTE] commit access for PolynomialDivision (Nick Hainke)

onboarding. Best, Paul > On 25. Apr 2023, at 19:59, Paul Spooren wrote: > > Hi all, > > After talking to Nick directly and asking during the last developer meeting a > few minutes ago, I’d like to start a vote on granting Nick commit access. > > With more than 300 commits i

Call for help with sysupgrade.openwrt.org maintainance

Hey all, some long time ago I attended a Google Summer of Code and created this service som may know called sysupgrade.openwrt.org. Essentially it’s an API for OpenWrt ImageBuilders. Instead of downloading them and its dependencies, you request a firmware image by specifying version, installed

Re: Reserving USERID

Hi, > Is explicit better or not? And if it is better, how do I go about reserving > values that won't get stepped on? Who is our Numbers Czar, who is our IANA? I always used Gentoos numbers[1] whenever I added something. Since Clixon is not part of that list, maybe use something that’s not ye

Adding a new x86 image or related packages to the default x86 image

Hi, I’d like to merge the PR which adds the Mellanox Spectrum SN2100 to OpenWrt[1]. In its current state a new x86 image would be added next to the generic x86 image. Another approach is to add all related packages to the default image. Either way creates a working image. I remember that peopl

Re: Adding a new x86 image or related packages to the default x86 image

Hi, > I'd suggest to stick to a single x86_64 image for maintenance and testing > reasons alone I agree. Furthermore, x86 devices have often no device identity like other devices using device tree do. With the current implementation, the attended sysupgrade service would be broken since on x86

Re: [PATCH] x86 64: Add new device Cordoba Edge Platform

Hi, We kind of don’t add image just to contain extra drivers. Extra UCI defaults for eth ordering are fine but please don’t add an extra image if it just contains 1-2 extra packages, installable via the ImageBuilder or OPKG. > >> On Oct 23, 2023, at 8:52 PM, Xiaojun Liu wrote: >> >> Add new

Re: [PATCH firmware-utils] add dlink-sge-image for D-Link devices by SGE

Hello, > On Jun 23, 2023, at 14:06, Sebastian Schaper > wrote: > > This tool will encrypt/decrypt factory images requiring the "SHRS" header > e.g. COVR-C1200, COVR-P2500, COVR-X1860, DIR-878, DIR-882, ... > > Encryption is loosely based on a series of blogposts by ricksanchez [1] > and the pr

Re: [PATCH v2 firmware-utils] add dlink-sge-image for D-Link devices by SGE

> On Nov 2, 2023, at 20:16, Sebastian Schaper > wrote: > > This tool will encrypt/decrypt factory images requiring the "SHRS" header > e.g. COVR-C1200, COVR-P2500, COVR-X1860, DIR-878, DIR-882, ... > > Encryption is loosely based on a series of blogposts by ricksanchez [1] > and the provided

Re: Adding a new x86 image or related packages to the default x86 image

>> On 2023-09-14, Paul Spooren wrote: >>> >>> I’d like to merge the PR which adds the Mellanox Spectrum SN2100 to >>> OpenWrt[1]. In its current state a new x86 image would be added next >>> to the generic x86 image. Another approach is to add all rela

Battlemesh x OpenWrt meeting in Cyprus?

Hi all, While attending this years Battlemesh in Spain some fellow mesh people asked why there weren’t more OpenWrt people around. I’m guessing it was mostly due to the lack of communication in advance, so I’d like to raise the topic here: Are people from the OpenWrt community, specially member

Maintenance of openwrt.org and CDN for downloads

Dear all, I plan to upgrade our wiki (openwrt.org ) next Sunday, 17th of December. I’m expecting just a short downtime since a successful upgrade already happened on a staging instance. In case you urgently need to lookup information, please use the staging instance during

Re: Maintenance of openwrt.org and CDN for downloads

package managers… Please report on issues and problems, ideally only to the openwrt-adm list. Thanks everyone for using OpenWrt! Best, Paul > On Dec 13, 2023, at 17:10, Paul Spooren wrote: > > Dear all, > > I plan to upgrade our wiki (openwrt.org <http://openwrt.org/>) ne

Re: Maintenance of openwrt.org and CDN for downloads

ould be able to serve 1PB/a, so ideally nothing that is limited to 1-2 TB per month. Thanks for ideas! Please enjoy the new download speeds including HTTP/3. Sunshine, Paul [1]: https://openwrt.org/downloads#mirrors > On Dec 13, 2023, at 17:10, Paul Spooren wrote: > > Dear all, >

RFC pkgs.staging.openwrt.org

Hey all, tl;dr checkout https://pkgs.staging.openwrt.org/ As some may experienced, openwrt.org is slow an one (of many reasons) is that it stores and renders tables with all packages. Based on feedback the experience is neither convincing nor does it perform well within a DokuWiki. After aski

Re: PKG_MAINTAINER_HANDLE

Hi Paul, > PKG_MAINTAINER:=Joe Bloggs > PKG_MAINTAINER_HANDLE:=github: @joe; https://forum.openwrt.org/u/joe/ > > Plan B > > co-opt existing PKG_MAINTAINER field, but perhaps it's possible? > > e.g: > > PKG_MAINTAINER:=Joe Bloggs , github: @Joe I think for that you could use a Codeowners fil

[PSA] forum.archive.openwrt.org moved to static copy

Hi all, As part of the ongoing migration away from the old mirror-01 server I copied the old forum today to a static git repository[1]. It’s now hosted as a GitHub page. Since they don’t support IPv6[2] I may move it to another provider in the near future. For now you may clone the repository

Re: Real name vs. known identity in contributions

Hi one-d-wide, > Unfortunately I was refused to contribute under my usual nickname due to > real-name-only rule I adopted the `submitting-patches` page and create PRs for both openwrt.git and packages.git. Thanks for reminding me of this. https://github.com/openwrt/packages/pull/23084 https:/

Re: Are we still use md5 as default as password hash?

Hi, > however Busybox doesn't configed to use those and still use md5 as > default, while we bring other hash algos into flash anyway: Does the following do the trick? diff --git a/package/utils/busybox/Config-defaults.in b/package/utils/busybox/Config-defaults.in index b3c3f9a0b2..5ae8dd5622 1

Re: Are we still use md5 as default as password hash?

ha512: this will make all new >> passwds to use new hash (shell or luci), but won't upgrade without user >> changing it first. but we'd better expose and set USE_BCRYPT of busybox >> option to be able to use bcrypt here (not sure routers cpu can handle it >> as it'

Re: [VOTE] New member proposal: Robimarko (Robert Marko)

Hi, > On Jan 30, 2024, at 19:15, Christian Marangi (Ansuel) > wrote: > > Robert is active in OpenWrt since 2017 and with some recent stats, he > has more than 310 commits merged in OpenWrt. > He also have uncounted Reviewed-by tag on various PR and merged commits > and generally helps in everyt

ustream-ssl ABI_VERSION usage

Hi, While working on using APK instead of OPKG, I started to look into ABI versions of different packages and found that ustream-ssl always install libustream-ssl.so , with no ABI version attached. > $(INSTALL_DATA) $(PKG_INSTALL_DIR)/usr/lib/libustream-ssl.so $(1)/l

Re: ustream-ssl ABI_VERSION usage

Hi, > On Feb 12, 2024, at 14:30, Petr Štetiar wrote: > > Jo-Philipp Wich [2024-02-12 14:09:27]: > > Hi, > >> Ideally all packages specifying an ABI version should ship versioned .so >> files >> as well. > > I would like to point out, that ustream-ssl is dynamically loaded library[1], > so

Re: some github runner failers

> On Feb 15, 2024, at 00:12, Paul D wrote: > > https://github.com/openwrt/packages/actions/runs/7908507874/job/21587828762?pr=23415 > > for various platforms > > errors: > > > #4 [internal] load metadata for > docker.io/openwrt/rootfs:i386_pentium-mmx-openwrt-23.05 > #4 ERROR: no match for

Re: live test system

Hi Paul (cool name!), > Another live system with openwrt master with various openwrt PRs that come > in, integrated under some predictable URL (https://host/pr2). Some kind > of capability to tweak settings live, or see the console output. ( Does owrt > run well in docker as a guest? ) QEM

Install LuCI for snapshots builds

Hi all, For some reason (resource usage?) our snapshot builds do not include the LuCI web interface. I think it’s an advantage to have LuCI installed in snapshot images since a) it installed for all releases anyway and b) often it’s just nice to have the web interface directly available. Is an

Re: [RFC PATCH] hostapd: Add support for APuP

Hi Gio, > On 10. May 2024, at 19:48, gio--- via openwrt-devel > wrote: > > The sender domain has a DMARC Reject/Quarantine policy which disallows > sending mailing list messages using the original "From" header. > > To mitigate this problem, the original message has been wrapped > automaticall

Re: Install LuCI for snapshots builds

Hi, — %< — Well to conclude, it takes more time and there is “always” firmware-selector.openwrt.org, so I’ll just leave it as is. Thanks for your thoughts, Paul ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/m

State of APK package manger integration

Dear all, With great contributions from Timo, Ansuel, Jonas, Daniel, Petr, John, and many others, APK is evolving smoothly, and the integration is progressing well! We have established a staging buildbot environment[1] that compiles firmware images and certain packages. To replicate this setup

Re: OpenWrt One - celebrating 20 years of OpenWrt

Sure, https://github.com/cyyself/wg-bench/pull/37 > On 29. Jul 2024, at 19:37, Paul D wrote: > > > Hi, could one of the early ONE owners/users post numbers for the ONE > regarding WireGuard performance? > > https://forum.openwrt.org/t/a-wireguard-comparison-db/187586/1 > > It's an important

Re: State of APK package manger integration

]: https://github.com/aparcar/openwrt/commit/2c98eb52e365be6e59b470b4c0001cf29e8a6fb3 [6]: https://buildbot.aparcar.org/faillogs/x86_64/ > On 13. Jun 2024, at 13:29, Paul Spooren wrote: > > Dear all, > > With great contributions from Timo, Ansuel, Jonas, Daniel, Petr, John, and >

<    1   2   3   4   5   6