* passwd(1): These commands may be run only on a terminal
@ 2015-05-03 4:23 sl
2015-05-03 16:31 ` [9front] " cinap_lenrek
0 siblings, 1 reply; 2+ messages in thread
From: sl @ 2015-05-03 4:23 UTC (permalink / raw)
To: 9front
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [9front] passwd(1): These commands may be run only on a terminal
2015-05-03 4:23 passwd(1): These commands may be run only on a terminal sl
@ 2015-05-03 16:31 ` cinap_lenrek
0 siblings, 0 replies; 2+ messages in thread
From: cinap_lenrek @ 2015-05-03 16:31 UTC (permalink / raw)
To: 9front
i only see auth/login to warn when run on a cpu and netkey to
refuse to work on a cpu. which commands need to be changed?
--
cinap
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-05-03 16:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-03 4:23 passwd(1): These commands may be run only on a terminal sl
2015-05-03 16:31 ` [9front] " cinap_lenrek
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).