![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.netbsd.org] / pkgsrc / security / gpgme
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.30 / (download) - annotate - [select for diffs], Thu Aug 11 11:15:00 2011 UTC (9 months, 2 weeks ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2012Q1-base,
pkgsrc-2012Q1,
pkgsrc-2011Q4-base,
pkgsrc-2011Q4,
pkgsrc-2011Q3-base,
pkgsrc-2011Q3,
HEAD
Changes since 1.29: +9 -10
lines
Diff to previous 1.29 (colored)
Changes 1.3.1: * Ported to Windows CE. * Detect GPG versions not supporting ---passwd.
Revision 1.29 / (download) - annotate - [select for diffs], Fri Mar 4 11:34:12 2011 UTC (14 months, 3 weeks ago) by obache
Branch: MAIN
CVS Tags: pkgsrc-2011Q2-base,
pkgsrc-2011Q2,
pkgsrc-2011Q1-base,
pkgsrc-2011Q1
Changes since 1.28: +2 -2
lines
Diff to previous 1.28 (colored)
Use AC_LINK_IFELSE instead of AC_COMPILE_IFELSE for __thread, or unwanted detect of TLS support on NetBSD-5.1.
Revision 1.28 / (download) - annotate - [select for diffs], Thu Mar 3 11:39:47 2011 UTC (14 months, 3 weeks ago) by adam
Branch: MAIN
Changes since 1.27: +10 -13
lines
Diff to previous 1.27 (colored)
Changes 1.3.0: * GPGME does not come with an internal libassuan version anymore. The external libassuan 1.1.0 release or later is required. For application programmers on systems that can resolve inter-library dependencies at runtime, this is a transparent change. * New engine GPGME_PROTOCOL_G13 to support the new g13 tool. * New engine GPGME_PROTOCOL_UISERVER to support UI Servers. * New API to change the passpgrase of a key.
Revision 1.27 / (download) - annotate - [select for diffs], Sun Nov 15 18:41:55 2009 UTC (2 years, 6 months ago) by drochner
Branch: MAIN
CVS Tags: pkgsrc-2010Q4-base,
pkgsrc-2010Q4,
pkgsrc-2010Q3-base,
pkgsrc-2010Q3,
pkgsrc-2010Q2-base,
pkgsrc-2010Q2,
pkgsrc-2010Q1-base,
pkgsrc-2010Q1,
pkgsrc-2009Q4-base,
pkgsrc-2009Q4
Changes since 1.26: +9 -12
lines
Diff to previous 1.26 (colored)
update to 1.1.8 changes: -bugfixes -API extensions -documentation improvement -The encoding of gpgme_data_t objects can affect the output encoding of export, sign and encrypt operations now -Using GPGME_KEYLIST_MODE_LOCAL combined with GPGME_KEYLIST_MODE_EXTERN is now supported
Revision 1.26 / (download) - annotate - [select for diffs], Sun Mar 25 00:48:08 2007 UTC (5 years, 2 months ago) by joerg
Branch: MAIN
CVS Tags: pkgsrc-2009Q3-base,
pkgsrc-2009Q3,
pkgsrc-2009Q2-base,
pkgsrc-2009Q2,
pkgsrc-2009Q1-base,
pkgsrc-2009Q1,
pkgsrc-2008Q4-base,
pkgsrc-2008Q4,
pkgsrc-2008Q3-base,
pkgsrc-2008Q3,
pkgsrc-2008Q2-base,
pkgsrc-2008Q2,
pkgsrc-2008Q1-base,
pkgsrc-2008Q1,
pkgsrc-2007Q4-base,
pkgsrc-2007Q4,
pkgsrc-2007Q3-base,
pkgsrc-2007Q3,
pkgsrc-2007Q2-base,
pkgsrc-2007Q2,
pkgsrc-2007Q1-base,
pkgsrc-2007Q1,
cwrapper,
cube-native-xorg-base,
cube-native-xorg
Changes since 1.25: +2 -1
lines
Diff to previous 1.25 (colored)
Fix build on DragonFly.
Revision 1.25 / (download) - annotate - [select for diffs], Fri Mar 23 20:04:13 2007 UTC (5 years, 2 months ago) by drochner
Branch: MAIN
Changes since 1.24: +11 -10
lines
Diff to previous 1.24 (colored)
update to 1.1.4 this fixes the same problem which was fixed by gpg-1.4.7: depending on use, additional text could get through undetected this gpgme uses gpg in a save way -- since we have gpg-1.4.7 in pkgsrc this is kindo belt-and-suspender, but anyway...
Revision 1.24 / (download) - annotate - [select for diffs], Fri Oct 20 15:25:22 2006 UTC (5 years, 7 months ago) by shannonjr
Branch: MAIN
CVS Tags: pkgsrc-2006Q4-base,
pkgsrc-2006Q4
Changes since 1.23: +4 -1
lines
Diff to previous 1.23 (colored)
Fix gpgsm option so that it builds and works.
Revision 1.23 / (download) - annotate - [select for diffs], Wed Jul 19 22:59:59 2006 UTC (5 years, 10 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2006Q3-base,
pkgsrc-2006Q3
Changes since 1.22: +10 -10
lines
Diff to previous 1.22 (colored)
Update to 1.1.0, based on patches provided by George Michaelson in PR 32761. Noteworthy changes in version 1.1.0 (2005-10-01) ------------------------------------------------ * You can now configure the backend engine file name and home directory to be used, as default and per context. * Information about the recipients of an encrypted text is now available at decryption time. * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt and verify handlers, the information about the plaintext filename, if available is made available in the new field file_name of the respective result structure. * The code for "automagically detecting the thread library" has been removed from libgpgme. It is deprecated since version 0.4.3. Since then, you had to link against libgpgme-pthread for applications using pthread and libgpgme-pth for applications using GNU Pth. The code was removed because it caused compilation problems on systems where the pthread.h header from GNU Pth is available in addition to the system header (FreeBSD 6 and later for example). * There is a new flag for keys and subkeys, is_qualified, which indicates if a key can be used for qualified signatures according to local government regulations. * You can associate a filename with a data object using the new function gpgme_data_set_file_name(). This filename will be stored in the output when encrypting or signing the data and will be returned when decrypting or verifying the output data. * You can now set notation data at signature creation with the new function gpgme_sig_notation_add(). * Interface changes relative to the 1.0.3 release: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ gpgme_set_engine_info NEW gpgme_ctx_get_engine_info NEW gpgme_ctx_set_engine_info NEW gpgme_recipient_t NEW gpgme_decrypt_result_t EXTENDED: New field recipients. gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo. gpgme_decrypt_result_t EXTENDED: New field plaintext_filename. gpgme_verify_result_t EXTENDED: New field plaintext_filename. GPGME_STATUS_PLAINTEXT NEW gpgme_key_t EXTENDED: New field is_qualified. gpgme_subkey_t EXTENDED: New field is_qualified. gpgme_data_get_file_name NEW gpgme_data_set_file_name NEW gpgme_sig_notation_flags_t NEW GPGME_SIG_NOTATION_HUMAN_READABLE NEW GPGME_SIG_NOTATAION_CRITICAL NEW gpgme_sig_notation_clear NEW gpgme_sig_notation_add NEW gpgme_sig_notation_get NEW
Revision 1.22 / (download) - annotate - [select for diffs], Wed Mar 1 16:22:21 2006 UTC (6 years, 2 months ago) by drochner
Branch: MAIN
CVS Tags: pkgsrc-2006Q2-base,
pkgsrc-2006Q2,
pkgsrc-2006Q1-base,
pkgsrc-2006Q1
Changes since 1.21: +2 -2
lines
Diff to previous 1.21 (colored)
resolve confusion about different behaviour of getenv_r in librfuncs and NetBSD-current which caused serius lossage: depend on librfuncs>=1.0.7nb1 which implements NetBSD-current's behaviour, change the patch to _gpgme_getenv() accordingly, and bump PKGREVISION
Revision 1.21 / (download) - annotate - [select for diffs], Sat Feb 11 14:11:07 2006 UTC (6 years, 3 months ago) by joerg
Branch: MAIN
Changes since 1.20: +2 -2
lines
Diff to previous 1.20 (colored)
Don't hard-wire -lpthread into gpgme-config, it breaks e.g. mail/balsa2 on DragonFly. Bump revision.
Revision 1.20 / (download) - annotate - [select for diffs], Fri Nov 4 17:16:34 2005 UTC (6 years, 6 months ago) by joerg
Branch: MAIN
CVS Tags: pkgsrc-2005Q4-base,
pkgsrc-2005Q4
Changes since 1.19: +3 -2
lines
Diff to previous 1.19 (colored)
Don't depend on -lpthread as name of the thread library, check in configure using PTHREAD_LIBS / PTHREAD_LDFLAGS and use them to link libgpgme_thread as well.
Revision 1.19 / (download) - annotate - [select for diffs], Fri Aug 12 19:36:53 2005 UTC (6 years, 9 months ago) by drochner
Branch: MAIN
CVS Tags: pkgsrc-2005Q3-base,
pkgsrc-2005Q3
Changes since 1.18: +4 -4
lines
Diff to previous 1.18 (colored)
update to 1.0.3 changes: -license changed to LGPL -changed default for "include certs" to use the backend's setting -bugfixes
Revision 1.18 / (download) - annotate - [select for diffs], Fri Apr 8 15:59:02 2005 UTC (7 years, 1 month ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2005Q2-base,
pkgsrc-2005Q2
Changes since 1.17: +4 -4
lines
Diff to previous 1.17 (colored)
Update to 1.0.2: Noteworthy changes in version 1.0.2 (2004-12-28) ------------------------------------------------ * Changed the license of the library to the GNU Lesser General Public License (LGPL), version 2.1 or later.
Revision 1.17 / (download) - annotate - [select for diffs], Thu Feb 24 13:10:06 2005 UTC (7 years, 3 months ago) by agc
Branch: MAIN
CVS Tags: pkgsrc-2005Q1-base,
pkgsrc-2005Q1
Changes since 1.16: +2 -1
lines
Diff to previous 1.16 (colored)
Add RMD160 digests.
Revision 1.16 / (download) - annotate - [select for diffs], Sun Nov 7 13:18:16 2004 UTC (7 years, 6 months ago) by jmmv
Branch: MAIN
CVS Tags: pkgsrc-2004Q4-base,
pkgsrc-2004Q4
Changes since 1.15: +2 -2
lines
Diff to previous 1.15 (colored)
Ew... also let this work if getenv_r returns no errors...
Revision 1.15 / (download) - annotate - [select for diffs], Sun Nov 7 13:11:30 2004 UTC (7 years, 6 months ago) by jmmv
Branch: MAIN
Changes since 1.14: +2 -2
lines
Diff to previous 1.14 (colored)
Now that librfuncs' getenv_r returns ENOENT when the variable is not defined in the environment, we can handle this case properly from here. I.e., treat ENOENT as if no error happened, and return NULL in the 'value' parameter (as the function documentation says). Finally fixes PR pkg/27884. Bump PKGREVISION to 2.
Revision 1.14 / (download) - annotate - [select for diffs], Sat Nov 6 17:40:15 2004 UTC (7 years, 6 months ago) by jmmv
Branch: MAIN
Changes since 1.13: +3 -2
lines
Diff to previous 1.13 (colored)
Let this build if gnupg 1.2.x is not installed (i.e., gnupg-devel exists). A test program was trying to run 'gpg', bypassing the binary name given through the --with-gpg flag to configure. XXX This still has a chance to break. If gnupg-devel is built w/o the gpgsm option and gpgme is being built w/ it, no gpg binary will be found. This is one of the those damages produced by build options...
Revision 1.13 / (download) - annotate - [select for diffs], Thu Nov 4 20:41:21 2004 UTC (7 years, 6 months ago) by shannonjr
Branch: MAIN
Changes since 1.12: +6 -4
lines
Diff to previous 1.12 (colored)
1) Revised gpg_strerror_r to match comments in using strerror_r 2) Revised configure to perform header check for rfuncs.h 3) Revised files referencing getenv_r, strerror_r and ttyname_r to include <rfuncs.h> if HAVE_RFUNCS_H
Revision 1.12 / (download) - annotate - [select for diffs], Wed Nov 3 15:48:31 2004 UTC (7 years, 6 months ago) by jmmv
Branch: MAIN
Changes since 1.11: +2 -2
lines
Diff to previous 1.11 (colored)
Add missing blank line after the NetBSD CVS tag in patch-ab.
Revision 1.11 / (download) - annotate - [select for diffs], Sat Oct 23 15:00:48 2004 UTC (7 years, 7 months ago) by shannonjr
Branch: MAIN
Changes since 1.10: +6 -4
lines
Diff to previous 1.10 (colored)
1) Updated to gpgme-1.0.1. This is a bug fix release. 2) Added optional support for OpenPGP/MIME and SMIME via gnupg-devel as described here: http://www.gnupg.org/aegypten2/
Revision 1.10 / (download) - annotate - [select for diffs], Wed Oct 20 19:09:12 2004 UTC (7 years, 7 months ago) by jmmv
Branch: MAIN
Changes since 1.9: +4 -3
lines
Diff to previous 1.9 (colored)
Update to 1.0.0: * Version 1.0.0! We are proud to present you with a thoroughly tested and stable version of the GPGME library. A big Thank You! to all the people who made this possible. The development will be branched into a stable 1.x.y series and the head. * The gpgme.m4 macro supports checking the API version. Just prepend it to the required version string, separated by a colon. For example, this release has the version "1:1.0.0". The last release to which this version is (mostly) ABI compatible is "1:0.4.2", which is the default required version.
Revision 1.9 / (download) - annotate - [select for diffs], Sun Aug 22 17:52:26 2004 UTC (7 years, 9 months ago) by recht
Branch: MAIN
CVS Tags: pkgsrc-2004Q3-base,
pkgsrc-2004Q3
Changes since 1.8: +3 -3
lines
Diff to previous 1.8 (colored)
update to gpgme-0.9.0 Noteworthy changes in version 0.9.0 (unreleased) ------------------------------------------------ * The type gpgme_key_t has now a new field keylist_mode that contains the keylist mode that was active at the time the key was retrieved. * The type gpgme_decrypt_result_t has a new field "wrong_key_usage" that contains a flag indicating that the key should not have been used for encryption. * Verifying a signature of a revoked key gives the correct result now (GPG_ERR_CERT_REVOKED error code). * Clarified that the error code GPG_ERR_NO_DATA from the decrypt & verify operations still allows you to look at the signature verification result. * Clarified that patterns in keylisting operations have an upper limit, and thus are not suited to list many keys at once by their fingerprint. Also improve the error message if the pattern is too long for the CMS protocol to handle. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ gpgme_key_t EXTENDED: New field keylist_mode. gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Set the 0.9.0 versions as BUILDLINK_DEPENDS in the buildlink3.mk for the library major version changes.
Revision 1.8 / (download) - annotate - [select for diffs], Sat Aug 21 10:54:47 2004 UTC (7 years, 9 months ago) by markd
Branch: MAIN
Changes since 1.7: +4 -4
lines
Diff to previous 1.7 (colored)
Update to 0.4.7. Noteworthy changes in version 0.4.7 (2004-04-29) ------------------------------------------------ * Correctly initialize the fields expired, revoked, invalid, and disabled in the gpgme_key_t structures. * A bug fix: The flag wrong_key_usage of gpgme_signature_t was accidently of type int instead unsigned int. Noteworthy changes in version 0.4.6 (2004-04-06) ------------------------------------------------ * Bug fixes Noteworthy changes in version 0.4.5 (2004-03-07) ------------------------------------------------ * GPGME is now compiled with LFS (large file support) by default. * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of the listed keys. * New interface gpgme_cancel() that can be used to cancel asynchronous operations. Noteworthy changes in version 0.4.4 (2004-01-12) ------------------------------------------------ * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has been renamed to "sig_class", to avoid clash with C++ compilers. In the C API, the old name "class" has been preserved for backwards compatibility, but is deprecated.
Revision 1.7 / (download) - annotate - [select for diffs], Sun Dec 14 15:05:01 2003 UTC (8 years, 5 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2004Q2-base,
pkgsrc-2004Q2,
pkgsrc-2004Q1-base,
pkgsrc-2004Q1
Changes since 1.6: +4 -3
lines
Diff to previous 1.6 (colored)
Update to 0.4.3 (for gpa-0.7.0): Noteworthy changes in version 0.4.3 (2003-10-06) ------------------------------------------------ * libgpgme should not be used for threaded programs anymore. This never worked reliably in all cases, because you had to be careful about the linking order and libtool wouldn't do that for you automatically. Instead, now you have to link against libgpgme-pthread for applications using pthread and libgpgme-pth for applications using GNU Pth. The old code for automagically detecting the thread library is still part of libgpgme, but it is DEPRECATED. * There are new automake macros AM_PATH_GPGME_PTH and AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS, GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These variables of course also include the configuration for the thread package itself. Alternatively, use libtool. * gpgme_strerror_r as a thread safe variant of gpgme_strerror was added. * gpgme-config doesn't support setting the prefix or exec prefix anymore. I don't think it ever worked correctly, and it seems to be pointless. * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID provided was not unique, instead returning the first matching key. * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate, that indicates if the key can be used for authentication. * gpgme_signature_t's status field is now correctly set to an error with error code GPG_ERR_NO_PUBKEY if public key is not found. * gpgme_new_signature_t's class field is now an unsigned int, rather than an unsigned long (the old class field is preserved for backwards compatibility). * A new function gpgme_set_locale() is provided to allow configuring the locale for the crypto backend. This is necessary for text terminals so that programs like the pinentry can be started with the right locale settings for the terminal the application is running on, in case the terminal has different settings than the system default (for example, if it is a remote terminal). You are highly recommended to call the following functions directly after gpgme_check_version: #include <locale.h> setlocale (LC_ALL, ""); gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL)); gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL)); GPGME can not do this for you, as setlocale is not thread safe, and there is no alternative. * The signal action for SIGPIPE is now set to SIG_IGN by gpgme_check_version, instead the first time a crypto engine is started (which is not well defined). * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160, TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440 to CRC24RFC2440. For now, these strings can be used as the MIC parameter for PGP/MIME (if appropriately modified). Noteworthy changes in version 0.4.2 (2003-07-30) ------------------------------------------------ * Allow gpg-error to be in non-standard place when linking the test suite. * Configure will fail now if gpg-error can not be found. * Fixed initialized memory backed data objects for writing, which caused the test program to crash (but only on Mac OS, surprisingly). * Eliminate use of C99 constructs. * Small improvements to the manual. Noteworthy changes in version 0.4.1 (2003-06-06) ------------------------------------------------ This is the release that 0.4.0 should have been. There are many interface changes, please see below for the details. The changes are sometimes the result of new functionality, but more often express a paradigm shift. Others are an overdue cleanup to get GPGME in line with the GNU coding standards and to make the interface more self-consistent. Here is an overview on the changes: All types have been renamed to conform to the GNU coding standards, most of the time by keeping the whole name in lowercase and inserting underscores between words. All operations consistently only accept input parameters in their invocation function, and return only an error code directly. Further information about the result of the operation has to be retrieved afterwards by calling one of the result functions. This unifies the synchronous and the asynchronous interface. The error values have been completely replaced by a more sophisticated model that allows GPGME to transparently and accurately report all errors from the other GnuPG components, irregardless of process boundaries. This is achieved by using the library libgpg-errors, which is shared by all GnuPG components. This library is now required for GPGME. The results of all operations are now provided by pointers to C structs rather than by XML structs or in other ways. Objects which used to be opaque (for example a key) are now pointers to accessible structs, so no accessor functions are necessary. Backward compatibility is provided where it was possible without too much effort and did not collide with the overall sanitization effort. However, this is only for ease of transition. NO DEPRECATED FUNCTION OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY. Recommendations how to replace deprecated or removed functionality can be found within the description of each change. What follows are all changes to the interface and behaviour of GPGME in detail. * If gpgme.h is included in sources compiled by GCC 3.1 or later, deprecated attributes will warn about use of obsolete functions and type definitions. You can suppress these warnings by passing -Wno-deprecated-declarations to the gcc command. * The following types have been renamed. The old types are still available as aliases, but they are deprecated now: [complete list in NEWS file] * gpgme_error_t is now identical to gpg_error_t, the error type provided by libgpg-error. More about using libgpg-error with GPGME can be found in the manual. All error symbols have been removed! * All functions and types in libgpg-error have been wrapped in GPGME. The new types are gpgme_err_code_t and gpgme_err_source_t. The new functions are gpgme_err_code, gpgme_err_source, gpgme_error, gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno, gpgme_err_code_from_errno, gpgme_err_code_to_errno, gpgme_strsource. * GPGME_ATTR_IS_SECRET is not anymore representable as a string. * GnuPG 1.2.2 is required. The progress callback is now also invoked for encrypt, sign, encrypt-sign, decrypt, verify, and decrypt-verify operations. For verify operations on detached signatures, the progress callback is invoked for both the detached signature and the plaintext message, though. * gpgme_passphrase_cb_t has been changed to not provide a complete description, but the UID hint, passphrase info and a flag indicating if this is a repeated attempt individually, so the user can compose his own description from this information. The passphrase is not returned as a C string, but must be written to a file descriptor directly. This allows for secure passphrase entries. The return type has been changed to gpgme_error_t value. This allowed to remove the gpgme_cancel function; just return the error code GPG_ERR_CANCELED in the passphrase callback directly. * gpgme_edit_cb_t has been changed to take a file descriptor argument. The user is expected to write the response to the file descriptor, followed by a newline. * The recipients interface has been removed. Instead, you use NULL-terminated lists of keys for specifying the recipients of an encryption operation. Use the new encryption flag GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of the keys (but note that in general this is not a good idea). This change has been made to the prototypes of gpgme_op_encrypt, gpgme_op_encrypt_start, gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start. The export interface has been changed to use pattern strings like the keylist interface. Thus, new functions gpgme_op_export_ext and gpgme_op_export_ext_start have been added as well. Now the prototypes of gpgme_op_export_start and gpgme_op_export finally make sense. * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status summary anymore. Use gpgme_get_sig_status to retrieve the individual stati. * gpgme_io_cb_t changed from a void function to a function returning a gpgme_error_t value. However, it will always return 0, so you can safely ignore the return value. * A new I/O callback event GPGME_EVENT_START has been added. The new requirement is that you must wait until this event until you are allowed to call the I/O callback handlers previously registered for this context operation. Calling I/O callback functions for this context operation before the start event happened is unsafe because it can lead to race conditions in a multi-threaded environment. * The idle function feature has been removed. It was not precisely defined in a multi-threaded environment and is obsoleted by the user I/O callback functions. If you still need a simple way to call something while waiting on one or multiple asynchronous operations to complete, don't set the HANG flag in gpgme_wait (note that this will return to your program more often than the idle function did). * gpgme_wait can return NULL even if hang is true, if an error occurs. In that case *status contains the error code. * gpgme_get_engine_info was radically changed. Instead an XML string, an info structure of the new type gpgme_engine_info_t is returned. This makes it easier and more robust to evaluate the information in an application. * The new function gpgme_get_protocol_name can be used to convert a gpgme_protocol_t value into a string. * The status of a context operation is not checked anymore. Starting a new operation will silently cancel the previous one. Calling a function that requires you to have started an operation before without doing so is undefined. * The FPR argument to gpgme_op_genkey was removed. Instead, use the gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t pointer to a structure which contains the fingerprint. This also works with gpgme_op_genkey_start. The structure also provides other information about the generated keys. * The new gpgme_op_import_result function provides detailed information about the result of an import operation in gpgme_import_result_t and gpgme_import_status_t objects. Thus, the gpgme_op_import_ext variant is deprecated. * The new gpgme_op_sign_result function provides detailed information about the result of a signing operation in gpgme_sign_result_t, gpgme_invalid_key_t and gpgme_new_signature_t objects. * The new gpgme_op_encrypt_result function provides detailed information about the result of an encryption operation in a GpgmeEncryptResult object. * The new gpgme_op_decrypt_result function provides detailed information about the result of a decryption operation in a GpgmeDecryptResult object. * The new gpgme_op_verify_result function provides detailed information about the result of an verify operation in a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_* values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr, gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated, and gpgme_get_notation is removed. * GpgmeTrustItem objects have now directly accessible data, so the gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr accessor functions are deprecated. Also, reference counting is available through gpgme_trust_item_ref and gpgme_trust_item_unref (the gpgme_trust_item_release alias for the latter is deprecated). * Keys are not cached internally anymore, so the force_update argument to gpgme_get_key has been removed. * GpgmeKey objects have now directly accessible data so the gpgme_key_get_string_attr, gpgme_key_get_ulong_attr, gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr functions are deprecated. Also, gpgme_key_release is now deprecated. The gpgme_key_get_as_xml function has been dropped. * Because all interfaces using attributes are deprecated, the GpgmeAttr data type is also deprecated. * The new gpgme_op_keylist_result function provides detailed information about the result of a key listing operation in a GpgmeKeyListResult object. * Now that each function comes with its own result retrieval interface, the generic gpgme_get_op_info interface is not useful anymore and dropped. * The type and mode of data objects is not available anymore. Noteworthy changes in version 0.4.0 (2002-12-23) ------------------------------------------------ * Key generation returns the fingerprint of the generated key. * New convenience function gpgme_get_key. * Supports signatures of user IDs in keys via the new GPGME_KEYLIST_MODE_SIGS keylist mode and the gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr interfaces. The XML info about a key also includes the signatures if available. * New data object interface, which is more flexible and transparent. Lots of interface changes, for details see the included NEWS file.
Revision 1.6 / (download) - annotate - [select for diffs], Tue Mar 11 00:11:31 2003 UTC (9 years, 2 months ago) by salo
Branch: MAIN
CVS Tags: pkgsrc-2003Q4-base,
pkgsrc-2003Q4
Changes since 1.5: +3 -3
lines
Diff to previous 1.5 (colored)
Updated to latest stable version 0.3.15. Changes: - The progress status is sent via the progress callbacks in gpgme_op_edit. - Bug fix for signing operations with explicit signer settings for the CMS protocol.
Revision 1.5 / (download) - annotate - [select for diffs], Sun Dec 22 13:53:04 2002 UTC (9 years, 5 months ago) by chris
Branch: MAIN
CVS Tags: netbsd-1-6-1-base,
netbsd-1-6-1
Changes since 1.4: +3 -3
lines
Diff to previous 1.4 (colored)
Update gpgme to 0.3.14. From NEWS file: Noteworthy changes in version 0.3.14 (2002-12-04) ------------------------------------------------- * GPGME-Plug is now in its own package "cryptplug". * Workaround for a setlocale problem. Fixed a segv related to not correctly as closed marked file descriptors. For full list of changes see ChangeLog. (distfile checked against .sig file)
Revision 1.4 / (download) - annotate - [select for diffs], Sun Nov 24 13:51:34 2002 UTC (9 years, 6 months ago) by chris
Branch: MAIN
Changes since 1.3: +3 -3
lines
Diff to previous 1.3 (colored)
Update gpgme to 0.3.13. Only change (other than version) is: * config.sub, config.guess: Updated from ftp.gnu.org/gnu/config to version 2002-11-08.
Revision 1.3 / (download) - annotate - [select for diffs], Sun Oct 27 03:09:14 2002 UTC (9 years, 7 months ago) by chris
Branch: MAIN
Changes since 1.2: +3 -4
lines
Diff to previous 1.2 (colored)
Update gpgme to 0.3.12. Again mostly bug fixes. Now depends on gpg 1.2.0. Don't seem to need patch-ba. Also fix .info file handling.
Revision 1.2 / (download) - annotate - [select for diffs], Mon Aug 26 13:34:16 2002 UTC (9 years, 9 months ago) by mjl
Branch: MAIN
Changes since 1.1: +4 -4
lines
Diff to previous 1.1 (colored)
Update to 0.3.9 * An experimental interface to GnuPG's --edit-key functionality is introduced, see gpgme_op_edit. * The new gpgme_import_ext function provides a convenient access to the number of processed keys. * It is possible to use an outside event loop for the I/O to the crypto engine by setting the I/O callbacks with gpgme_set_io_cbs. * GPGME_ATTR_OTRUST is implemented now. * A first step toward thread safeness has been achieved, see the documentation for details. Supported thread libraries are pthread and Pth. * All error output of the gpgsm backend is send to the bit bucket. * The signature verification functions are extended. Instead of always returning GPGME_SIG_STATUS_GOOD, the functions new codes for expired signatures. * The current passphrase callback and progress meter callback can be retrieved with the new functions gpgme_get_passphrase_cb and gpgme_get_progress_cb respectively. * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this case, symmetric encryption is performed. Note that this requires a passphrase from the user. * More information is returned for X.509 certificates. * Interface changes relative to the 0.3.4 release: * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if some recipients have been invalid, whereas earlier versions succeeded in this case. * gpgme_op_verify now allows to pass an uninitialized data object as its plaintext argument to check for normal and cleartext signatures. The plaintext is then returned in the data object. * New interfaces gpgme_set_include_certs and gpgme_get_include_certs to set and get the number of certifications to include in S/MIME signed messages. * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start to encrypt and sign a message in a combined operation. * New interface gpgme_op_keylist_ext_start to search for multiple patterns. * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute. * Interface changes relative to the 0.3.3 release: * Fix the Makefile in jnlib. * Fix the test suite (hopefully). It should clean up all its state with `make check' now. * Remove erroneous dependency on libgcrypt in jnlib. * There is a Texinfo manual documenting the API. * The gpgme_set_keylist_mode function returns an error, and changed its meaning. It is no longer usable to select between normal and fast mode (newer versions of GnuPG will always be fast), but selects between local keyring, remote keyserver, or both. For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the current setting, a fucntion gpgme_get_keylist_mode was added to retrieve the current mode. * gpgme_wait accepts a new argument STATUS to return the error status of the operation on the context. Its definition is closer to waitpid() now than before. * The LENGTH argument to gpgme_data_new_from_filepart changed its type from off_t to the unsigned size_t. * The R_HD argument to the GpgmePassphraseCb type changed its type from void* to void**. * New interface gpgme_op_trustlist_end() to match gpgme_op_keylist_end(). * The CryptPlug modules have been renamed to gpgme-openpgp and gpgme-smime, and they are installed in pkglibdir by `make install'. * An idle function can be registered with gpgme_register_idle(). * The GpgSM backend supports key generation with gpgme_op_genkey().
Revision 1.1.1.1 / (download) - annotate - [select for diffs] (vendor branch), Sun Mar 17 13:33:40 2002 UTC (10 years, 2 months ago) by uebayasi
Branch: TNF
CVS Tags: pkgviews-base,
pkgviews,
pkgsrc-base,
netbsd-1-6-RELEASE-base,
netbsd-1-6,
netbsd-1-5-PATCH003,
buildlink2-base,
buildlink2
Changes since 1.1: +0 -0
lines
Diff to previous 1.1 (colored)
Initial import of GPGME 0.3.0. From DESCR: GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG easier for applications. It provides a High-Level Crypto API for encryption, decryption, signing, signature verification and key management.
Revision 1.1 / (download) - annotate - [select for diffs], Sun Mar 17 13:33:40 2002 UTC (10 years, 2 months ago) by uebayasi
Branch: MAIN
Initial revision