Can not find "opkg-key add" passwall.pub in OpenWrt SNAPSHOT

I am using OpenWrt SNAPSHOT 25 on a Raspberry Pi 5 (by the way working great with even 2.5G Lan) . I want to install Passwall as explained here https://github.com/Ramtiiin/install-passwall2-openwrt
My question: what is replacing "opkg-key" in Version 25 ?

root@OpenWrt:~# opkg-key add passwall.pub
-ash: opkg-key: not found

the "opkg-key" is not found . I tried

root@OpenWrt:~# apk-key add passwall.pub
-ash: apk-key: not found

root@OpenWrt:~# apk-key add passwall.pub
-ash: apk-key: not found

When you log into your OpenWrt/ snapshot device via ssh, you get to read a large banner - which explains that opkg has been replaced by apk.

yes I saw this banner but I can not find the replacement for "opkg-key" I tried apk-key

How about you tell apk to ignore the keys, during package installation instead ?

or copy the key to the correct directory by hand?
/etc/apk/keys

root@router6000:~# ls -1 /etc/apk/keys/
openwrt-snapshots.pem
public-key.pem

EDIT:
It might not help as the key may be in the wrong format (usign key)...

root@router6000:/etc/apk/keys# cat passwall.pub
untrusted comment: OpenWRT usign key of dianlujitao
RWQKvaZaSStIhx4t06ISyV42CIpK7niKfR+Yro/WHiKLa122SEh2j3Z4

root@router6000:/etc/apk/keys# cat openwrt-snapshots.pem
-----BEGIN PUBLIC KEY-----
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEqDM0+yparYvbHosRPBhvT5Z3MEXz
AFYrTnqJrnURywsKpD+ZKCLjPluvoHe/FABIvIuHLvICALA3IMjhm0Z0cA==
-----END PUBLIC KEY-----

thank you
root@OpenWrt:~# apk add luci-app-passwall-25.1.28-r1.apk --allow-untrusted

yes it helped me find out that the next issue is that Passwall need so many packages which are not pre-compiled for Cortex A76

I thought this Passwall could be helpful in China and found the following Video: https://youtu.be/7pVN4-N8wio?si=xZykLuaO7QfMN91W
However, this is showing an installation on a PC

There's v2ray, but I have no idea if they do the same (or perhaps are the same), I don't use any of them.

Hi. If you want to install Passwall 2, then use these commands, everything works. Just be careful when entering commands.

 # opkg update

 # opkg remove dnsmasq

 # opkg install dnsmasq-full

 # opkg install kmod-nft-socket

 # opkg install kmod-nft-tproxy

 # opkg install kmod-nft-nat

 # opkg install wget-ssl

 # wget -O passwall.pub https://master.dl.sourceforge.net/project/openwrt-passwall-build/passwall.pub

 # opkg-key add passwall.pub

read release arch << EOF
$(. /etc/openwrt_release ; echo ${DISTRIB_RELEASE%.*} $DISTRIB_ARCH)
EOF
for feed in passwall_luci passwall_packages passwall2; do
  echo "src/gz $feed https://master.dl.sourceforge.net/project/openwrt-passwall-build/releases/packages-$release/$arch/$feed" >> /etc/opkg/customfeeds.conf
done

 # opkg update

 # opkg install luci-app-passwall2

 # opkg update

 # reboot

Except that there is no opkg in the main/master builds...
There is now apk (like the OP says already in the first message).

So, most of the commands you list would only work in 24.10 or earlier releases, but not in the current main/master SNAPSHOT builds.

Hello. Everything works in the stable version of OpenWrt 23.05.5, checked a couple of days ago.
I DID NOT use APK!
Personally, in my opinion, it is a mistake to change OPKG to APK, this will create additional confusion for users when searching the Internet, since the apk format is used for android files.
This is a mistake by the developers! (my subjective opinion) It was possible to make, for example, OPK!

https://wiki.adminforge.de/wiki/Apk_(file_format)?lang=en

The Android Package with the file extension apk[1] is the file format used by the Android operating system

No, that is a different apk format. This is apk from Alpine Linux. File extensions have not been uniquely allocated, ever.

I understand what you mean https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper

Let's start learning Alpine Package Keeper :grinning:

I quote from : https://linuxiac.com/openwrt-adopts-apk-as-new-package-manager/
"One difference is that APK requires valid signatures for all packages, while OPKG ignores this requirement for local ones. Therefore, if you’re installing a non-standard (self-built) package, use the --allow-untrusted option."

you posted this 19h ago ?

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.