From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] first 24B in /adm/keys
Date: Sat, 12 Nov 2016 14:27:25 +0100 [thread overview]
Message-ID: <befb98db5c4df3427caade7072af99fb@felloff.net> (raw)
In-Reply-To: <A89C5B72-4CDE-42D3-A236-56FB04C813C1@ar.aichi-u.ac.jp>
keyfs writes a new file when you add/change users. when theres
no previous des format keydb, then it will always create a new
file in aes format as long as it has the aes key which it gets
from nvram or calculates itself from the password (-p flag) on
startup.
so, unless you use -p flag, make sure you have the aes key
stored in your nvram. you can do that with auth/wrkey.
whenever you change users in keyfs, it will reencrypt everything
and write a new file. it will also generate a new random iv
each time so the value you put there doesnt matter.
--
cinap
next prev parent reply other threads:[~2016-11-12 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 11:36 arisawa
2016-11-12 13:27 ` cinap_lenrek [this message]
2016-11-13 3:05 ` [9front] " arisawa
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=befb98db5c4df3427caade7072af99fb@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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 NNTP newsgroup(s).