Skip to content

Conversation

@weshaggard
Copy link
Member

Plumb options to force repack binaries that were signed externally
otherwise the repacking command will not pack the extracted signed
binaries and only repack the unsigned binaries which is not what we
want.

cc @JohnTortugo

@markwilkie
Copy link
Member

cc/ @riarenas and @jcagme as @JohnTortugo is OOF for a while.

@weshaggard weshaggard force-pushed the EnableForceRepackOption branch from 6610514 to 3adc978 Compare March 1, 2019 23:31
Copy link
Contributor

@JohnTortugo JohnTortugo left a comment

Choose a reason for hiding this comment

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

LGTM. Just some comments about verbosity.

}
else
{
_log.LogMessage($"Assembly {file.FullPath} is signed properly");
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this will be too verbose.

Copy link
Member Author

Choose a reason for hiding this comment

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

It could be but I find that for the signing step it is good to be specific about which files were checked and valid. I will change the messages to Low importance to help allow people to control what is dumped to the log.

}
else
{
_log.LogMessage($"Container {file.FullPath} has a signature marker.");
Copy link
Contributor

Choose a reason for hiding this comment

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

Same as above. May be too verbose?

}

TrackFile(file, ContentUtil.StringToHash(stringHash), false);
// if the content has of the file doesn't match the hash in file path then the file has changed
Copy link
Contributor

Choose a reason for hiding this comment

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

typo on "content has of the"


// When reading from an existing cache use the already computed hash from the directory
// structure instead of computing it from the file because things like signing
// might have changed the hash but we want to still use the same hash of the unsigned
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this comment still accurate?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes this is still accurate. The has might be different.

Plumb options to force repack binaries that were signed externally
otherwise the repacking command will not pack the extracted signed
binaries and only repack the unsigned binaries which is not what we
want.
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