From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: 9front@9front.org
Subject: first 24B in /adm/keys
Date: Sat, 12 Nov 2016 20:36:00 +0900 [thread overview]
Message-ID: <A89C5B72-4CDE-42D3-A236-56FB04C813C1@ar.aichi-u.ac.jp> (raw)
hello cinap,
I have been in trouble since last updating. perhaps I did something stupid.
I wanted to initialize /adm/keyfs so that dp9ik can work.
however I couldn’t find the description for that in manual.
I looked /sys/src/cmd/auth/keyfs.c to fix the problem and found:
term% echo AES KEYS0123456789012345>/adm/keys
term% >/adm/keys.who
can initialize /adm/keys in dp9ik format.
but I am uneasy because I don’t know 0123456789012345 ( referred as iv[16] in comment in keyfs.c) is OK or not.
what is intended for iv[16] and what is recommended value for it?
it seems the content in iv[16] is not checked in current code, however future code may check it.
Kenji Arisawa
next reply other threads:[~2016-11-12 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 11:36 arisawa [this message]
2016-11-12 13:27 ` [9front] " cinap_lenrek
2016-11-13 3:05 ` 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=A89C5B72-4CDE-42D3-A236-56FB04C813C1@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--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).