Actualy, we are going to retire the XrdHttpVoms plugin as liXrdVoms
plugin works as the 1-for-1 replacement and does all the new things in the
right way. So, no urgent need to update it. It's available in the 4.12.x
series as well as in R5.
On Fri, 26 Jun 2020, Brian P Bockelman wrote:
> @esindril - I fixed a memory leak and got rid of the extra `SSL_get_peer_certificate` call here: https://github.com/esindril/xrootd/pull/2
>
> @ffurano - when checking for leaks, I noticed that `xrdhttpvoms` always leaks a copy of the X509 certificate if there's no VOMS extension present. See: https://gitlab.cern.ch/lcgdm/xrdhttpvoms/-/merge_requests/1. I would also note your change for 0.2.6 hardcodes the XRootD 5 plugin extension (`-5.so`). You might be better served by using the CMake macros which ship with the XRootD RPM as they define the `XROOTD_PLUGIN_VERSION` variable. This way, the build always "does the right thing" according to the compile-time version of xrootd.
>
> I think I'm ready for this to go in once the above PR is merged.
>
> --
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/pull/1224#issuecomment-650480821
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/pull/1224#issuecomment-650483811",
"url": "https://github.com/xrootd/xrootd/pull/1224#issuecomment-650483811",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
