[issue35084] binascii.Error: Incorrect padding

2018-10-27 Thread TestUser


New submission from TestUser :

The below "test.code1" is not base64 encoded. Though, it is a good file.

t:~$ python3 -m base64 -d test.code1
Traceback (most recent call last):
  File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File "/usr/lib/python3.6/base64.py", line 602, in 
main()
  File "/usr/lib/python3.6/base64.py", line 586, in main
func(f, sys.stdout.buffer)
  File "/usr/lib/python3.6/base64.py", line 512, in decode
s = binascii.a2b_base64(line)
binascii.Error: Incorrect padding

--
components: Library (Lib)
messages: 328664
nosy: Tester
priority: normal
severity: normal
status: open
title: binascii.Error: Incorrect padding
type: crash
versions: Python 3.6

___
Python tracker 
<https://bugs.python.org/issue35084>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue35085] FileNotFoundError: [Errno 2] No such file or directory:

2018-10-27 Thread TestUser


New submission from TestUser :

Seems the base64 module has issues with bad file(s). This does not seems to 
generate a Crash Report.

t:~$ python3 -m base64 -d "12s345a2"
Traceback (most recent call last):
  File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File "/usr/lib/python3.6/base64.py", line 602, in 
main()
  File "/usr/lib/python3.6/base64.py", line 585, in main
with open(args[0], 'rb') as f:
FileNotFoundError: [Errno 2] No such file or directory: '12s345a2'

test@TestNut:~$ python3 -m base64 -d /test.txt
Traceback (most recent call last):
  File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File "/usr/lib/python3.6/base64.py", line 602, in 
main()
  File "/usr/lib/python3.6/base64.py", line 585, in main
with open(args[0], 'rb') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/test.txt'

--
components: Library (Lib)
messages: 328666
nosy: Tester
priority: normal
severity: normal
status: open
title: FileNotFoundError: [Errno 2] No such file or directory:
versions: Python 3.6

___
Python tracker 
<https://bugs.python.org/issue35085>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue35084] binascii.Error: Incorrect padding

2018-10-28 Thread TestUser


TestUser  added the comment:

The file contained the following code:
0x11a3ff119c\xe3\x50\x89\xe2\x53\x89\xe1\xb0\x0b\xcd\x80#%^ciuqrfiqrYWJjMTIzIT8kKiYoKSctPUB-
abc123!

On Sun, Oct 28, 2018 at 1:35 AM Karthikeyan Singaravelan <
rep...@bugs.python.org> wrote:

>
> Karthikeyan Singaravelan  added the comment:
>
> Thanks for the report. Can you please attach the file test.code1? Your
> original report says "test.code1" is not base64 encoded and -d takes a file
> that is base64 encoded and decodes it. Can you please be more descriptive
> about what you are expecting?
>
> --
> nosy: +xtreak
>
> ___
> Python tracker 
> <https://bugs.python.org/issue35084>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue35084>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue35085] FileNotFoundError: [Errno 2] No such file or directory:

2018-10-28 Thread TestUser


TestUser  added the comment:

How can that be CLI useful. Lucky I guess as this does not generate a Crash
Report. OK.

Bad/Missing File would have been my preferred. Then again?

Thanks

On Sun, Oct 28, 2018 at 1:48 AM Karthikeyan Singaravelan <
rep...@bugs.python.org> wrote:

>
> Karthikeyan Singaravelan  added the comment:
>
> I can see one another related report issue35084. As @steven.daprano said
> this is an expected traceback and it's working correctly. -d expects a
> valid base64 encoded file and supplying a non-existent file or file with
> invalid encoding is supposed to throw a traceback.
>
> --
> nosy: +xtreak
>
> ___
> Python tracker 
> <https://bugs.python.org/issue35085>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue35085>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue35084] binascii.Error: Incorrect padding

2018-10-28 Thread TestUser


TestUser  added the comment:

FYI: This error generates an Ubuntu Crash Report. Every time I use it on
the CLI. I wonder how many of these are generated?

On Sun, Oct 28, 2018 at 3:49 PM TestUser  wrote:

>
> TestUser  added the comment:
>
> The file contained the following code:
>
> 0x11a3ff119c\xe3\x50\x89\xe2\x53\x89\xe1\xb0\x0b\xcd\x80#%^ciuqrfiqrYWJjMTIzIT8kKiYoKSctPUB-
> abc123!
>
> On Sun, Oct 28, 2018 at 1:35 AM Karthikeyan Singaravelan <
> rep...@bugs.python.org> wrote:
>
> >
> > Karthikeyan Singaravelan  added the comment:
> >
> > Thanks for the report. Can you please attach the file test.code1? Your
> > original report says "test.code1" is not base64 encoded and -d takes a
> file
> > that is base64 encoded and decodes it. Can you please be more descriptive
> > about what you are expecting?
> >
> > --
> > nosy: +xtreak
> >
> > ___
> > Python tracker 
> > <https://bugs.python.org/issue35084>
> > ___
> >
>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue35084>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue35084>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue35084] binascii.Error: Incorrect padding

2018-10-28 Thread TestUser


TestUser  added the comment:

Thanks. The Python Foundation asked for users to report bugs. I've done so.

I'm looking at putting this in an article and Tweets on the bug process:
generating bugs, reporting, and resolution.

If I go forward I would like a thought or two from you on this bug process.

Thanks

On Sun, Oct 28, 2018, 5:41 PM Braden Groom  wrote:

>
> Braden Groom  added the comment:
>
> The file contents that you've provided aren't valid base64. I think the
> traceback that you've received is a reasonable one.
>
> --
> nosy: +bradengroom
>
> ___
> Python tracker 
> <https://bugs.python.org/issue35084>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue35084>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue35084] binascii.Error: Incorrect padding

2018-10-29 Thread TestUser


TestUser  added the comment:

In the new version of Ubuntu this generates a system crash report. Normally
I delete them.

Give me a day or to to get you one.

Funny, since it is the crash reports use of base64 encoding that led me to
the Python base64 module.

On Sun, Oct 28, 2018 at 8:42 PM Karthikeyan Singaravelan <
rep...@bugs.python.org> wrote:

>
> Karthikeyan Singaravelan  added the comment:
>
> Can you please add your definition of a crash? Crash in bug report context
> is used in C language context like causing a segfault, buffer overflow etc.
> Proper Exceptions are not considered as a crash and this is an exception
> raised since the contents are invalid. If it crashes as I mentioned above
> can you please add the crash log?
>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue35084>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue35084>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue35084] binascii.Error: Incorrect padding

2018-11-01 Thread TestUser

TestUser  added the comment:

On Mon, Oct 29, 2018 at 4:03 PM TestUser  wrote:

>
> TestUser  added the comment:
>
> In the new version of Ubuntu this generates a system crash report. Normally
> I delete them.
>
> Give me a day or to to get you one.
>
> Funny, since it is the crash reports use of base64 encoding that led me to
> the Python base64 module.
>
> On Sun, Oct 28, 2018 at 8:42 PM Karthikeyan Singaravelan <
> rep...@bugs.python.org> wrote:
>
> >
> > Karthikeyan Singaravelan  added the comment:
> >
> > Can you please add your definition of a crash? Crash in bug report
> context
> > is used in C language context like causing a segfault, buffer overflow
> etc.
> > Proper Exceptions are not considered as a crash and this is an exception
> > raised since the contents are invalid. If it crashes as I mentioned above
> > can you please add the crash log?
> >
> > --
> >
> > ___
> > Python tracker 
> > <https://bugs.python.org/issue35084>
> > ___
> >
>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue35084>
> ___
>

--
Added file: 
https://bugs.python.org/file47900/_usr_lib_python3.6_base64.py.1000.zip

___
Python tracker 
<https://bugs.python.org/issue35084>
___<>
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue35084] binascii.Error: Incorrect padding

2018-11-01 Thread TestUser


TestUser  added the comment:

That is all the crash automator provides.

On Thu, Nov 1, 2018 at 9:13 AM Serhiy Storchaka 
wrote:

>
> Change by Serhiy Storchaka :
>
>
> --
> Removed message: https://bugs.python.org/msg329061
>
> ___
> Python tracker 
> <https://bugs.python.org/issue35084>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue35084>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue35084] binascii.Error: Incorrect padding

2018-11-01 Thread TestUser


TestUser  added the comment:

My guess is the Gnome terminal. It does not like non ASCI data. There are
other programs that generate segfaults in the terminal when piped random
binary data.

Maybe, Python could get a -Q quit setting to turn of the trace back?

Thanks

On Thu, Nov 1, 2018 at 9:18 AM TestUser  wrote:

>
> TestUser  added the comment:
>
> That is all the crash automator provides.
>
> On Thu, Nov 1, 2018 at 9:13 AM Serhiy Storchaka 
> wrote:
>
> >
> > Change by Serhiy Storchaka :
> >
> >
> > --
> > Removed message: https://bugs.python.org/msg329061
> >
> > ___
> > Python tracker 
> > <https://bugs.python.org/issue35084>
> > ___
> >
>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue35084>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue35084>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue35084] binascii.Error: Incorrect padding

2018-11-01 Thread TestUser


TestUser  added the comment:

Last thought ...

man base64 has different options than the program:

python3 -m base64 -d -i test.code2
option -i not recognized
usage: /usr/lib/python3.6/base64.py [-d|-e|-u|-t] [file|-]
-d, -u: decode
-e: encode (default)
-t: encode and decode string 'Aladdin:open sesame'

On Thu, Nov 1, 2018 at 9:31 AM Fred Unll 
wrote:

> My guess is the Gnome terminal. It does not like non ASCI data. There are
> other programs that generate segfaults in the terminal when piped random
> binary data.
>
> Maybe, Python could get a -Q quit setting to turn of the trace back?
>
> Thanks
>
>
> On Thu, Nov 1, 2018 at 9:18 AM TestUser  wrote:
>
>>
>> TestUser  added the comment:
>>
>> That is all the crash automator provides.
>>
>> On Thu, Nov 1, 2018 at 9:13 AM Serhiy Storchaka 
>> wrote:
>>
>> >
>> > Change by Serhiy Storchaka :
>> >
>> >
>> > --
>> > Removed message: https://bugs.python.org/msg329061
>> >
>> > ___
>> > Python tracker 
>> > <https://bugs.python.org/issue35084>
>> > ___
>> >
>>
>> --
>>
>> ___
>> Python tracker 
>> <https://bugs.python.org/issue35084>
>> ___
>>
>

--

___
Python tracker 
<https://bugs.python.org/issue35084>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue35084] binascii.Error: Incorrect padding

2018-11-02 Thread TestUser


TestUser  added the comment:

One of the problems reporting is the archaic way the bug trackers work.
Sorry fo the confusion except I am not sure of the exact request.

On my end I have provided what I can. You are welcome to fire up a VM and
run the sample submitted.

All the best.

On Fri, Nov 2, 2018, 4:09 PM Terry J. Reedy 
> Terry J. Reedy  added the comment:
>
> TestUser, please re-read and follow Serhiy's request.
>
> --
> nosy: +terry.reedy
>
> ___
> Python tracker 
> <https://bugs.python.org/issue35084>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue35084>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com