control: tags 853915 + patch
> > Somehow, when the code is run on the BTS server, the MIME::Parser seems
> > to fail and the `parse` function code is falling back to the legacy
> > pre-MIME code. Why?
>
> The reason is that the perl code on the BTS server is executed in taint
> mode, and
> Somehow, when the code is run on the BTS server, the MIME::Parser seems
> to fail and the `parse` function code is falling back to the legacy
> pre-MIME code. Why?
The reason is that the perl code on the BTS server is executed in taint
mode, and MIME::Parser fails on multipart messages when run
control: reassign 853915 bugs.debian.org
control: affects 853915 reportbug
Bug summary:
- Browsing bug logs in reportbug is broken for some messages
- Bug log messages retrieved from the BTS via the SOAP interface
are supposed to be decoded, but in these cases aren't.
- All MIME multipart
> So either something does not work as expected there, or I'm simply
> looking at the wrong code and should be looking somewhere else.
If this is the correct code, then why is it behaving differently when
its is run to serve a soap request, as compared to running it directly,
for the same email
When running e.g. `reportbug -N 853037`, a bunch of base64 is
displayed instead of the actual content of the messages.
> Could the BTS SOAP interface be changed to return the decoded message
> body of signed messages? Being able to deal with all other kinds of
> complex MIME messages
control: reassign 853915 debbugs
> >> When running e.g. `reportbug -N 853037`, a bunch of base64 is
> >> displayed instead of the actual content of the messages.
> > I'm not sure if this problem comes from the BTS which sends wrong
> > SOAP or on my side for parsing it wrong.
> My suspicion is
> It seems like the core of the problem is that parts of the header -- i.e.:
>
> Content-Type: text/plain; charset="UTF-8"
>
> Content-Transfer-Encoding: base64
>
> are assigned as part of the email body instead of the -header.
The message is a multipart message, where
>> When running e.g. `reportbug -N 853037`, a bunch of base64 is
>> displayed instead of the actual content of the messages.
> I'm not sure if this problem comes from the BTS which sends wrong
> SOAP or on my side for parsing it wrong.
My suspicion is that the BTS SOAP interface has trouble
It seems like the core of the problem is that parts of the header -- i.e.:
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
are assigned as part of the email body instead of the -header. I'm not
sure if this problem comes from the BTS which sends wrong
Can you please provide a case to reproduce this issue? I'm not sure if
this is a problem with python-reportbug.
Cheers,
Bastian
--
Dr. Bastian Venthur http://venthur.de
Debian Developer venthur at debian org
Package: reportbug
Version: 7.1.2
Followup-For: Bug #853915
Dear Maintainer,
The same thing occurs when saving a bug report to disk if the bug report
contains a non-ascii character - it is saved as base64 and then is
rejected by the bug tracking system if you try to send it later because
the
Package: reportbug
Version: 7.1.4
Severity: important
Dear Maintainer,
When running e.g. `reportbug -N 853037`, a bunch of base64 is displayed
instead of the actual content of the messages.
-Ben
-- System Information:
Debian Release: 9.0
APT prefers unstable-debug
APT policy: (500,
12 matches
Mail list logo
