From: Pierre Ossman <drzeus@drzeus.cx>
To: Dave Airlie <airlied@csn.ul.ie>
Cc: "J.H." <warthog19@eaglescrag.net>,
Jon Tollefson <kniht@linux.vnet.ibm.com>,
Jim Zemlin <jzemlin@linux-foundation.org>,
bugme-admin@linux-foundation.org,
linux-kernel <linux-kernel@vger.kernel.org>,
"FTPAdmin Kernel.org" <ftpadmin@kernel.org>,
"Jorge O. Castro" <jorge@ubuntu.com>,
users@kernel.org, support@osuosl.org
Subject: Re: [kernel.org users] [KORG] Bugzilla Upgrade / Server move
Date: Thu, 26 Mar 2009 08:11:37 +0100 [thread overview]
Message-ID: <20090326081137.09e8dc0d@mjolnir.ossman.eu> (raw)
In-Reply-To: <alpine.DEB.2.00.0903260111370.27027@skynet.skynet.ie>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
On Thu, 26 Mar 2009 01:12:33 +0000 (GMT)
Dave Airlie <airlied@csn.ul.ie> wrote:
> >
> > One small misfeature in the new bugzilla is that you can no longer view
> > attachments directly in the browser. For text/plain stuff this is
> > particularly annoying. If it could be fixed I'd be a much happier
> > camper. :)
>
> I think upstream bugzilla stopped this due to a potential security problem
> with feeding things to the browser.
>
If we cannot trust the browser to safely handle most data, then I
suppose we'll all have to start using wget and browsing our pages via
less.
I hope this feature can be reconfigured, even if upstream happens to
think out browsers are too insecure to be on the net.
Rgds
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-03-26 7:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 7:13 J.H.
2009-03-25 11:57 ` Alan Cox
2009-03-25 14:38 ` Martin Bligh
2009-03-25 20:21 ` [kernel.org users] " Pierre Ossman
2009-03-26 1:12 ` Dave Airlie
2009-03-26 7:11 ` Pierre Ossman [this message]
2009-03-26 7:23 ` Tejun Heo
2009-03-26 7:48 ` Stefan Richter
2009-03-26 8:04 ` Stefan Richter
2009-03-26 19:21 ` J.H.
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=20090326081137.09e8dc0d@mjolnir.ossman.eu \
--to=drzeus@drzeus.cx \
--cc=airlied@csn.ul.ie \
--cc=bugme-admin@linux-foundation.org \
--cc=ftpadmin@kernel.org \
--cc=jorge@ubuntu.com \
--cc=jzemlin@linux-foundation.org \
--cc=kniht@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=support@osuosl.org \
--cc=users@kernel.org \
--cc=warthog19@eaglescrag.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
Powered by JetHome