Bcrypt Data in the trace instead of the hande/Pointer?

Questions about Wine on Linux
Locked
here
Level 2
Level 2
Posts: 29
Joined: Sun Jan 28, 2018 5:51 am

Bcrypt Data in the trace instead of the hande/Pointer?

Post by here »

I was looking for data in an application and read about tracing bcrypt in
https://source.winehq.org/git/wine.git/ ... ypt_main.c


bcrypt:BCryptCreateHash 0E9B1B50, 1046BF10, 00000000, 0, 00000000, 0, 00000000
TRACE( "%p, %p, %p, %u, %p, %u, %08x - stub\n", algorithm, handle, object, objectlen, secret, secretlen, flags );

bcrypt:BCryptImportKeyPair 12A9F898, 00000000, L"ECCPUBLICBLOB", 0F6E73DC, 17884DD0, 104, 00000000
TRACE("%p, %p, %s, %p, %p, %u, %p, %u, %u\n", algorithm, decrypt_key, debugstr_w(type), key, object, object_len, input, input_len, flags);

instead of a human readable algorithm or input, you get a pointer.
Shouldn't we get the original data as well in the output of all the bcrypt functions so keys, input and output data are logged directly?
Locked