From: Vagrant Cascadian <vagrant@debian.org>
To: Raghav Gururajan <raghavgururajan@disroot.org>,
Giovanni Biscuolo <g@xelera.eu>,
help-guix@gnu.org
Subject: Re: Passwords inside System Configuration
Date: Tue, 21 Jan 2020 13:24:24 -0800 [thread overview]
Message-ID: <87r1zsy03b.fsf@ponder> (raw)
In-Reply-To: <d94d9e79f851e540bdc9bc41f3d2ee6b2fa4f452.camel@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
On 2020-01-21, Raghav Gururajan wrote:
>> 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?
I'm no expert, but evaluating the future based on today has it's
weaknesses; brute-force isn't usually what makes it possible to
compromise an algorithm...
https://valerieaurora.org/hash.html
According to wikipedia, SHA-512 is in the SHA2 family:
https://en.wikipedia.org/wiki/SHA-2
Which outlines papers, some going back over a decade, on various ways
SHA2 could be weakened...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-01-21 21:24 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
2020-01-21 21:24 ` Vagrant Cascadian [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1zsy03b.fsf@ponder \
--to=vagrant@debian.org \
--cc=g@xelera.eu \
--cc=help-guix@gnu.org \
--cc=raghavgururajan@disroot.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.