Re: Fix displaying attachments with spaces etc.

[Toby Speight <streapadair@gmx.net>]

Please don't send me separate copies of list articles (did my
"Mail-Copies-To: never" get dropped somewhere?)


0> In article <vafofc03qy5.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>,
0> Kai Großjohann <URL:mailto:Kai.Grossjohann@CS.Uni-Dortmund.DE> ("Kai") wrote:

Kai> I guess the filename is needed for some programs.  Maybe some
Kai> programs look at the filename to decide what to do with it?

Well, that's broken on their part, but if we are to support filename-based
processing, shouldn't we be using the established local filename convention
(as described in /etc/mime.types or equivalent) rather than the *sender's*
local filename convention?

I see too many exploit attempts from the Windows world using MIME
parts with a declared type that's different to the receiver's implied
(from the filename) type.  I don't want to open up GNU systems to that
sort of abuse.


Kai> But Gnus could mangle the filename to be somewhat harmless.  For
Kai> example, it could replace spaces with underscores and ticks of
Kai> all kinds and sizes, too.  That would keep the extension intact
Kai> which is probably what those programs are looking at...

Possibly all non-alphamerics (except '.') could safely be stripped or
replaced?