OpenWrt 19.07.8 service release

Perhaps I am doing something wrong, but I get the message that the key has expired.

Dowloaded

https://downloads.openwrt.org/releases/19.07.8/targets/ath79/generic/sha256sums

and

https://downloads.openwrt.org/releases/19.07.8/targets/ath79/generic/sha256sums.asc

Then

$ gpg --with-fingerprint --verify sha256sums.asc sha256sums
gpg: Signature made Wed 17 Feb 2021 14:52:39 CET
gpg:                using RSA key D9C6901F45C9B86858687DFF28A39BC32074BE7A
gpg: Good signature from "OpenWrt Build System (PGP key for 19.07 release builds) <pgpsign-19.07@openwrt.org>" [expired]
gpg: Note: This key has expired!
Primary key fingerprint: D9C6 901F 45C9 B868 5868  7DFF 28A3 9BC3 2074 BE7A

Presumably they key is not meant to be expired?

Edit to add:

$ gpg -a --export "19.07"| gpg --list-packets 
# off=0 ctb=99 tag=6 hlen=3 plen=525
:public key packet:
	version 4, algo 1, created 1563103655, expires 0
	pkey[0]: [4096 bits]
	pkey[1]: [17 bits]
	keyid: 28A39BC32074BE7A
# off=528 ctb=b4 tag=13 hlen=2 plen=83
:user ID packet: "OpenWrt Build System (PGP key for 19.07 release builds) <pgpsign-19.07@openwrt.org>"
# off=613 ctb=89 tag=2 hlen=3 plen=599
:signature packet: algo 1, keyid 28A39BC32074BE7A
	version 4, created 1563906191, md5len 0, sigclass 0x13
	digest algo 8, begin of digest f1 10
	hashed subpkt 27 len 1 (key flags: 03)
	hashed subpkt 9 len 4 (key expires after 2y0d0h0m)
	hashed subpkt 11 len 4 (pref-sym-algos: 9 8 7 2)
	hashed subpkt 21 len 5 (pref-hash-algos: 8 9 10 11 2)
	hashed subpkt 22 len 3 (pref-zip-algos: 2 3 1)
	hashed subpkt 30 len 1 (features: 01)
	hashed subpkt 23 len 1 (keyserver preferences: 80)
	hashed subpkt 33 len 21 (issuer fpr v4 D9C6901F45C9B86858687DFF28A39BC32074BE7A)
	hashed subpkt 2 len 4 (sig created 2019-07-23)
	hashed subpkt 25 len 1 (primary user ID)
	subpkt 16 len 8 (issuer key ID 28A39BC32074BE7A)
	data: [4095 bits]

Edit to add:

OK, updated the key by the following:

$ gpg --keyserver keys.openpgp.org --receive-keys 28A39BC32074BE7A

Re-doing the export etc

$ gpg -a --export "19.07"| gpg --list-packets 
# off=0 ctb=99 tag=6 hlen=3 plen=525
:public key packet:
	version 4, algo 1, created 1563103655, expires 0
	pkey[0]: [4096 bits]
	pkey[1]: [17 bits]
	keyid: 28A39BC32074BE7A
# off=528 ctb=b4 tag=13 hlen=2 plen=83
:user ID packet: "OpenWrt Build System (PGP key for 19.07 release builds) <pgpsign-19.07@openwrt.org>"
# off=613 ctb=89 tag=2 hlen=3 plen=599
:signature packet: algo 1, keyid 28A39BC32074BE7A
	version 4, created 1563906191, md5len 0, sigclass 0x13
	digest algo 8, begin of digest f1 10
	hashed subpkt 27 len 1 (key flags: 03)
	hashed subpkt 9 len 4 (key expires after 2y0d0h0m)
	hashed subpkt 11 len 4 (pref-sym-algos: 9 8 7 2)
	hashed subpkt 21 len 5 (pref-hash-algos: 8 9 10 11 2)
	hashed subpkt 22 len 3 (pref-zip-algos: 2 3 1)
	hashed subpkt 30 len 1 (features: 01)
	hashed subpkt 23 len 1 (keyserver preferences: 80)
	hashed subpkt 33 len 21 (issuer fpr v4 D9C6901F45C9B86858687DFF28A39BC32074BE7A)
	hashed subpkt 2 len 4 (sig created 2019-07-23)
	hashed subpkt 25 len 1 (primary user ID)
	subpkt 16 len 8 (issuer key ID 28A39BC32074BE7A)
	data: [4095 bits]
# off=1215 ctb=89 tag=2 hlen=3 plen=599
:signature packet: algo 1, keyid 28A39BC32074BE7A
	version 4, created 1628534601, md5len 0, sigclass 0x13
	digest algo 8, begin of digest 85 86
	hashed subpkt 27 len 1 (key flags: 03)
	hashed subpkt 11 len 4 (pref-sym-algos: 9 8 7 2)
	hashed subpkt 21 len 5 (pref-hash-algos: 8 9 10 11 2)
	hashed subpkt 22 len 3 (pref-zip-algos: 2 3 1)
	hashed subpkt 30 len 1 (features: 01)
	hashed subpkt 23 len 1 (keyserver preferences: 80)
	hashed subpkt 25 len 1 (primary user ID)
	hashed subpkt 33 len 21 (issuer fpr v4 D9C6901F45C9B86858687DFF28A39BC32074BE7A)
	hashed subpkt 2 len 4 (sig created 2021-08-09)
	hashed subpkt 9 len 4 (key expires after 3y27d7h15m)
	subpkt 16 len 8 (issuer key ID 28A39BC32074BE7A)
	data: [4095 bits]

Key is no longer expired - (sig created 2021-08-09), (key expires after 3y27d7h15m)

Redo check of sha256sums signature

$ gpg --verify sha256sums.asc
gpg: assuming signed data in 'sha256sums'
gpg: Signature made Mon 09 Aug 2021 22:49:08 CEST
gpg:                using RSA key D9C6901F45C9B86858687DFF28A39BC32074BE7A
gpg: Good signature from "OpenWrt Build System (PGP key for 19.07 release builds) <pgpsign-19.07@openwrt.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: D9C6 901F 45C9 B868 5868  7DFF 28A3 9BC3 2074 BE7A


From:

PGP key for 19.07 release builds

User ID: OpenWrt Build System pgpsign-19.07@openwrt.org
Public Key: 0x28A39BC32074BE7A (4096 Bit RSA, created 2019-07-14, expires 2022-08-09)
Fingerprint: D9C6 901F 45C9 B868 5868 7DFF 28A3 9BC3 2074 BE7A
Last change: 2021-08-09 21:30:39 +0200 | Download

I second 20% wifi throughput increase :clap: :clap:
For 1 cpu Archer A7 v5 On 80Mhz wide channel I get ~440 Mbits/sec on 19.07.8 as measured by iperf3

1 Like

anyone try wrt32x yet on this? im literally never going to 21.02 it was a complete shit show and I ended up having to go get a spare router for a AP luckily found davidc502 builds on waybackmachine so running his latest ancient build. wouldnt mind giving it one more push forward before I go x86 lol

I upgraded my WRT1200 without any issue.

And I have a dual 2.4/5GHz SSID setup, plus a VPN SSID (Cyberghost) based on source policy routing.

No issue to report, after one week. All. fine. Just need to have all packages up to date. And keep every config files :slight_smile:

I'll consider going 21, but I'm cautious on this ...

installed on CF e320n-V2 and has been stable for around 1 week now.

r7800 looks stable after this.
I just figured out that Software Flow Offloading on the R7800 breaks some vital functionality that I have with port forwarding becoming dog-slow. Disabling Software Flow Offloading allows my LAN-WAN sftp to work, otherwise everything comes to a screeching halt at 7kbps...
I cannot load my Synology DiskStation's web portal from the WAN side with Software offloading enabled.
Apart from that all is great.

Thanks for the hardwork!

I'm on the wrt3200 which is almost identical with no issues.
Like you I'm nervous about 21, although one regular poster here reports that snapshots from master work fine

Try the ramfs image via uart/serial first. That way you don't change anything on the flash chip and still reboot the old config if the new version doesn't work.

21.02, and even better the lastest master on kernel 5.10, was a big improvement for my WRT32X, in everything except wifi. The wifi stalls out occationally now which never happened in 19.07 branch. There must be a bug somewhere and with less people using mvebu (because of mwlwifi being abandoned) may be unresolved. I might just get a wifi 6 ap (e.g. U6-Lite-US) and keep the router on master snapshot. Overall I think it's a very worthy upgrade update though and I wouldn't go back to 19.07 even though it was rock solid.

1 Like

19.07.8 with custom compiled wifi driver and properly working ipv6 still much faster than stock 21.02.0

1 Like

Anyone running 19.07 on TP-Link A7 v5 that can share wifi performance metrics on 5GHz ?
Trying to decide if this works better than the master build.

Running stock 19.07.8 on A7 v5 as an AP in one house, main in another. Extremely stable on both 2.4 and 5.

Easybox 802 (Arcadian752dpw) USB ports are now powered on ( Activated power supply to USB ports). There is no switch in all 19.07 versions.

I'n trying to connect USB. Device is visible as /mnt/sda1 but ls /mint/sda1 shows nothing.
Packages for USB NTFS and others mounted.
I Will try tomorrow.

I've observed random reboots on the R7800 running v19.07.8 after days of uptime (last one just an hour ago). Previous was perhaps 20 days back. But it has happened in a span of less than 10 days as well.

I had the same thing until I changed the performance governor, see e.g. here:
[19.07] R7800 random reboots - Installing and Using OpenWrt - OpenWrt Forum

Is 19.07.9 out yet, as I can find the release but no announcement: https://downloads.openwrt.org/releases/19.07.9/targets/ar71xx/mikrotik/

Not yet...

In general, a new OpenWrt version isn't technically released until an official announcement is made.

The technicality is important because the build may not actually be complete. It is possible that images for some devices may not be ready, or maybe certain packages will not have finished building. There is also a small possibility that an issue may arise in the build process that causes the build to fail for some targets or packages.

Therefore, just wait until the official announcement is made (should be pretty soon -- usually just a few days after the build-bots start compiling/building a newly tagged stable release version).

2 Likes

19.07.9 has been officially announced today

3 Likes