public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: awaria@chopin.edu.pl
Subject: Re: [gentoo-dev] Bugzilla 4 migration
Date: Tue, 8 Mar 2011 15:53:01 +0100	[thread overview]
Message-ID: <20110308155301.6af83f28@pomiocik.lan> (raw)
In-Reply-To: <c66b505c52b39cd9960f564b813d52ce@chopin.edu.pl>

[-- Attachment #1: Type: text/plain, Size: 1876 bytes --]

On Tue, 08 Mar 2011 16:41:08 +0200
Antoni Grzymała <awaria@chopin.edu.pl> wrote:

>  On Tue, 8 Mar 2011 15:26:34 +0100, Michał Górny wrote:
> > On Mon, 07 Mar 2011 15:06:25 -0500
> > Olivier Crête <tester@gentoo.org> wrote:
> >
> >> On Mon, 2011-03-07 at 20:47 +0100, Michał Górny wrote:
> >> > Why does everyone assume it needs to be enforced? If user is
> >> > interested in protecting his/her data, he/she can simply use
> >> > https://. If he/she is not, there is no real reason to enforce
> >> > slower (and not always supported) SSL.
> >>
> >> Maybe it's not to protect the user, but to protect the Gentoo
> >> infrastructure.. And really, SSL has been supported by every
> >> browser for the last 15 years. And it is not in any way slow or
> >> slower than non-SSL.
> >
> > If you really think you need to force all users to use SSL, thus
> > assuming they're unable to make their own decisions, why don't you
> > restrict bugzie access completely?
> 
>  You don't seem to (or pretend not to) understand that using SSL 
>  protects not *the user* (in which case, yes, a user is free to leave
> the door to *his own* house wide open), but the Gentoo infrastructure
> that is far from his own and that all of us are using.

Please explain to me how not using SSL for a particular bugzie user is
going to hurt Gentoo infra. Even if we're talking about a dev,
and we're really assuming a dev is completely unaware of security
issues he/she's dealing with, I'd say power outage could cause more
damage.

> Besides, complaining about SSL being slow is absurd considering how
> mildly interactive and how low-traffic a typical bugzilla session is.
> You could do just fine over a 9600 bps modem.

It is more absurd to waste 5 minutes trying to establish login session
due to packet loss.

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-03-08 14:55 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-06 22:55 [gentoo-dev] Bugzilla 4 migration Christian Ruppert
     [not found] ` <4D742033.5030609@gentoo.org>
2011-03-07  1:49   ` Christian Ruppert
2011-03-07  9:12 ` Michał Górny
2011-03-07  9:24   ` Dirkjan Ochtman
2011-03-07  9:30     ` Michał Górny
2011-03-07  9:25   ` Mike Frysinger
2011-03-07 14:48     ` Tobias Klausmann
2011-03-07 14:50       ` Dane Smith
2011-03-07 15:00       ` Mike Frysinger
2011-03-07 19:47       ` Michał Górny
2011-03-07 20:03         ` Christian Ruppert
2011-03-07 20:06         ` Olivier Crête
2011-03-07 21:32           ` Fabian Groffen
2011-03-07 21:52             ` Rich Freeman
2011-03-07 21:59               ` Fabian Groffen
2011-03-07 22:23                 ` Mike Frysinger
2011-03-07 22:25             ` Mike Frysinger
2011-03-08  8:08               ` Fabian Groffen
2011-03-08 14:26           ` Michał Górny
2011-03-08 14:41             ` Antoni Grzymała
2011-03-08 14:53               ` Michał Górny [this message]
2011-03-08 15:06                 ` Nathan Phillip Brink
2011-03-07  9:33   ` Robin H. Johnson
2011-03-07  9:51 ` Robin H. Johnson
2011-03-07 10:09   ` justin
2011-03-07 11:30   ` Jorge Manuel B. S. Vicetto
2011-03-07 14:13   ` Donnie Berkholz
2011-03-07 15:35     ` Dirkjan Ochtman
2011-03-07 15:47       ` Donnie Berkholz
2011-03-08  6:50     ` Hans de Graaff
2011-03-08 14:06       ` Donnie Berkholz
2011-03-07 12:20 ` Markos Chandras

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=20110308155301.6af83f28@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=awaria@chopin.edu.pl \
    --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