From 0079c47c20284f5ed9c283b51f68b8ddad5a617e Mon Sep 17 00:00:00 2001 From: florian Date: Sat, 8 Jun 2024 06:05:40 +0000 Subject: [PATCH] Do not enforce the next version key if installing a snapshot. Developers sometimes have dev machines with an older snapshot that already has the correct signify key but sysupgrade(8) refuses to do an upgrade because it thinks it's a version jump. That's just silly. tb pointed out that signify(1) can just work out the correct key all by itself. problem reported, same diff & OK deraadt --- usr.sbin/sysupgrade/sysupgrade.sh | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/usr.sbin/sysupgrade/sysupgrade.sh b/usr.sbin/sysupgrade/sysupgrade.sh index 21094819592..a30d13fad2f 100644 --- a/usr.sbin/sysupgrade/sysupgrade.sh +++ b/usr.sbin/sysupgrade/sysupgrade.sh @@ -1,6 +1,6 @@ #!/bin/ksh # -# $OpenBSD: sysupgrade.sh,v 1.49 2023/10/12 12:31:15 kn Exp $ +# $OpenBSD: sysupgrade.sh,v 1.50 2024/06/08 06:05:40 florian Exp $ # # Copyright (c) 1997-2015 Todd Miller, Theo de Raadt, Ken Westerback # Copyright (c) 2015 Robert Peichaer @@ -139,16 +139,21 @@ unpriv -f SHA256.sig ftp -N sysupgrade -Vmo SHA256.sig ${URL}SHA256.sig _KEY=openbsd-${_KERNV[0]%.*}${_KERNV[0]#*.}-base.pub _NEXTKEY=openbsd-${NEXT_VERSION%.*}${NEXT_VERSION#*.}-base.pub -read _LINE