CRL downloading path from CRL Distribution Points extension does not always work #1
Assignees
Labels
Comments
gganis
pushed a commit
that referenced
this issue
Oct 10, 2017
xlBuff was being defined in two separate compilation units,
thus violating C++'s one-definition-rule. The linker did not
complain, since the two symbols were defined in two different
libraries loaded at runtime.
Caught by ASan:
==10109==ERROR: AddressSanitizer: odr-violation (0x00000144a5e0):
[1] size=80 'XrdGlobal::xlBuff' /home/gbitzes/xrootd/src/Xrd/XrdConfig.cc:94:11
[2] size=80 'XrdGlobal::xlBuff' /home/gbitzes/xrootd/src/Xrd/XrdBuffer.cc:73:11
These globals were registered at these points:
[1]:
#0 0x435b40 (/home/gbitzes/xrootd/build-asan-clang/install/bin/xrootd+0x435b40)
#1 0x51eee9 (/home/gbitzes/xrootd/build-asan-clang/install/bin/xrootd+0x51eee9)
[2]:
#0 0x435b40 (/home/gbitzes/xrootd/build-asan-clang/install/bin/xrootd+0x435b40)
#1 0x7f7a70ceb41b (/home/gbitzes/xrootd/build-asan-clang/install/lib64/libXrdUtils.so.2+0x12441b)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The reason is that the URL in the CA certificate extension is the one of the ROOT CA is a ROOT CA exists. The solution is to use always the 'CRL Distribution Points' extension from the end-point certificate, but this requires a change in loading logic.
The text was updated successfully, but these errors were encountered: