TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Content-Transfer-Encoding: 8BIT
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
From: Jacob Sparre Andersen <[log in to unmask]>
Date: Thu, 20 Jul 2000 15:05:46 +0200
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
MIME-Version: 1.0
Reply-To: Jacob Sparre Andersen <[log in to unmask]>
Parts/Attachments: TEXT/PLAIN (39 lines)
I don't know how many of you follow the security bulletins
in the Unix-world, but there has recently been a lot of
trouble with the more widely used FTP daemons (one of them
is WU-FTPD).

Seeing a FTP daemon in operation from the client-side, it
doesn't seem like a very complicated piece of software, and
my WU-FTPD binary takes up "only" 159 kb on the disk.

On the other hand have I seen "cascades" of reports of
security vulnerabilities for this program. Many more than I
would expect to be possible from my view of the simplicity
of a FTP daemon.

My point:

FTP daemons are high-visibility programs, which I imagine
shouldn't be that hard to implement.

[ assuming I am not mistaken about the level of difficulties
  implementing a FTP daemon: ]

So why don't we write a Team Ada FTP daemon, so we can show
that all our fine words about Ada's suitability for
high-reliability software are more than just words?

I must admit that I don't know much about network
programming, so I can't do much alone, but if somebody can
point me to some useful litterature and answer the questions
that pop up, then I am willing to start on the project.


"Then, after a second or so, nothing continued to happen."