Open droe opened 5 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
comment.
Stale issues will be closed after an additional 30d of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale
/remove-lifecycle stale
/lifecycle frozen
«I want my bug report timed out without anybody looking at it!» - no one ever
[ ] I have uploaded Diagnostics- irrelevant to the issueExpected behavior
com.docker.
.Actual behavior
Docker.app/Contents/Resources/bin/notary
)com.docker
)kubectl
instead ofcom.docker.kubectl
)These problems lead to various (mostly minor) issues with software inventory, application deployment, personal firewalls, binary whitelisting and security monitoring systems that cannot tell the different binaries apart based on the identifier embedded in the code signature.
Information
Diagnostic logs
Steps to reproduce the behavior
codesign -d -vvvv
to inspect the code signature on each MachO binary.