Hi Elvin,
Not at all. You can't do what you want to do without using the XrdCrypto
library. I was saying that I'd like XrdHttpProtocol.cc refactored so that
al the security related stuff, especially that deals with XrdCrypto be
moved to a separate file for clarity. The changes to XrdCrypto are fine
other than passing the ssl object to it; which can be easily avoided.
Apparently, my final "points" comments were not clear. If not, other than
this, please tell me what is not still clear.
Andy
On Wed, 1 Jul 2020, Elvin Sindrilaru wrote:
> Hi Andy,
>
> Just for me to understand, you propose to drop the changes in XrdCrypto and keep all this certificate handling business isolated in the XrdHttp part?
>
> Thanks,
> Elvin
>
> --
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/pull/1231#issuecomment-652254218
—
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/1231#issuecomment-652590561",
"url": "https://github.com/xrootd/xrootd/pull/1231#issuecomment-652590561",
"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