Re: [DNG] Configuring ethernet port for IPv6
On Mon, Sep 05, 2022 at 11:47:33AM -0400, Curtis Maurand wrote: > I think this is all great right up until you need a fixed address for > something like a mail server or a web server. So far, I've found IPV6 to be > unreliable. I would argue it's easier to get a fixed address with IPv6 than it is with IPv4. If a provider is using mobile IPv6 to hand out addresses, or is doing something else preventing users from having a fixed static IPv6 subnet this is the fault of that provider, and not a deficiency of the IPv6 protocol. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] meta: list
Hi Simon, On Sun, 2022-09-04 at 21:22 +0100, Simon Hobson wrote: > declassed art via Dng wrote: > > > I do have an unconfigured PTR for a couple of reasons, one > > of those is lack of static IP for now. > > I figured out quite quickly that checking reverse DNS is a waste of > time - too many systems, even those run by professional > network/server engineers, are just badly configured. > My experience (running a small family mail server on the premises, but of course with a fixed IP - I'm with Zen in the UK) is the opposite of this. I configure strict postfix rules that incoming mail should have a reverse DNS. Here's my recent traffic: 3490 received 3444 delivered 43 forwarded 1 deferred (1 deferrals) 0 bounced 1799 rejected (34%) Of those rejected: 974 Cannot find your reverse hostname 283 Helo command rejected: Host not found 251 Cannot find your hostname 23 Helo command rejected: need fully-qualified hostname 16 Recipient address rejected: User unknown Message that pass my postfix filters are then scored by my spamfilter rspamd: 222 Rejected by rspamd (mix of 4.7.1 try again later or 5.7.1 spam message rejected). In practice most greylisted 'try again laters' that do try again then end up in the users spam folders for them to evaluate and if necessary recategorise. So checking for a valid reverse DNS is my most effective filter. Only very rarely is it rejecting mail from anyone I'm expecting mail from: by inspection they are all obvious spam addresses and of course if they have a genuine reason to email me they are getting the message that their mail isn't getting through because they have no reverse DNS. -- Marjorie ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] chimaera install problem
On Tue, 2022-09-06 at 17:46 +0100, Peter Duffy wrote: > Ralph, thanks for the workaround - it worked fine. I had been trying > something similar, but I'd forgotten about the chroot. (Or to coin a phrase, close but no ch(e)root ;) ) ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Key is expired
I also had to manually delete the previous key in order for this to work: apt-key del "E032 601B 7CA1 0BC3 EA53 FA81 BB23 C00C 61FC 752C" After that: wget http://deb.devuan.org/devuan/pool/main/d/devuan-keyring/devuan-keyring_2022.09.04_all.deb sudo dpkg -i devuan-keyring_2022.09.04_all.deb sudo apt update Just spent that last few hours updating all our Devuan servers. May want to put this information on the home page or something. Chris On 9/3/22 11:27, Ludovic Bellière via Dng wrote: > Hello list, > > In order to resolve the gpg key being outdated, the following steps needs to > be taken: > > wget > http://deb.devuan.org/devuan/pool/main/d/devuan-keyring/devuan-keyring_2022.09.04_all.deb > sudo dpkg devuan-keyring_2022.09.04_all.deb > sudo apt update > > Cheers, > Ludovic > > > On Sat, 03 Sep 2022, Elimar Riesebieter wrote: > >> >> Hi all, >> >> the signing key 'Devuan Repository (Amprolla3 on Nemesis)' is >> expired: >> >> W: GPG error: http://deb.devuan.org/merged stable InRelease: The following >> signatures were invalid: EXPKEYSIG BB23C00C61FC752C Devuan Repository >> (Amprolla3 on Nemesis) >> >> Elimar > > -- > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] chimaera install problem
On Tue, 2022-09-06 at 23:02 +1000, Ralph Ronnquist wrote: > > The required hands-on to make use of the current installer ISOs > includes the use of wget and dpkg at the point where the installation > first breaks, though probably only via a C-A-F2 escape to a root > shell > while the installation (at C-A-F1) is blocked and waiting on the > error > report dialog. > > At that point you use wget to grab the devuan-keyring package > http://deb.devuan.org/merged/pool/DEVUAN/main/d/devuan-keyring/devuan-keyring_2022.09.04_all.deb > and store that at /target, so you can follow up with manual > installation into /target, by: > # chroot /target /usr/bin/dpkg -i devuan-keyring_2022.09.04_all.deb > > Following that, you re-enter the installation at C-A-F1 and select > "continue" so that it re-tries with the failing step using the the > updated keyring. > > On the side of all that I should add that I also taken have the > opportunity to polish the installer-iso project so that it easily > builds ISOs for the old releases. Some trial builds of that are > currently available for testing at https://ido.rrq.id.au/download Ralph, thanks for the workaround - it worked fine. I had been trying something similar, but I'd forgotten about the chroot. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] chimaera install problem
On Tue, Sep 06, 2022 at 03:53:08PM +0200, Adrian Zaugg wrote: > In der Nachricht vom Tuesday, 6 September 2022 15:02:47 CEST steht: > > At that point you use wget to grab the devuan-keyring package > > http://deb.devuan.org/merged/pool/DEVUAN/main/d/devuan-keyring/devuan-keyrin > > g_2022.09.04_all.deb and store that at /target, so you can follow up with > > manual > > installation into /target, by: > > # chroot /target /usr/bin/dpkg -i devuan-keyring_2022.09.04_all.deb > There is neither curl, wget nor dpkg available in the netinst iso, at least > not in daedalus and presumably not in chimaera either. I must say that you are mistaken about that. "/usr/bin/wget" is available in the installer itself, and "/usr/bin/dpkg" is available in the installed base system (i.e. chroot /target) Ralph. > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] chimaera install problem
In der Nachricht vom Tuesday, 6 September 2022 15:02:47 CEST steht: > At that point you use wget to grab the devuan-keyring package > http://deb.devuan.org/merged/pool/DEVUAN/main/d/devuan-keyring/devuan-keyrin > g_2022.09.04_all.deb and store that at /target, so you can follow up with > manual > installation into /target, by: > # chroot /target /usr/bin/dpkg -i devuan-keyring_2022.09.04_all.deb There is neither curl, wget nor dpkg available in the netinst iso, at least not in daedalus and presumably not in chimaera either. Regards, Adrian. signature.asc Description: This is a digitally signed message part. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] chimaera install problem
On Tue, Sep 06, 2022 at 01:14:06PM +0100, Peter Duffy wrote: > Adrian and Olaf - thanks for the comments. > > This is definitely the expired key problem - so at the moment, chimaera > can't be installed via the netinstall image. Probably the same for > other devuan versions. > > Adrian - I tried changing the date as you suggested. That doesn't work > - I now get a message in the log saying: > > "http://deb.devuan.org/merged/dists/chimaera/InRelease is not valid > yet" > > I found that I could get the install to complete if I told it to ignore > the error, and the resulting system would boot. However, it's obviously > just the bare-bones base system from the netinstall image. > > Are the netinstall images going to be re-generated fairly soon? If not, > is it worth while thinking of a way of importing the new key into the > install process? The required hands-on to make use of the current installer ISOs includes the use of wget and dpkg at the point where the installation first breaks, though probably only via a C-A-F2 escape to a root shell while the installation (at C-A-F1) is blocked and waiting on the error report dialog. At that point you use wget to grab the devuan-keyring package http://deb.devuan.org/merged/pool/DEVUAN/main/d/devuan-keyring/devuan-keyring_2022.09.04_all.deb and store that at /target, so you can follow up with manual installation into /target, by: # chroot /target /usr/bin/dpkg -i devuan-keyring_2022.09.04_all.deb Following that, you re-enter the installation at C-A-F1 and select "continue" so that it re-tries with the failing step using the the updated keyring. On the side of all that I should add that I also taken have the opportunity to polish the installer-iso project so that it easily builds ISOs for the old releases. Some trial builds of that are currently available for testing at https://ido.rrq.id.au/download Ralph. > > On Mon, 2022-09-05 at 16:49 +0100, Peter Duffy wrote: > > Sorry if this has been addressed before - I did look through the > > posts, > > but couldn't see anything relevant. Also sorry if I'm missing > > something > > obvious. > > > > I'm trying to install chimaera on a virtualbox VM, using the > > netinstall > > image (devuan_chimaera_4.0.0_amd64_netinstall.iso, dated Nov 18 2021) > > - > > I've done this many times before, without a problem. This time, when > > I > > get to "configure the packet manager", it comes back with "The > > installer failed to access the mirror". I used wireshark to check > > that > > it's talking to the network and the server - it appears to be doing > > so > > (accessing server at 95.216.15.86). > > > > I'm wondering if it could be another effect of the recent key expiry > > problem. > > > > > > > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] chimaera install problem
Hi Peter Good if your new system boots up afterwards! Go to a console and run as root tasksel --new-install and complete the installation like this. If you're missing other packages install them with apt, e.g. apt install openntpd ...to have time synchronisation. Regards, Adrian. In der Nachricht vom Tuesday, 6 September 2022 13:10:47 CEST steht: > Hi Adrian > > I tried changing the date as you suggested. That doesn't work - I now > get a message in the log saying that > "http://deb.devuan.org/merged/dists/chimaera/InRelease is not valid > yet" > > If I tell the install to ignore the error and continue, it completes > and the system boots successfully - but obviously that's only a very > basic system. > > I've been trying to install the new devuan-keyring package via one of > the console sessions during installation - but I think there are too > many missing and conflicting dependencies. > signature.asc Description: This is a digitally signed message part. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] chimaera install problem
Adrian and Olaf - thanks for the comments. This is definitely the expired key problem - so at the moment, chimaera can't be installed via the netinstall image. Probably the same for other devuan versions. Adrian - I tried changing the date as you suggested. That doesn't work - I now get a message in the log saying: "http://deb.devuan.org/merged/dists/chimaera/InRelease is not valid yet" I found that I could get the install to complete if I told it to ignore the error, and the resulting system would boot. However, it's obviously just the bare-bones base system from the netinstall image. Are the netinstall images going to be re-generated fairly soon? If not, is it worth while thinking of a way of importing the new key into the install process? On Mon, 2022-09-05 at 16:49 +0100, Peter Duffy wrote: > Sorry if this has been addressed before - I did look through the > posts, > but couldn't see anything relevant. Also sorry if I'm missing > something > obvious. > > I'm trying to install chimaera on a virtualbox VM, using the > netinstall > image (devuan_chimaera_4.0.0_amd64_netinstall.iso, dated Nov 18 2021) > - > I've done this many times before, without a problem. This time, when > I > get to "configure the packet manager", it comes back with "The > installer failed to access the mirror". I used wireshark to check > that > it's talking to the network and the server - it appears to be doing > so > (accessing server at 95.216.15.86). > > I'm wondering if it could be another effect of the recent key expiry > problem. > > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] chimaera install problem
Hi Peter, Peter Duffy writes: > Sorry if this has been addressed before - I did look through the posts, > but couldn't see anything relevant. Also sorry if I'm missing something > obvious. > > I'm trying to install chimaera on a virtualbox VM, using the netinstall > image (devuan_chimaera_4.0.0_amd64_netinstall.iso, dated Nov 18 2021) - > I've done this many times before, without a problem. This time, when I > get to "configure the packet manager", it comes back with "The > installer failed to access the mirror". I used wireshark to check that > it's talking to the network and the server - it appears to be doing so > (accessing server at 95.216.15.86). > > I'm wondering if it could be another effect of the recent key expiry > problem. I'd start a shell in the installer environment (or switch to a VT) and poke in the various logs to see more details. -- Olaf Meeuwissen ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] meta: list
> Maybe related news, and some more reading: > > https://www.jwz.org/blog/2022/08/today-in-google-broke-email/ No, it is not related, he just needs to get SRS implemented. Regards, Adrian. signature.asc Description: This is a digitally signed message part. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] chimaera install problem
Hi Peter This is because package verification fails, you can see this in the console log. Devuan has forgotten to renew its signing key on time, which is major fault. All install images need to be regenerated but it seems that hasn't been done. A workaround, not a nice one, is to set your clock to a date before the key was expired. Unfortunately you can't update the repository signing key in the installer env the way it was posted here. Change to a console with alt-F2, hit enter to activate it, and set the date using: date -s "2022-08-31" ...then try again to configure the package manager. Regards, Adrian. In der Nachricht vom Monday, 5 September 2022 17:49:23 CEST steht: > Sorry if this has been addressed before - I did look through the posts, > but couldn't see anything relevant. Also sorry if I'm missing something > obvious. > > I'm trying to install chimaera on a virtualbox VM, using the netinstall > image (devuan_chimaera_4.0.0_amd64_netinstall.iso, dated Nov 18 2021) - > I've done this many times before, without a problem. This time, when I > get to "configure the packet manager", it comes back with "The > installer failed to access the mirror". I used wireshark to check that > it's talking to the network and the server - it appears to be doing so > (accessing server at 95.216.15.86). > > I'm wondering if it could be another effect of the recent key expiry > problem. > > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- -°) (_^/ Adrian Zaugg Zweierstrasse 56 CH-8004 Zürich 044 291 02 38 (This eMail gets best displayed using a monospace font.) # Retrieve my public GPG key: gpg --locate-external-keys a...@ente.limmat.ch signature.asc Description: This is a digitally signed message part. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
