Although I fundamentally disagree that this is a GDPR concern, we've gone ahead and removed the email address in both XF1 and XF2 anyway. This place is the only place that a user's email address is "leaked" to a moderator, so at best it seems inconsistent.
It's a little bit icky, but it's not actually that difficult.
I'd just extend logDownload and use:
$attachments = $version->Attachments;
if ($attachments->count() > 1)
$attachmentId = $this->app()->inputFilterer()->filter('file', 'uint');
$attachment = $attachments[$attachmentId];
We can only provide support to licensed customers. Once you associate your forum username to the Forum users page in the customer area you will be able to post in the Development discussions forum for help.
Just wanted to offer an alternative to editing the core code directly if you need to use this as a workaround. Instead, you can actually make the changes by editing your config.php file and extending the session.public container:
This isn't actually a bug with the software itself, so not something that belongs here. Either way, there's not a lot we can do about it if those software vendors are separately or jointly blocking reCAPTCHA. That's something to be resolved on their side.