From: Cam <camilo@mesias.co.uk>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS3 document / wiki [OT]
Date: Thu, 27 Jan 2005 18:27:01 +0000 [thread overview]
Message-ID: <41F93275.3090705@mesias.co.uk> (raw)
In-Reply-To: <20050127163845.GA7755@wohnheim.fh-wedel.de>
Jörn
> Various bits of information on this were spread all over the place:
> o Code examples of mysql - tons of buffer overflows.
> o Code examples of php - same.
> o Various hacks of machines based on either php or mysql
> vulnerabilities.
> o Some specific problems with some wiki implementations.
>
> Considering that most wikis use php, mysql or both, you can pretty
> much get the idea. I cannot point to specific vulnerabilities or
> exploits, but the only thing stopping me from owning your wiki is my
> lack of interest.
Sorry but I'm not convinced. The link is interesting but there is no
mention of wikis. Also, php and mysql are used widely for other
purposes, if it was as bad as you say, we would be in some kind of web
apocalypse, which we're not. There are other wikis too (Java based or
Perl/CGI in my case).
Cheers,
-Cam
--
camilo@mesias.co.uk <--
next prev parent reply other threads:[~2005-01-27 18:27 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 ` JFFS3 document / wiki [OT] Cam
2005-01-27 16:38 ` 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 [this message]
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=41F93275.3090705@mesias.co.uk \
--to=camilo@mesias.co.uk \
--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