public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Cam <camilo@mesias.co.uk>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: JFFS3 document / wiki [OT]
Date: Thu, 27 Jan 2005 16:10:38 +0000	[thread overview]
Message-ID: <41F9127E.6030508@mesias.co.uk> (raw)
In-Reply-To: <20050127131702.GA22121@wohnheim.fh-wedel.de>

Jörn

> Plus, Wikis tend to be instant security problems.  The situation
> appears to be so bad that anyone with average exploit knowledge can
> read the sources and control some new machines within a rainy
> afternoon. 

Can you back that statement up with an example please? I wasn't aware 
that wikis were so dangerous! :)

I run a wiki which had some problems with spam but it didn't go beyond 
that, and I've never heard of a wiki that caused security problems. IMHO 
they provide a reasonable compromise between high security and good 
features.

-Cam


-- 
camilo@mesias.co.uk                                                 <--

  reply	other threads:[~2005-01-27 16:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-25 10:11 JFFS3 document Artem B. Bityuckiy
2005-01-26 20:51 ` Michael
2005-01-26 21:30   ` Josh Boyer
2005-01-27  9:47     ` David Woodhouse
2005-01-27 13:17       ` Jörn Engel
2005-01-27 16:10         ` Cam [this message]
2005-01-27 16:38           ` JFFS3 document / wiki [OT] Jörn Engel
2005-01-27 16:37             ` jasmine
2005-01-27 16:51               ` Jörn Engel
2005-01-27 17:35             ` Jörn Engel
2005-01-27 18:27             ` Cam
2005-01-27 19:01               ` Jörn Engel

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=41F9127E.6030508@mesias.co.uk \
    --to=camilo@mesias.co.uk \
    --cc=dwmw2@infradead.org \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-mtd@lists.infradead.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