Anton Hvornum

> @Torxed did you start on this already? Otherwise I'd be interested in doing it if you're okay with that :) more than welcome to! ^^ I addes more colors...

> Are there already other ideas on how to improve it or how it should look like? Nothing really, but either a pre-parser in `log()` with regexp or something. Or...

@svartkanin just FYI, I moved it from v2.4.0 to v2.4.1. This is to reduce stress and v2.4.0 already contains [so many changes](https://github.com/archlinux/archinstall/releases/tag/v2.4.0.rc2) that it makes sense to split new functionality...

I'm pushing this back one more release as the main goal for 2.5.1 is to patch issues. Apologies if anyone got their hopes up, I was a bit to optimistic.

Well spotted @ysf and thank you for reporting @kpcyrd! `sys_command` should support it now days, I don't think it did way back when I was using `Popen()` due to the...

Appreciate that information and link, that's a cleaner way of doing I recon! I'll bring this into the re-work of `sys_command` once I get to it!

Just for my own sanity, piping the password in to `stdin` is the way to go. To avoid users reporting issues like this leaking the password if it's on the...

Hi. Just piping to let you guys know I haven't forgotten about this. And I feel archinstall is stable enough that I can start tinker with the encryption process in...

> /dev/stdin Unfortunately this does not work: > Cannot read keyfile from a terminal. Trying just a normal "type it in" approach since `SysCommandWorker()` supports that.

> Also hand up here ✋ > > After the installation, I see the plain text password in the `/var/log/archinstall/install.log` file: > > > Marking partition for use with encryption-key:...