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

Update to 24.09 troubles ... #387

Open
sebres opened this issue Dec 17, 2024 · 7 comments
Open

Update to 24.09 troubles ... #387

sebres opened this issue Dec 17, 2024 · 7 comments

Comments

@sebres
Copy link
Collaborator

sebres commented Dec 17, 2024

Trying to merge mainline 24.09, there is some crossing of hashers (introduced in 24.09) by its registration:

24.09 (0x208):

REGISTER_HASHER(CMd5Hasher, 0x208, "MD5", MD5_DIGEST_SIZE)

7-Zip ZS (0x207):

REGISTER_HASHER(CMD5Hasher, 0x207, "MD5", MD5_DIGEST_LENGTH)


24.09 (0x222 and 0x223):

REGISTER_SHA512_HASHER (Sha384Hasher, 0x222, "SHA384", SHA512_384_DIGEST_SIZE)
REGISTER_SHA512_HASHER (Sha512Hasher, 0x223, "SHA512", SHA512_DIGEST_SIZE)

7-Zip ZS (0x209 and 0x208):

REGISTER_HASHER(CSHA512Hasher, 0x209, "SHA512", SHA512_DIGEST_LENGTH)

REGISTER_HASHER(CSHA384Hasher, 0x208, "SHA384", SHA384_DIGEST_LENGTH)


@mcmilk what would you suggest here:

  1. drop that modules introduced in 24.09 and use 7-Zip ZS (inclusive registration IDs)
  2. drop 7-Zip ZS modules and use modules introduced in 24.09 (inclusive registration IDs of them)
  3. drop 7-Zip ZS modules and use modules introduced in 24.09 (but adjust registration IDs to 7-Zip ZS)
  4. mix of both, somehow (they deviate by their case-sensitivity and name, CMd5Hasher vs CMD5Hasher, but what is about their numbers)?
  5. alternative?

By the way, have you talked to Igor about a possible merge of 7-Zip ZS (in parts or completely)? Is there any chance for that?..

@mcmilk
Copy link
Owner

mcmilk commented Dec 18, 2024

We can remove the own hashes, when Igor added them.
The IDs are not important here. I will take also a look to it today.

Edit: I think one hash was not properly added by me last time, so the hashsum was wrong also.

@sebres
Copy link
Collaborator Author

sebres commented Dec 18, 2024

Edit: I think one hash was not properly added by me last time, so the hashsum was wrong also.

Which one?

@mcmilk
Copy link
Owner

mcmilk commented Dec 18, 2024

It's listed in issue #336 - the SHA3 thing.

@sebres
Copy link
Collaborator Author

sebres commented Dec 18, 2024

It's listed in issue #336 - the SHA3 thing.

I cannot reproduce it with new branch 24.08 (#377 (comment), probably fixed somewhere by merge or conflicts resolving)... I get proper SHA3-256 in any case, by * and by direct menu items.
So the issue #336 could be closed if it gets merged.

@sebres
Copy link
Collaborator Author

sebres commented Dec 18, 2024

Found it:
4f9c3eb#diff-3efab4a12e4465b384048d18e8a8356e17d932d122f75aa18f56efe815f8c5ceL309-R311

@isarrider
Copy link

Thanks folks...
Thats why I bought you 2 beers recently ;)

@MouriNaruto
Copy link

I think I should provide my opinions which may help.

According to my 7-Zip mainline merging experiences in NanaZip, maybe 7-Zip ZS can separate the extended implementations to the separate dynamic/static library which follow the 7-Zip interfaces ABI for better maintenance.

I use the different GUID scheme to make my extended implementations will not affected by Igor's changes.

Here is my work in progress subproject for create 7-Zip interface definition without 7-Zip source code because Igor may changes a lot in the future like 22.xx to 23.xx.

Kenji Mouri

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants