[DNG] Post install disk partitioning/encryption
Hi All, We have a "tasksel" for software that we can run after install. Is there something similar for the disk partitioning/encryption part of install? I finally figured out how to do an install with 2 disks (SSD and spin), both encrypted and asking for passphrases at boot. The spin disk promptly died during testing. Since I’ve already figured out how to use the install partitioning interface, I’m hoping there’s a way to re-access it after install like you can tasksel. Secondary Q: Is there a reason the install process isn’t setting up or triggering decrypt_keyctl [1] if the passphrases are the same for all disks? (Or more appropriately having a selection box to enable.) Thanks, Michael [1] https://unix.stackexchange.com/questions/392284/using-a-single-passphrase-to-unlock-multiple-encrypted-disks-at-boot ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Devuan on the Librem5 devkit
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 My devuan Images can boot on the librem5 devkit now. A lot of things, like the lcd display, don't work yet, but I'm working on it. A uart adapter is required to access the linux console, which is currently the only way to access the image after it has been flashed. The build scripts can be found here: * https://github.com/Daniel-Abrecht/librem5-image-builder * https://gitlab.com/DanielAbrecht/librem5-image-builder If anyone has cloned my repos before already, I recommend doing a "make reset", or at least a "make reset-repo" before rebuilding the images to make sure all repos are up-to-date. I also recommend doing a "make reset-repo@linux" and "make reset-repo@uboot" from time to time, to get the latest kernel & uboot, the repos are active at the moment. There is still a lot to do, I'll keep y'all updated. Regards, Daniel Abrecht -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEZT8xKpcJ1eXNKSM1cASjafdLVoEFAlwqhcwACgkQcASjafdL VoE5qggAoA2dq+9lpgoEONU6DwDlehxWP7iXkUFt0uLIFn0Cr+jxjn+K9Wc6jPdy TBb2ujZcgN7oVVVbQnffKVcknyC0ISpio1y137J4teKDdK6XR35H318ept41lpMx 9PpgPx0/HxyZjW5WELN3AsFJJHbc50MFiU706tRW0dYLvhXqw+f5NcQSeQm0ddDe 9ar4IDI4ELWV+r+83BmJDMUhfmkK67XW1b3c0B1UD5ng3998EMHttKefflHI6zDs hKVQ6NWlbKMSUa8dEUSm8d4G/YMlWE0IKdhGfiYjsRDk7g4G5S3HXuBUml+NWzF3 /j7uuAYjmjIgfq4Z0Toobi/qJadDfw== =CNLF -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Admins can you fix/set the header overrides?
Quoting KatolaZ (kato...@freaknet.org): > I might have missed something, but there is no need to speculate: it's > sufficient to have a look at the headers of emails posted on DNG. Most > of them do not have a Reply-To: header set, which means that Mailman > does not add anything (there is a config option to do that, but it's > quite annoying TBH). Bless you for trying to help, Enzo, but I think you've addressed an entirely different question from the one Hendrik just raised. Hendrik was hoping that Mailman's DMARC mitigation would not discard a poster's existing Reply-To: header in cases where Mailman appends one of its own pointing back to the poster. In reply, I was citing reasons to expect it will not discard such a header. As I've already explained, Dng's Mailman configuration has been, since December 6th, munging the From: header in cases where the poster's domain has a DMARC policy of p=reject or p=quarantine, and _only_ in such cases. For your reference, in Mailman v. 2.1.18 and later admin webUI screens (Dyne.org's current version being 2.1.23), this is on page Privacy Options, Sender Filters, item 'Action to take when anyone posts to the list from a domain with a DMARC Reject/Quarantine Policy' aka dmarc_moderation_action. Applying the mitigation Mailmna's developers recommend consists of changing default radio button 'Accept' to "Munge From'. And then one also changes 'dmarc_quarantine_moderation_action)' to Yes. Mailman's developers no longer recommend the similar-looking setting 'Replace the From: header address with the list's posting address to mitigate issues stemming from the original From: domain's DMARC or similar policies' aka from_is_list on page General Options: Opting for that (older) version of Mailman's munging kludge unconditionally applies it to all postings whether they are from DMARC-encumbered domains or not. You may or may not recall that we discussed all of these matters on Devuan-dev in a couple of threads starting October 29th. It took until December 6th for action to be taken, but we went through the matter a few times in discusison. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Admins can you fix/set the header overrides?
On Sun, Dec 30, 2018 at 01:18:18PM -0800, Rick Moen wrote: > Quoting Hendrik Boom (hend...@topoi.pooq.com): > > > I hope it doesn't add a reply-to header if there's already one. > > I can't say for certain, but it's likely GNU Mailman would (in that > case) add the poster's real address as an additional address within the > existing Reply-To: address (if they even differ). > I might have missed something, but there is no need to speculate: it's sufficient to have a look at the headers of emails posted on DNG. Most of them do not have a Reply-To: header set, which means that Mailman does not add anything (there is a config option to do that, but it's quite annoying TBH). My2Cents KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
