Package: fnord
Version: 1.10-2
Severity: normal

*** Please type your report below this line ***

Several httpds, thttpd, fnord, and others default to type text/plain if
the file extension is not in a short compiled-in fixed list.  The use of
a compiled in list is a good idea for purposes of chroot, security, etc.

However, the use of a short fixed list means that many common file types
will not be on the list. Your addition of 'deb' and others to this list
testafies to this.  

When the default is text/plain, this causes unix configfiles and the
like to display nicely in browsers.  However, it causes binary files
downloaded by windows clients to become corrupted via the LF -> CR/LF
translation implemented in their (foolish?) operating system.

Since I do not like my datafiles to be corrupted on download, I have to
manually patch my httpd for every revision that comes out to default the
mime type to application/octet-stream, which is safe for all uses.
Another approach would be to add 30 or so (and growing over time) other
extensions to the fixed list.

I often get behind in this because it is not really a job or anything,
which means i am often open to compromise or my users are often getting
corrupt downloads.

I think correct is better than convient, and thus I consider this a bug.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-jsr
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to 
en_US.iso88591)

fnord depends on no packages.

Versions of packages fnord recommends:
ii  ipsvd                         0.11.1-1   Internet protocol service daemons
ii  runit                         1.3.2-1    a UNIX init scheme with service su

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to