Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: ramen worm
- To: tlug@example.com
- Subject: Re: ramen worm
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Date: Sat, 20 Jan 2001 18:10:17 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <XFMail.20010119084504.s-luppescu@example.com>
- References: <200101190204.f0J24ZT12545@example.com><XFMail.20010119084504.s-luppescu@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <cxA3pB.A.ruB.NbVa6@example.com>
- Resent-Sender: tlug-request@example.com
>>>>> "Stuart" == Stuart Luppescu <s-luppescu@example.com> writes: Stuart> Well, ftp is very useful in some cases, especially for Stuart> anonymous access to files. HTTP is generally faster, more robust (to stupid clients that wake up in ASCII mode for example), and doesn't require special treatment for firewalls. Stuart> The vulnerability in ftp was fixed a long time ago, You're missing Joerg's point. The vulnerability in FTP will _never_ be fixed, because FTP is a complex server application. HTTP has exactly the same vulnerability, of course---so why run two such servers? And neither should be enabled by default. Not even if you install the package. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."
- Follow-Ups:
- Re: ramen worm
- From: s-luppescu@example.com
- References:
- Re: ramen worm
- From: Joerg Winkelmann <jwinkel@example.com>
- Re: ramen worm
- From: s-luppescu@example.com
Home | Main Index | Thread Index
- Prev by Date: Re: Network problem: hard or soft?
- Next by Date: Re: DSL in Tokyo (again)
- Prev by thread: Re: ramen worm
- Next by thread: Re: ramen worm
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links