Malware
Help bugs
g
feport spam
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 MIME::P
when run in taint
mode. Adding the -T flag to the perl invocation in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853915#65
reproduces the problem: The message body is not properly decoded.
ldstable) and jessie (old-oldstable), but couldn't reproduce the
problem there either.
Thanks to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910360
it is now also clear that I've looked at the correct code, and the code
is actually working as intended in another debbugs installation.
> 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 m
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 is
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
Hello,
I'm often hit by this bug, as I have several Debian instances where no e-mail
conection is available. So I save the report of reportbug, transfer
the file to another machine and then I need to massage the e-mail to
get it accepted (currently removing all but the base64 part, running
"base64
> 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 Content-Typ
>> 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 with
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 SOA
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
control: clone 853915 -1
control: reassign 853915 python-debianbts
control: retitle -1 reportbug: base64 encoded reports rejected by bts
Reading and sending base64 message are two different bugs, so let's
split this report.
I believe that python-debianbts is supposed to decode a base64 message
bo
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, 'unstab
20 matches
Mail list logo
