NNSquad - Network Neutrality Squad

NNSquad Home Page

NNSquad Mailing List Information

 


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ NNSquad ] Re: HTTP must die!


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

the last article on Lauren's blog surely makes a good point.

However this leaves us with the issue of how to provide
certificates for all those "do-it-at-some-free-time" content
providers. Surely it would not be of much use, if their ISPs
would sell them the certificates, because then they still had
the power to change the content as they wished.

However external entities currently charge really high
amounts for simple certificates, which currently limits the use
of https. A good solution could be those trust-web authorities
like CA-Cert.

    Jens-W. Schicke

On a related side-note: Why does https://lauren.vortex.com/
return a 403 Forbidden?

      [ I'll be addressing the certificate issue in a new blog posting
	hopefully later today, though the topic is starting to stray out of
	scope for this list.  As for the 403 -- I actually have supported
	https: on the blog over various periods.  Currently it's disabled
	since the underlying hardware (a number of infrastructure items are
	involved) is underpowered to deal with the increasing load at a
	performance level I'd like to see, even with http: (especially when
	I'm being slashdotted, like, uh, right now).  Some sites choose to
	redirect https: to http: in such situations.  I don't disapprove of
	that practice in a general sense, but I've personally chosen to 403 in
	that situation.

        A number of infrastructure upgrades are needed as resources permit.

                    -- Lauren Weinstein
                       NNSquad Moderator ]

 			

        

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHXmlrzhchXT4RR5ARAgDxAJ4/Xcg9Vwmmx1edSVJFsIlkyKYJUgCeMfy+
EeYJRRt5d8DNEER0ZP3LZp8=
=Msxt
-----END PGP SIGNATURE-----