[issue29385] Sockets Crashes or Memory Corruption

[INADA Naoki]

INADA Naoki added the comment:

I can't reproduce it because of some reason.

1. While you report it affects Python 3.3~3.7, the script doesn't work on 
Python 3.7
2. I've fixed webserver.py to work on Python 3, but it uses very old (draft) 
websocket protocol.  Current browser doesn't send headers like 
"Sec-WebSocket-Key1".
3. Even if handshake succeed, you can't send `\xff`*10 directly.  You should 
wrap it with "frame", specified in RFC.

I can't understand what "Close/Crash" means.
But I propose you to use websocket libraries, or read protocol specification 
carefully.
WebSocket is not "raw TCP socket after handshake", it's framed protocol on top 
of TCP (or other stream protocol).

--
nosy: +inada.naoki
resolution:  -> not a bug
status: open -> closed

___
Python tracker 

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

[issue29385] Sockets Crashes or Memory Corruption

[Dhiraj]

New submission from Dhiraj:

When Python Server receives a string of '/xff' (5 or more) from a page  after 
completing a handshake, the tab immediately crashes.  There are variations of 
this string with other characters mixed in that also cause an immediate close 
of python server.

To reproduce:

1. Run the websockets.py server 
2. Then open websockets.html in browser 

The PY server gets Close/Crash

--
components: Windows
files: REPRO.ZIP
messages: 286429
nosy: Dhiraj_Mishra, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Sockets Crashes or Memory Corruption
versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7
Added file: http://bugs.python.org/file46448/REPRO.ZIP

___
Python tracker 

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