From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] Should stats(1) support rcpu(1)?
Date: Thu, 18 Feb 2016 03:27:05 +0100 [thread overview]
Message-ID: <37cdcd54c24d4ec1815fed38d2383f9d@felloff.net> (raw)
In-Reply-To: <e7ccabcde07c03a90ef0165ab02fc0d8@ghost.attlocal.net>
yes. it should just run rimport $sysname / /n/$sysname to get the other machines
mounted. that way the connection will get encrypted properly, currently it isnt.
the problem with not encrypting is that someone could hijack the connection and
access arbitrary shit with your credentials. if its encrypted he cannot do anything
with the connection :-)
at some point, we can disable the old exportfs listen script and rename import
and cpu to /bin/unimportant and /bin/cpikachu
--
cinap
prev parent reply other threads:[~2016-02-18 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 0:50 sl
2016-02-18 1:58 ` [9front] " Steve Simon
2016-02-18 2:27 ` cinap_lenrek [this message]
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=37cdcd54c24d4ec1815fed38d2383f9d@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).