public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Richard Retanubun <richardretanubun@ruggedcom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] sha256_crypt for uboot
Date: Wed, 27 Jun 2012 10:46:57 -0400	[thread overview]
Message-ID: <4FEB1CE1.609@ruggedcom.com> (raw)

Hello,

I am working on a project to allow uboot to authenticate users by using the same sha256_crypt function that Linux user-space use for libcrypt
[ref] http://www.akkadia.org/drepper/SHA-crypt.txt

We chose sha256 because uboot already have support for doing sha256 hashes, I am wondering about a few things:
1. Has this been attempted before?

2. If I want to make a test command for a proof of concept using crypt(), how do I modify the Makefile to allow a
    command to statically link to libcrypt? hacking it into the Makefile's $(PLATFORM_LIBS)?

3. Once I am done porting sha256_crypt to use it using the facilities uboot has, is there any hope of getting this mainlined when I am done?
    If there is a policy to not unnecessarily add crypto algorithm, then I'll just keep it all in one file to reduce risk of merge conflict.
    If there is interest to mainline this, then I'll stage the supporting functions that uboot does not have yet (mempcpy, stpcpy, etc) into
    separate files.

Thank you for everyone's time
-- 
Richard Retanubun

             reply	other threads:[~2012-06-27 14:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27 14:46 Richard Retanubun [this message]
2012-07-05  9:59 ` [U-Boot] sha256_crypt for uboot Albert ARIBAUD
2012-07-09 13:50   ` Richard Retanubun
2012-07-09 14:12     ` Albert ARIBAUD
2012-07-09 14:55       ` Richard Retanubun
2012-07-09 15:56         ` Albert ARIBAUD
2012-07-09 19:38     ` Wolfgang Denk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FEB1CE1.609@ruggedcom.com \
    --to=richardretanubun@ruggedcom.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox