From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] A few questions about 9p
Date: Thu, 29 Jan 2015 06:52:19 -0800 [thread overview]
Message-ID: <a7e9b7053f5e266405f00f2d481b746b@lilly.quanstro.net> (raw)
In-Reply-To: <CAHL7psE+6gt35Ntt8MVfvRZR-zH7o_-8AL-B2ufdeRbjfC=bxQ@mail.gmail.com>
> >> I can't find details on the file execution permission: looks like a
> malicious client could just ignore it on files and execute anything that it
> can read (obviously I'm just talking about single files, not directory).
> >
> > It's not malicious, just incorrect. Obviously you can't execute a
> remote image or script unless you read it.
>
> By malicious I mean that the client could execute a script that it wasn't
> allowed to.
if you can read the executable you can already copy it somewhere, set the execute
bit, and away you go. the x bit is purely advisory. it is not a security mechanism.
- erik
next prev parent reply other threads:[~2015-01-29 14:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHL7psHNZrbQuFRz5grmXgR686o2e+-SX=tW6yxnfNaduec5NQ@mail.gmail.com>
[not found] ` <CAHL7psGPf3z56wjZGJsSVCeEzHBJgtbt17nL-UNA8kXKM-mkuw@mail.gmail.com>
[not found] ` <CAHL7psFTR7G1N069XoqYkuxJ_P0TYzmXAZ752wVa=9BAOX0CQg@mail.gmail.com>
[not found] ` <CAHL7psEUjdaV9LABzRrHn1TLftF+moxWV563-tvK+7VLviKhRg@mail.gmail.com>
2015-01-29 9:04 ` Giacomo Tesio
2015-01-29 10:07 ` Charles Forsyth
2015-01-29 14:36 ` erik quanstrom
2015-01-29 14:41 ` Giacomo Tesio
2015-01-29 14:52 ` erik quanstrom [this message]
2015-01-29 14:54 ` cinap_lenrek
2015-01-29 15:46 ` Giacomo Tesio
2022-10-31 23:14 ibrahim via 9fans
2022-11-04 23:41 ` ron minnich
2022-11-05 1:32 ` ibrahim via 9fans
2022-11-05 4:10 ` ibrahim via 9fans
2022-11-05 4:30 ` ori
2022-11-05 6:30 ` ibrahim via 9fans
2022-11-05 14:09 ` ori
2022-11-05 15:50 ` ibrahim via 9fans
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=a7e9b7053f5e266405f00f2d481b746b@lilly.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).