From: "Bryan Østergaard" <kloeri@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] enable UTF8 per default?
Date: Tue, 28 Feb 2006 19:25:55 +0100 [thread overview]
Message-ID: <20060228182555.GA14125@mail.fl.dk> (raw)
In-Reply-To: <1141148853.4294.17.camel@onyx>
On Tue, Feb 28, 2006 at 12:47:33PM -0500, solar wrote:
> I forget where I read it but I thought that unicode lead to overflows
> and was considered a general security risk. I wish I knew where I read
> that but I'm unable to find it.
>
> Any list readers know anything relating to that?
>
It's true that many overflows have been found in unicode aware
applications, like the zillion unicode overflows in Internet Explorer
for example. But that shouldn't lead to considering unicode a general
security risk in my mind even though the apache team uses ascii in the
default configuration to protect against bugs in poorly written
applications.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-28 18:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 10:58 [gentoo-dev] enable UTF8 per default? Patrick Lauer
2006-02-28 11:32 ` Diego 'Flameeyes' Pettenò
2006-02-28 11:47 ` Patrick Lauer
2006-02-28 12:11 ` Diego 'Flameeyes' Pettenò
2006-02-28 14:27 ` Mike Frysinger
2006-02-28 12:50 ` Lars Weiler
2006-02-28 13:50 ` Patrick Lauer
2006-02-28 14:46 ` Joseph Jezak
2006-02-28 16:24 ` Kalin KOZHUHAROV
2006-03-04 12:46 ` Alexander Simonov
2006-03-04 20:13 ` Kalin KOZHUHAROV
2006-02-28 16:51 ` Josh
2006-02-28 17:47 ` solar
2006-02-28 17:53 ` Ciaran McCreesh
2006-02-28 18:25 ` Bryan Østergaard [this message]
2006-02-28 19:18 ` Kevin F. Quinn (Gentoo)
2006-02-28 20:23 ` solar
2006-02-28 23:51 ` Bjarke Istrup Pedersen
2006-03-08 7:43 ` [gentoo-dev] " Mathieu Bonnet
2006-03-09 20:25 ` [gentoo-dev] " Kevin F. Quinn (Gentoo)
2006-03-11 20:29 ` Eldad Zack
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=20060228182555.GA14125@mail.fl.dk \
--to=kloeri@gentoo.org \
--cc=gentoo-dev@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