[37874] in North American Network Operators' Group
Re: Stealth Blocking
daemon@ATHENA.MIT.EDU (Shawn McMahon)
Fri May 25 08:05:57 2001
Date: Fri, 25 May 2001 08:03:32 -0400
From: Shawn McMahon <smcmahon@eiv.com>
To: nanog@merit.edu
Message-ID: <20010525080332.E16908@eiv.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="hwvH6HDNit2nSK4j"
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.30.0105250042230.3328-100000@redhat1.mmaero.com>; from jlewis@lewis.org on Fri, May 25, 2001 at 12:44:28AM -0400
Errors-To: owner-nanog-outgoing@merit.edu
--hwvH6HDNit2nSK4j
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, May 25, 2001 at 12:44:28AM -0400, jlewis@lewis.org wrote:
>=20
> Email them a URL with a username and password.
This requires that you:
1) Have a web site with sufficient space to store the file.
2) Have it accessible, i.e. not firewalled on port 80.
3) Set up the accounts and passwords.
It also requires that they:
1) Run a web browser.
2) Have the username and password available when they attempt to get the
file.
Exactly how is that more efficient than just mailing them the file?
I'd completely agree with you for, say, a mailing list; but we're talking
about person A wants the file, person B has the file. Why should either
one of them jump through hoops? More importantly, why do you give a shit
how they choose to transfer files to each other?
--hwvH6HDNit2nSK4j
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjsOShQACgkQEcl9bQ0RMt09LQCaA9e79qYs1Ox5m8pY45DdQhqs
5UoAnjxqkCDHNLmtIZE02PIWRostCB77
=0MxN
-----END PGP SIGNATURE-----
--hwvH6HDNit2nSK4j--
