[issue50] gpgme is not largefile-safe

Marc Mutz <[email protected]>
Newsgroups gmane.comp.encryption.gpg.gpa.devel
Message-ID <[email protected]>
New submission from Marc Mutz <[email protected]>:

gpgme uses off_t, size_t et al in it's public function signatures, but fails to 
provide two versions for each such function (one for sizeof(off_t) == 8 and one 
for sizeof(off_t) == 4). 
 
Because on 32bit-Linux, application developers are free to choose their off_t's 
size with e.g. -D_FILE_OFFSET_BITS=64, this leads to very subtle bugs in 
applications using an eight-byte off_t. 
 
As an example, try running make check in libkdenetwork/qgpgme/tests. The seeks 
fail because gpgme and qgpgme's off_t's differ in size (gpgme: 4; qgpgme: 8). 
Thus callbacks are passed corrupted data and fail for one reason or another. 
 
Thanks to dfaure for finding this one.

----------
assignedto: Marcus.Brinkmann
messages: 181
nosy: Marcus.Brinkmann, marc
priority: urgent
status: unread
title: gpgme is not largefile-safe
topic: GPGME
______________________________________________________
Aegypten issue tracker <[email protected]>
<https://intevation.de/roundup/aegypten/issue50>
______________________________________________________
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.