a calendar thingy for anyone/@ll in devuan core team with access to the key, should be easy to do. (to save same trouble next year.)

ralph, users do not have access to gpg keys, nor do they sign packages with that key "everyday", nor do they run `apt-key list` everyday....
i think it's mostly up to the core team to just put some reminders on key/security processes.
yes, users can help, but you should not rely on others noticing in the first place for core/critical(imho), things.

2c.

not using palemoon. in basilisk i would add a string in about:config, eg :
preference name : general.useragent.override.discourse.pi-hole.net
value : Mozilla/5.0 (Windows NT 6.1; rv:42.0) Gecko/20100101 Firefox/91.0

and that would usually override discourse crap. used it a couple of times, i had to use discourse. you can try to see if it works with palemoon, and then add new strings for other discourse fora too.

a "full report", but no details. so, questions :

• what devuan iso? does the iso checks out ok? (md5sum?)

• did you burn iso in usb from legacy boot or uefi?

• what wifi card? what firmware? cause devuan includes non-free firmware by default as stated in latest release notes : https://files.devuan.org/devuan_chimaer … _notes.txt

• network manager applications like connman or network-manager get installed by installer, providing you choose a DE on installation.. eg. xfce recommends network-manager... so it should be there on default installation..

just a blind guess: bad/not fully downloaded iso or bad USB or something else..

edit] re-read, so network-install without network, doesn't work as expected.. better choose a full iso next time..

2c.

binaries are generally here : https://ungoogled-software.github.io/un … -binaries/
appimage is updated, debian package is still older..
--
repo error is about expired gpg signing, url is correct.

(no obfs4proxy)
so, purged both tor + apparmor and reinstalled with defaults, but same error on boot. removed apparmor and tor starts again normally.. didn't try another boot without apparmor installed, but will probably file a bug with tor since that package provides apparmor profile and reinstalling tor is a "workaround" for some reason..

just wanted to know if its reproducible in other systems with runit+tor+apparmor.. this behavior started since latest runit upgrade in ceres, so i thought i asked you first if it's connected to the latest upgrade somehow.. (?)

https://dev1galaxy.org/viewtopic.php?pid=36517#p36517

after new boot :

/etc/init.d/tor status
tor is not running ... failed!
➜  /etc/init.d/tor stop  
Stopping tor daemon...done (not running - there is no /run/tor/tor.pid).
➜  /etc/init.d/tor start
Starting tor daemon...[15690] aa-exec: ERROR: profile 'system_tor' does not exist

➜  sv status tor
down: tor: 1s, normally up, want up; run: log: (pid 1656) 933s
➜  sv stop tor
ok: down: tor: 1s, normally up, want up
➜  sv start tor
timeout: down: tor: 0s, normally up, want up

/etc/sv/tor/run 
Jul 05 12:34:04.739 [notice] Tor 0.4.7.8 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.4, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.5.2 and Glibc 2.33 as libc.
Jul 05 12:34:04.739 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Jul 05 12:34:04.739 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Jul 05 12:34:04.739 [notice] Read configuration file "/etc/tor/torrc".
Configuration was valid
[17313] aa-exec: ERROR: profile 'system_tor' does not exist

 apt install --reinstall tor
....
Preparing to unpack .../tor_0.4.7.8-1_amd64.deb ...
Unpacking tor (0.4.7.8-1) over (0.4.7.8-1) ...
Installing tor (0.4.7.8-1) ...
ok: run: tor: (pid 17844) 0s
.....
Stopping tor daemon...done.
Starting tor daemon...done (already running).
Processing triggers for man-db (2.10.2-1) ...

sv status tor
run: tor: (pid 17895) 15s; run: log: (pid 1656) 1032s

using it as a daily driver since 2005 (debian sid - devuan ceres since 2017). a few breakings over the years, some serious (=unbootable systems), but overall a nice experience.. so you need a good apt/debian knowledge-experience in order to workaround possible bugs.
if you need a mix of newer software + some better stability, you can always go with testing/daedalus. or use stable with some apt pin for specific packages from unstable (in case they don't need newer libc6 or some other critical upgrade).

i don't understand the essence of most linux distributions, but still not judging anyone.. people are free to do volunteer work/hobby as they like and announce it in relevant forums..

but more importantly, i don't understand the criticism in this particular one (?) wtf?
someone is doing work based on / around Devuan and people repell it for no apparent reason... is there something i don't know about this one? or someting's wrong with you people? you criticise a devuan derivative based on website graphics and a debian mention? really?

tip: dont turn this forum into the toxic thing DNG is..
disclaimer, dont know, haven't tried, aint affiliated, nor,  nor, nor,..... with this derivative distro.

2c, (and a step away from quitting forum too).

@golinux, not secure because of a video still served from a staging environment :
http://lionlinux-com.stackstaging.com/w … bution.mp4
mixed content is(was?) most common reason for non-secure sites, but it's not always something scary..
but anyway....

website start page mentions debian as base, but a look inside (or sourceforge), mentions clearly the new devuan base : https://lionlinux.com/versions-control/

Connection Options.
if you already connected virt-manager to local libvirtd : choose that (qemu:///system) connection and :
(menu) Edit -> Connection Details -> Virtual Networks tab -> choose network, and check "Autostart On Boot"  on network Details.

`apt remove --purge` is the same as `apt purge`.
---

if you're not purging (cancelling request or whatever) then what are you doing? you need to post full commands and output. if you already reinstalled at some point, it's not mentioned in your steps in original post..
if you're purging slim, you should only have one choice (lightdm). if you see both slim+lightdm, then `purge slim` didn't work/failed (or there is a bug indeed)... so we'll need the full steps/output to debug.

2c.