Skip to content

Conversation

@ztravis
Copy link

@ztravis ztravis commented Aug 16, 2024

Two fixes for what I think are upstream issues.
The first is related to PSTs with name-to-id maps that don't have a GUID stream or an Entry stream. I don't think there is any reason to require these to be present or non-empty - in particular, the documentation indicates that a minimal name-to-id map only contains one property (https://learn.microsoft.com/en-us/openspecs/office_file_formats/ms-pst/5161fee7-42b1-4790-8337-411892b0032c), so it can reasonably not have the streams at all.
The second is related to an upstream bug where a return value is getting incorrectly reused, PR here: libyal#133

{
return( 0 );
}
result = 0;
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This variable is used twice - just above, it's the return value of a submethod, but then it's also used later to represent the return value of this method itself. In between, we should make sure to reset it so that the first value doesn't accidentally get used for the second... this method is searching for a matching node and a value of 0 means no such node was found, so it's an appropriate default.

@EverlawKilian EverlawKilian merged commit 0b6edfc into master Aug 19, 2024
@EverlawKilian EverlawKilian deleted the bugfix/two-pst-fixes branch August 19, 2024 17:33
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

Successfully merging this pull request may close these issues.

3 participants