-
Notifications
You must be signed in to change notification settings - Fork 930
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
lxd/instance/driver/qemu: replace sha1 by sha256 in blockNodeName() #12454
Conversation
While this sha1 usage is perfectly fine as it's not used for its security properties, there is no downside to using sha256 instead. On the other hand, not using sha1 anywhere makes auditing this part trivial. Signed-off-by: Simon Deziel <simon.deziel@canonical.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this potentially change the device name of the disk inside the guest? In that case we cannot accept the patch as it will potentially change the devices that users are expecting to see inside the guest.
@tomponline while I didn't test, I would think it doesn't because commit 55228ba changed the hash a few months after the initial hash was introduced in commit 13ede0e. |
IIRC we had to do that otherwise qemu wouldnt start. |
But please can you try it and see. Thanks |
I followed the reproduction instructions from #11129 and Using QMP (thanks for showing me how to us it btw!) here is what we have for
Which parses as:
And for
Which parses as:
So only the
|
While this sha1 usage is perfectly fine as it's not used for its security properties, there is no downside to using sha256 instead. On the other hand, not using sha1 anywhere makes auditing this part trivial.