[Python-bugs-list] [ python-Bugs-436948 ] cPickle.loads(): Insecure string pickle

[noreply@sourceforge.net]

Bugs item #436948, was opened at 2001-06-27 21:04
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=436948&group_id=5470

>Category: Extension Modules
>Group: Not a Bug
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: wah meng wong (r32813)
Assigned to: Nobody/Anonymous (nobody)
Summary: cPickle.loads(): Insecure string pickle

Initial Comment:
Python Version = python 1.5.2 on AIX 4.3.3.0
Module used = cPickle

I encountered the ValueError: Insecure string pickle problem when I wanted to unpickle a pickled 
data that I query from database. I guess there is a data corruption problem to the data string but I 
don't know what it is. Appreciate if someone can tell me what could cause this problem. I am not 
sure if this is related to the unicode new line character issue where it will break the loads() 
function as reported by someone else in the buglist. 

BTW, the data string that I tried to unpickle is 65535 bytes in size. Is that too big? I have attach 
the file containing the problematic data. With this data I will be able to reproduce the problem. 

Appreciate your helps!

Regards,
Wah Meng

----------------------------------------------------------------------

>Comment By: Tim Peters (tim_one)
Date: 2001-06-28 09:31

Message:
Logged In: YES 
user_id=31435

Thanks for the followup!  Closing as requested.  You would 
have gotten a reply "eventually", but looking into problems 
nobody has seen before is sometimes a low priority.  FYI, 
the "insecure" exception in cPickle is raised for things 
like strings with unbalanced quotes, implying that they 
could not possibly have been *created* by cPickle.  
Truncated data is a thoroughly believable cause for that.

----------------------------------------------------------------------

Comment By: wah meng wong (r32813)
Date: 2001-06-28 05:28

Message:
Logged In: YES 
user_id=216234

I would like to cancel this question as I found out that the data was really 'corrupted' because it wasn't the 
complete string that I inserted into the table. The problem was due to there was a limitation on the 
Oracle where only the first 64k bytes of data if returned if one queries a column with long as datatype. My 
data was exceeding 64k thus the returned value from such SQL wasn't the complete data that I inserted. 
Sorry for this silly mistake. There is no bug on the cPickle. :).

Thanks anyway to whom have at least read my question and intended to reply...

Regards,
Wah Meng

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=436948&group_id=5470