bug: several warnings & fails in official install process

[avczar]

Describe the bug

Fresh Debian 13 installation done, then I'm running the installation sequence directly:

1. su -
2. apt install sudo
3. sudo usermod -aG sudo master
4. exit + exit (re-login)
5. sudo apt update -y
6. sudo apt install curl git unzip tar gpg -y (gpg is missing in step 2 of official doc)
7. curl -fsSL https://get.docker.com | sudo bash -

Usual warning about run as non-root user: https://i.goopics.net/sv59ag.jpg

8. sudo mkdir -p /etc/apt/keyrings
9. sudo mkdir /root/.gnupg
10. sudo gpg --no-default-keyring --keyring /etc/apt/keyrings/swiftwave.gpg --keyserver keyserver.ubuntu.com --recv-keys DD510C86CD3F6764

Warning about local keyring safety (I dont know why): https://i.goopics.net/k60v53.jpg (line 2)

11. echo "deb [signed-by=/etc/apt/keyrings/swiftwave.gpg] http://deb.repo.swiftwave.org/ swiftwave stable" | sudo tee /etc/apt/sources.list.d/swiftwave.list
12. sudo apt update -y

Fail: https://i.goopics.net/k60v53.jpg

I retried 2 times, and same result each time.

Thanks for help.

Are you working on this issue?

Yes

[tanmoysrt]

Warning about local keyring safety (I dont know why): i.goopics.net/k60v53.jpg (line 2)

Based on the image, it looks like the key hasn't been downloaded correctly.
Try again to download the key and also do check the file, if it's blank.

We use ubuntu keyserver for fetching the PGP keys, so it shouldn't be an issue until unless your network provider blocking HKP Protocol or something.

sudo gpg --no-default-keyring --keyring /etc/apt/keyrings/swiftwave.gpg --keyserver keyserver.ubuntu.com --recv-keys DD510C86CD3F6764

If this not working correcting, try another keyserver

sudo gpg --no-default-keyring --keyring /etc/apt/keyrings/swiftwave.gpg --keyserver keys.openpgp.org  --recv-keys DD510C86CD3F6764

[avczar]

Hi,

Same with keys.openpgp.org, but after new full install of Debian 13 and a network interface change. This time, seems no warn about repo safety, but can't still properly establish SSL connection to your server: "Download of some index files failed, so ignored, old ones use instead" (https://i.goopics.net/usm8i6.jpg)
I tried to install anyway in next step (sudo apt install swiftwave -y), but "impossible to find swiftwave."

I installed successful Dokploy, Coolify, CasaOS and Cosmos in other similar VMs (PVE9) with same config and Debian 13 too; I didn't have any problem with.

Thanks again.

[avczar]

I retested with Debian 13.1 minimal (like previously, w/o any module/desktop env), with getting key from ubuntu.com or openpgp.org, I'm always blocked at the same point, just before install swiftwave. Your repo seems not properly signed, or maybe integrity problem w/ your signature key... I did not make any copy and paste, every command was typed by hand each time (VM).
Check: https://i.goopics.net/naosip.jpg | Wrong last command to check gpg, fixed here: https://i.goopics.net/mbvb8t.jpg

---

And in doc, you should be more specific by fix and complete the instructions:

sudo apt install curl git unzip tar gpg -y
...
sudo mkdir -p -m 0755 /etc/apt/keyrings
sudo chmod 0644 /etc/apt/keyrings/*.gpg
sudo chown -R root:root /etc/apt/keyrings
sudo mkdir -m 0700 /root/.gnupg

[tanmoysrt]

I use Ubuntu 22.04/24.04 and never faced any issue like that before, maybe there are some security hardening on other os.
Raise a PR here - https://github.com/swiftwave-org/swiftwave.org for adding the extra setup steps.

[avczar]

Ubuntu 24.04 is still fairly tolerant about repositories sign/auth method, whereas Debian 13 already applies latest security rules in state-of-the-art. This will change in the next version of Ubuntu, so you will need to adapt your repo sooner or later to comply with the new requirements.