Skip to content
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

[digest] add sha1verify command #57

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

bmwiedemann
Copy link
Contributor

@bmwiedemann bmwiedemann commented Oct 10, 2016

This allows to get a trusted image with known digest value
that is embedded in the ipxe script

example usage:
kernel http://boot.ipxe.org/memtest.0
sha1verify memtest.0 5d78d4c7e97c99bca3d3dff602b84dde5b70c5bf
boot

an md5verify cmd could easily be added,
but would not be recommended to use
because of known weaknesses with MD5 digests

This allows to get a trusted image with known digest value
that is embedded in the ipxe script
making http downloads safe to use this way

example usage:
kernel http://boot.ipxe.org/memtest.0
sha1verify memtest.0 5d78d4c7e97c99bca3d3dff602b84dde5b70c5bf
boot

an md5verify cmd could easily be added,
but would not be recommended to use
because of known weaknesses with MD5 digests
because we are only ever interested
in the hex string of the digest value
@bmwiedemann
Copy link
Contributor Author

ping

@oxypwn
Copy link

oxypwn commented Mar 30, 2017

There is weaknesses in sha1 to; https://shattered.io Go for sha256 at least.

@mcb30
Copy link
Member

mcb30 commented Mar 30, 2017

It needs a substantial cleanup before being mergeable. Also, rather than argue over which digest algorithm commands should exist, we should be able to use whichever digests are compiled in (which is controlled by config/crypto.h); this will require either a command syntax such as "digest sha256 " with digests collected via the linker table mechanism, or per-digest files linked in as necessary (as used by e.g. crypto/mishmash/rsa_sha256.c).

@bmwiedemann
Copy link
Contributor Author

I just noticed that this is similar to #34 but I cannot follow up on either. So, if someone wants to pick this up, I'd welcome it.

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.

None yet

3 participants