From: Jonas de Buhr <jonas.de.buhr@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} Development framework with access restriction?
Date: Thu, 29 Sep 2011 08:57:49 +0200 [thread overview]
Message-ID: <20110929085749.7a8c8f46@toxic.dbnet> (raw)
In-Reply-To: <CAN0CFw2NEwDkC8OkDQs74e6aGR2Nz=GLpJ3ahYm-C1-s0s5NQw@mail.gmail.com>
>> The problem with that is he will need to test his code in the working
>> system.
why in the production system?
>>I need a way for him to be able to read/write to a certain
>> file or files within the working system, but have no read/write
>> access to any other files in the system.
>>
>> Is SFTP perhaps the way to go for this?
>>
>> - Grant
>
>For some reason I thought SFTP would provide access control but now
>I'm thinking it's just like SSH in that access control is based on
>file ownership and permissions?
yes.
> If that's the case, can anyone think
>of a better way to control remote access to my files than chmod/chown?
someone already did ;)
http://www.gentoo-wiki.info/HOWTO_Use_filesystem_ACLs
> I think it would be nice if the access control were built into the
>transport mechanism, version control system, or something else already
>in use, but it doesn't sound like that's going to happen.
its certainly possible to control the write access with ACLs. read
access however is a different story because as soon as his code runs in
the context of the webrowser he will likely be able to read the rest of
the code.
next prev parent reply other threads:[~2011-09-29 6:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 20:01 [gentoo-user] {OT} Development framework with access restriction? Grant
2011-09-26 21:37 ` Michael Orlitzky
2011-09-27 11:27 ` Mick
2011-09-29 1:18 ` Grant
2011-09-29 2:23 ` Grant
2011-09-29 6:57 ` Jonas de Buhr [this message]
2011-09-29 7:32 ` Mick
2011-09-30 23:53 ` Grant
2011-10-01 11:07 ` Florian Philipp
2011-10-01 23:27 ` Grant
2011-10-02 22:41 ` Mick
2011-10-03 22:01 ` Grant
2011-10-03 22:12 ` Michael Mol
2011-09-29 8:13 ` Neil Bothwick
2011-09-29 17:23 ` Michael Orlitzky
2011-09-30 23:59 ` Grant
2011-10-01 0:23 ` Michael Orlitzky
2011-10-01 23:46 ` Grant
2011-10-02 19:04 ` Michael Orlitzky
2011-10-03 21:54 ` Grant
2011-10-03 22:00 ` Michael Mol
2011-10-04 4:25 ` Michael Orlitzky
2011-09-27 12:19 ` Jonas de Buhr
2011-09-29 1:23 ` Grant
2011-09-29 6:43 ` Jonas de Buhr
2011-09-30 23:50 ` Grant
-- strict thread matches above, loose matches on Subject: below --
2011-10-01 5:58 Pandu Poluan
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=20110929085749.7a8c8f46@toxic.dbnet \
--to=jonas.de.buhr@gmx.net \
--cc=gentoo-user@lists.gentoo.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