Hi,

I use the following patch in order to get the current encryption in use:
--- a/soapclient.module
+++ b/soapclient.module
@@ -147,7 +147,7 @@ function soapclient_find_nusoap_library() {

// configuration form
function soapclient_config() {
-
+ global $_soapclient_MCRYPT;
$_soapclient_LIBRARY = variable_get('soapclient_lib', 'auto');

$form = array();

CommentFileSizeAuthor
0001-correct-a-libmcrypt-configuration-not-printed.patch726 bytesbroucaries
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

grub3’s picture

grub3 CreditAttribution: grub3 commented

subscribe.

13rac1’s picture

13rac1 CreditAttribution: 13rac1 commented
Status: Needs review » Needs work

This should be implemented via a function call, not via a global variable.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
CreditAttribution: greggles commented
Priority: Minor » Normal
Status: Needs work » Needs review

I don't understand comment #2. I agree that overall these globals are probably not necessary and can be replaced by a few function calls and get/set paradigm, but I don't see why this fix should be held back on that change.

There's a call later in the function to the global variable:

'!cryptlib' => $_soapclient_MCRYPT != NULL ? 'mcrypt extension' : 'AES128 bundled library',

That threw a notice for me until I made the change suggested in the original post.