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

Malformed directory entry (invalid storage start sector: 0x3a) #27

Closed
ikrivosheev opened this issue Jun 24, 2022 · 3 comments
Closed

Malformed directory entry (invalid storage start sector: 0x3a) #27

ikrivosheev opened this issue Jun 24, 2022 · 3 comments

Comments

@ikrivosheev
Copy link
Contributor

Hello! Thank you for the great library. I get error when try to open file: Custom { kind: InvalidData, error: "Malformed directory entry (invalid storage start sector: 0x3a)" }

File: qalt_attach_240-2087.zip

@mdsteele
Copy link
Owner

Thanks! This is yet another case where the cfb crate is being stricter than really necessary. Section 2.6.3 of the CFB spec says that storage directory entries should have the Starting Sector Location and Stream Size fields set to zero, but the CFB file you attached has nonzero values for both (in at least one storage entry). Just like with issue #26, we can just ignore the invalid values and pretend they were set to zero. I'll make a fix.

@ikrivosheev
Copy link
Contributor Author

@mdsteele thank you for the fix! Can you make a fix release with these changes?

@mdsteele
Copy link
Owner

Yep, just published v0.7.2 with this fix.

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

2 participants