Am Tue, 19 Apr 2011 19:28:50 -0700 (PDT)
schrieb Jean-Paul Calderone calderone.jeanp...@gmail.com:
It is completely insecure. Do not use pickle and
sockets together.
Yes pickle is like eval, but that doesnt mean that one should never
ever use it over a socket connection.
What about ssl
On Wed, Apr 20, 2011 at 4:44 PM, Bastian Ballmann ba...@chaostal.de wrote:
Yes pickle is like eval, but that doesnt mean that one should never
ever use it over a socket connection.
What about ssl sockets where client and server authenticate each other?
Or you encrypt the pickle dump with
Am Wed, 20 Apr 2011 16:59:19 +1000
schrieb Chris Angelico ros...@gmail.com:
Even public/private key systems won't
work here; someone could get hold of your client and its private key,
and poof.
Oh yeah but than all kinds of trusted computing wont work. Sure
one can see it on the net these
Am 20.04.2011 09:34, schrieb Bastian Ballmann:
No system is totally secure. You can _always_ poke around if a program
uses user input.
It depends on what the program does with the input. If it treats it
appropriately, nothing can happen.
For example one can totally own a complete
Am Wed, 20 Apr 2011 10:25:14 +0200
schrieb Thomas Rachel
nutznetz-0c1b6768-bfa9-48d5-a470-7603bd3aa...@spamschutz.glglgl.de:
It depends on what the program does with the input. If it treats it
appropriately, nothing can happen.
Yes, but the question seems to be what is appropriately.
What
On Wed, Apr 20, 2011 at 7:17 PM, Bastian Ballmann ba...@chaostal.de wrote:
Well you forgot to escape ; and \ but this seems to slide into OT ;)
The semicolon doesn't need to be escaped in a quoted string, and the
backslash does only if it's the escape character. The
string-safetifier function
Am Wed, 20 Apr 2011 19:26:44 +1000
schrieb Chris Angelico ros...@gmail.com:
Yes, but the other half of the issue is that you have to treat
anything that comes over the network as user input, even if you
think it's from your own program that you control.
Sure.
Buffer overruns can happen in
On Tue, Apr 19, 2011 at 11:53 AM, Roger Alexander rtalexan...@mac.com wrote:
Hi,
I'm trying to understand how to pickle Python objects over a TCP
socket.
In the example below (based on code from Foundations of Python Network
Programming), a client creates a dictionary (lines 34-38) and uses
On Wed, Apr 20, 2011 at 4:53 AM, Roger Alexander rtalexan...@mac.com wrote:
Hi,
I'm trying to understand how to pickle Python objects over a TCP
socket.
In the example below (based on code from Foundations of Python Network
Programming), a client creates a dictionary (lines 34-38) and uses
On Tue, Apr 19, 2011 at 11:53 AM, Roger Alexander rtalexan...@mac.com wrote:
Hi,
I'm trying to understand how to pickle Python objects over a TCP
socket.
In the example below (based on code from Foundations of Python Network
Programming), a client creates a dictionary (lines 34-38) and uses
On Wed, Apr 20, 2011 at 5:30 AM, Dan Stromberg drsali...@gmail.com wrote:
I played around with it until something worked, and ended up with the
below. The most significant change was probably using sc.makefile
instead of s.makefile in the server...
Oh! I didn't notice that in the OP. Yep,
Thanks everybody, got it working.
I appreciate the help!
Roger.
--
http://mail.python.org/mailman/listinfo/python-list
On Apr 19, 6:27 pm, Roger Alexander rtalexan...@mac.com wrote:
Thanks everybody, got it working.
I appreciate the help!
Roger.
It's too bad none of the other respondents pointed out to you that you
_shouldn't do this_! Pickle is not suitable for use over the network
like this. Your server
13 matches
Mail list logo
