Re:Docker Hub Hacked – 190k accounts, GitHub tokens revoked,...
by blattimwind on Saturday April 27, 2019 @06:42AM
(#19764882)
Infosec in 2019: The server I download code from telling me the hash of said code is "certainly an excellent hardening step".
[ Parent
| on HN ]
Re:Docker Hub Hacked – 190k accounts, GitHub tokens revoked,...
by gtsteve on Sunday April 28, 2019 @11:59AM
(#19771813)
Well I was approaching it from the point of view that you verify the image is correct and then you guarantee you'll always use that image and not some other version given that tags are mutable.
Re:Docker Hub Hacked – 190k accounts, GitHub tokens revoked,...
by ithkuil on Saturday April 27, 2019 @01:20PM
(#19766550)
Can't the hash be verified by the client too?
Re:Docker Hub Hacked – 190k accounts, GitHub tokens revoked,...
by subway on Saturday April 27, 2019 @01:47PM
(#19766700)
Sure, but who tells the client what the correct hash is?
Re:Docker Hub Hacked – 190k accounts, GitHub tokens revoked,...
by krferriter on Saturday April 27, 2019 @05:06PM
(#19767638)
If you're the entity who created the image you can retain the original hash and verify it against the downloaded copies. But that kind of defeats the purpose of being able to download docker images across distributed hosts.
They'd really need to be signatures attached to the images, not just hashes.