Re: Couple of questions re: attributes

Peter Gutmann wrote:

> At the native API level it should be binary data, however I'm not sure whatz
> Python's marshalling does when it passes the data to the native API, perhaps
> someone else can answer this.

As near as I can tell it's using the old C embedding/extension 
protocols.  It's a direct conversion of a Python str into a C char* 
using the PyObject_AsCharBuffer() call.

http://docs.python.org/c-api/objbuffer.html

Who's the maintainer of this binding?  Is there one?  It could use 
updating, even for 2.6, and I doubt it will work under 3.0.

>>>> cryptSetAttributeString(ctx, CRYPT_CTXINFO_KEYING_VALUE, 'password')
>> Traceback (most recent call last):
>>   File "<stdin>", line 1, in <module>
>> cryptlib_py.CryptException: (-16, 'Internal consistency check failed')

> Hmm, can you provide details of what gets passed to the native API to trigger
> this?  Or can you build the debug version of the code, which will throw an
> exception for the check indicating where it's being done?

When I retry with a debug build I get (-3, 'Bad argument, parameter 3') 
instead.  As near as I can tell the Python binding doesn't pass on 
anything else.  I can try to skip the binding and call to cryptlib 
directly using ctypes.

-- Tim

_______________________________________________
Cryptlib mailing list
[email protected] via Mail: [email protected]
Archive: ftp://ftp.franken.de/pub/crypt/cryptlib/archives/
http://news.gmane.org/gmane.comp.encryption.cryptlib
Posts from non-subscribed addresses are blocked to prevent spam, please
subscribe in order to post messages.