From: sl@9front.org
To: 9front@9front.org
Subject: passwd(1): These commands may be run only on a terminal
Date: Sun, 3 May 2015 00:23:48 -0400 [thread overview]
Message-ID: <55459fd59ac3c1faf5e94246c6e99a50@u2.inri> (raw)
From passwd(1):
BUGS
Now that cpu connections are always encrypted, the only good
reason to require that these commands be run only on termi-
nals is concern that the CPU server might be subverted.
Now that I am providing cpu accounts for some 9front developers, I have
a use case for allowing users to change their own passwords.
Should these commands be changed so that they may be run on cpu servers?
sl
next reply other threads:[~2015-05-03 4:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 4:23 sl [this message]
2015-05-03 16:31 ` [9front] " cinap_lenrek
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=55459fd59ac3c1faf5e94246c6e99a50@u2.inri \
--to=sl@9front.org \
--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).