From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] proposal: disable most of /rc/bin/services/tcp* by default
Date: Wed, 20 May 2015 22:34:51 +0200 [thread overview]
Message-ID: <2c054e0c3296713f66537c623a082f73@felloff.net> (raw)
In-Reply-To: <A6221413-9A09-4E9F-BFB9-6F517CD3FB2C@9.offblast.org>
i'm not against this, but what exactly is the problem? its not like
these services are usable unless you have an actual account on the
auth server (and created a mailbox for the user in case of imap/pop3).
this is not like unix where services run as "root" and then impersonate
some user on the system, but they start as "none" and cant do anything
(even if there are bugs) unless the user authenticates.
if you have an account, then you can as well cpu in and run commands.
what we really want is a authorization scheme that would allow us to
grant a user the services he can use on the system. right now its
a all or nothing. if you have an account you can use every service
in the network.
--
cinap
next prev parent reply other threads:[~2015-05-20 20:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 18:16 sl
2015-05-20 18:32 ` [9front] " cinap_lenrek
2015-05-20 18:36 ` Kurt H Maier
2015-05-20 20:10 ` mischief
2015-05-20 20:34 ` cinap_lenrek [this message]
2015-05-20 22:46 ` Kurt H Maier
2015-05-21 9:19 ` cinap_lenrek
2015-05-21 11:05 ` arisawa
-- strict thread matches above, loose matches on Subject: below --
2015-05-21 19:29 sl
2015-05-21 19:38 ` cinap_lenrek
2015-05-21 18:01 sl
2015-05-21 18:06 ` Kurt H Maier
2015-05-21 16:27 sl
2015-05-21 18:08 ` Devon H. O'Dell
2015-05-21 19:24 ` cinap_lenrek
2015-05-21 16:15 sl
2015-05-20 22:51 sl
2015-05-21 9:20 ` cinap_lenrek
2015-05-20 18:46 sl
2015-05-21 9:18 ` cinap_lenrek
2015-05-20 17:07 sl
2015-05-20 17:01 sl
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=2c054e0c3296713f66537c623a082f73@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).