Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sha256 not supported for TPC #7599

Open
Jo-stfc opened this issue Jun 19, 2024 · 3 comments
Open

sha256 not supported for TPC #7599

Jo-stfc opened this issue Jun 19, 2024 · 3 comments
Labels
xroot Targeting affects support for the xroot protocol (either door or pool)

Comments

@Jo-stfc
Copy link

Jo-stfc commented Jun 19, 2024

Hi, back in March I had run into some TPC failures from XRootD 5.6+ to some dcache sites. the error was tracked down to:
org.dcache.xrootd.core.XrootdException: all sender digests are unsupported: [sha256].
sha256 is the new default md algorithm from that version of xrootd and up.
Is sha256 already supported in the latest version of dcache? If not could you add support for it?

@Jo-stfc
Copy link
Author

Jo-stfc commented Jun 19, 2024

xrootd/xrootd#2202 is the original issue where this was identified

@paulmillar paulmillar added the xroot Targeting affects support for the xroot protocol (either door or pool) label Jun 19, 2024
@paulmillar
Copy link
Member

In the above xrootd issue, this comment seems the most relevant.

The underlying problem seems to be that the xroot "GSI" authentication protocol doesn't support a negotiation of which digest algorithm is used. Therefore, when adopting a new digest algorithm, all services must be updated to versions that support a new digest algorithm before that new algorithm is actually used.

The xrootd software has updated their default algorithm. This places a burden on people using that new version to ensure all their xroot-protocol endpoints have been upgraded.

In this case, xrootd4j should be updated to support sha256, with dCache updated to use a version of xrootd4j with that support.

The problem is (likely) independent of TPC. GSI-based direct access from an xrootd client would (likely) also be affected, if that client is using sha256 by default.

@Jo-stfc
Copy link
Author

Jo-stfc commented Jun 19, 2024

thanks Paul, I'll open a new issue on xrootd4j and link this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
xroot Targeting affects support for the xroot protocol (either door or pool)
Projects
None yet
Development

No branches or pull requests

2 participants