From: Raghav Gururajan <raghavgururajan@disroot.org>
To: Giovanni Biscuolo <g@xelera.eu>, help-guix@gnu.org
Subject: Re: Passwords inside System Configuration
Date: Tue, 21 Jan 2020 15:45:37 -0500 [thread overview]
Message-ID: <d94d9e79f851e540bdc9bc41f3d2ee6b2fa4f452.camel@disroot.org> (raw)
In-Reply-To: <87zheipghw.fsf@roquette.mug.biscuolo.net>
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
Hello Giovanni!
> --8<---------------cut here---------------start------------->8---
> (user-account
> (name "charlie")
> (group "users")
>
> ;; Specify a SHA-512-hashed initial password.
> (password (crypt "InitialPassword!" "$6$abc")))
> --8<---------------cut here---------------end--------------->8---
Thanks! But how do I do this for 'root' user as well?
> but please read
> https://guix.gnu.org/manual/en/html_node/User-Accounts.html#user_002daccount_002dpassword
OOPS! I somehow missed it. Thanks for letting me know.
> You would normally leave this field to #f, initialize user passwords
> as
> root with the passwd command, and then let users change it with
> passwd. Passwords set with passwd are of course preserved across
> reboot
> and reconfiguration.
Yes, but I wanted to do things in declarative way.
> Note: The hash of this initial password will be available in a file
> in
> /gnu/store, readable by all the users, so this method must be used
> with
> care.
I see. But why would it be a concern? It is not feasible to brute-force
SHA-512 hash right?
> > 3) LUKS Device
>
> AFAIK it's not possible to provide the passphrase in the system
> configuration, and it's by design :-)
Hmm, I have heard of a way to embed the passphrase in 'initrd'. Do you
know how to do that?
Thank you!
Regards,
RG.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-01-21 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 11:20 Passwords inside System Configuration Raghav Gururajan
2020-01-20 10:31 ` Giovanni Biscuolo
2020-01-21 20:45 ` Raghav Gururajan [this message]
2020-01-21 21:24 ` Vagrant Cascadian
2020-01-23 1:36 ` Raghav Gururajan
2020-01-24 20:53 ` Giovanni Biscuolo
2020-01-25 0:34 ` Raghav Gururajan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d94d9e79f851e540bdc9bc41f3d2ee6b2fa4f452.camel@disroot.org \
--to=raghavgururajan@disroot.org \
--cc=g@xelera.eu \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).