Bug#950319: libreoffice: filename replacements in mime entries for mailcap must not be quoted within the given command

2020-12-26 Thread Marriott NZ
Hi, thanks for such a quick reply. On Thu, 17 Dec 2020 08:34:44 +0100, Rene Engelhard wrote: > > 1) There is a Lintian test for this specific problem: > > I know and saw that one, and as long as there isn't a *definitive* > answer am continuing what I am doing already: ignoring it. > > Or is

Bug#950319: libreoffice: filename replacements in mime entries for mailcap must not be quoted within the given command

2020-12-16 Thread Rene Engelhard
Hi, Am 17.12.20 um 00:48 schrieb Marriott NZ: > Unfortunately no progress yet on #928037, but I wanted to add here some info > from related bug reports. > > 1) There is a Lintian test for this specific problem: > https://lintian.debian.org/tags/quoted-placeholder-in-mailcap-entry.html > Package

Bug#950319: libreoffice: filename replacements in mime entries for mailcap must not be quoted within the given command

2020-12-16 Thread Marriott NZ
Hello, Unfortunately no progress yet on #928037, but I wanted to add here some info from related bug reports. 1) There is a Lintian test for this specific problem: https://lintian.debian.org/tags/quoted-placeholder-in-mailcap-entry.html Package libreoffice and 40 more, currently trigger the

Bug#950319: libreoffice: filename replacements in mime entries for mailcap must not be quoted within the given command

2020-02-01 Thread Rene Engelhard
block 950319 by 928037 thanks On Sat, Feb 01, 2020 at 08:21:20AM +0100, Frank Loeffler wrote: > in the mailcap is able to prevent shell escapes. This is why the replacing > program must be the one doing this. Thus, if any tool using mailcap does not > quote filenames properly and only relies on

Bug#950319: libreoffice: filename replacements in mime entries for mailcap must not be quoted within the given command

2020-02-01 Thread Rene Engelhard
Hi, On Sat, Feb 01, 2020 at 08:21:20AM +0100, Frank Loeffler wrote: > For thunderbird I find, e.g.: > > message/rfc822; /usr/bin/thunderbird %s; test=test -n "$DISPLAY" > text/calendar; /usr/bin/thunderbird %s; test=test -n "$DISPLAY" > text/x-vcard; /usr/bin/thunderbird %s; test=test -n

Bug#950319: libreoffice: filename replacements in mime entries for mailcap must not be quoted within the given command

2020-01-31 Thread Frank Loeffler
Hi Rene, On Fri, Jan 31, 2020 at 05:28:58PM +0100, Rene Engelhard wrote: Using mutt, I created a new email, added an attachment with a file name containing spaces (a pptx file, thus libreoffice), and without sending no, MS Office. Which LibreOffice happens to be registered for. I know.

Bug#950319: libreoffice: filename replacements in mime entries for mailcap must not be quoted within the given command

2020-01-31 Thread Rene Engelhard
found 950319 1:5.2.3~rc1-3 thanks Hi, On Fri, Jan 31, 2020 at 11:47:29AM +0100, Frank Loeffler wrote: > Using mutt, I created a new email, added an attachment with a file name > containing spaces (a pptx file, thus libreoffice), and without sending no, MS Office. Which LibreOffice happens to be

Bug#950319: libreoffice: filename replacements in mime entries for mailcap must not be quoted within the given command

2020-01-31 Thread Frank Loeffler
Package: libreoffice Version: 1:5.2.7-1+deb9u11 Severity: normal Dear Maintainer, * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? Using mutt, I created a new email, added an attachment with a file name containing spaces (a