-
Notifications
You must be signed in to change notification settings - Fork 73
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
PRC seems to ignore the "irods_default_hash_scheme" in the environment.json #610
Comments
How did you upload the data for the iCommands example? I'm assuming you used I see that
That would mean that the checksum only needs to be calculated on the server side, and it would appear that it uses the hash scheme configured for that server. What you're looking for, I think, is the equivalent of
This feature uses You could try using I'll mark this as a bug, but I view it more as a missing feature rather than something not working. We can play with the labels. :) @d-w-moore - Does that seem right? Am I missing something? |
I am sorry, I forgot to copy that command over. Indeed I used:
And the version of the icommands is 4.3.1-0~bionic. |
In case this is news - there is a little section on checksums in the README... https://github.com/irods/python-irodsclient?tab=readme-ov-file#computing-and-retrieving-checksums |
@trel What's our milestone to be for this one? |
Let's get the remaining issues for 2.1.1 resolved and handle this in 3.0. |
Yep |
While transferring data I noticed that the iRODS server uses different hash schemes for the checksums depending on the client I use.
In my irods_environment.json I set the checksum algorithm as below:
On the server
sha256
is the default checksum algorithm.When I use the icommands to upload data, the data is checked by md5 sums:
When I transfer data with the PRC v 2.0.1.
sha2
is used as checksum algorithm:Is there an extra parameter which I have to pass to the PRC to ensure that the data is checksummed by
md5
?The text was updated successfully, but these errors were encountered: