Updating DIRACOS2 to OpenSSL 3 #6851
chrisburr
announced in
Announcements
Replies: 3 comments 12 replies
-
@hmiyake Can you look at this and check if you have any storage elements which have issues? (see the annoucment at the top of this page) |
Beta Was this translation helpful? Give feedback.
4 replies
-
The same issue was found at RAL, so we need to wait for them to fix it. |
Beta Was this translation helpful? Give feedback.
2 replies
-
Dunno if it can also affect DIRAC, but Rucio reported performance degradation of some agent (deletion) after moving to openSSL 3.0 see rucio/rucio#6106 for more details. |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We're about to update DIRACOS2 to OpenSSL 3. This has two known consequences:
The second issue is caused by the minimum DH modulus size being increased to 512 bits in OpenSSL 3 (openssl/openssl#9437) and needs to be fixed on the site side. The error from OpenSSL itself is
error:0280007E:Diffie-Hellman routines::modulus too small
.I've prepared this script[1] which can be ran against a DIRAC installation to iterates all storage elements and use an installation of XRootD+OpenSSL 3 on
/cvmfs/lhcb.cern.ch
to see if listing a directory works. The output will show all storage elements that fail regardless of reason. The OpenSSL 3 problem will look something like:Other issues are likely caused by misconfigurations or downtimes.
Please comment here after trying it so we know how many installations are ready for OpenSSL 3.
[1] Click to show script
Beta Was this translation helpful? Give feedback.
All reactions