From: Sascha Hauer <s.hauer@pengutronix.de>
To: Gerd Pauli <gp@high-consulting.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v1] Crypt and decrypt files using password in keystore.
Date: Wed, 25 Apr 2018 10:23:13 +0200 [thread overview]
Message-ID: <20180425082313.ur6rzyepbxhtcvao@pengutronix.de> (raw)
In-Reply-To: <1524487970.8922.2.camel@high-consulting.de>
On Mon, Apr 23, 2018 at 02:52:50PM +0200, Gerd Pauli wrote:
> Hi Sascha,
>
> This is not the same as in Linux Cryptop Api. The goal of this command
> and library is to provide a compatible command with the ccrypt tool
> from linux.
> https://packages.debian.org/stretch/ccrypt
> It is not intended to write a standard AES Crypting Tool.
>
> Please tell me if this is useful for merging like this.
> Then i clean up some spaces in the code and send again ( checkscript ).
Sorry, I don't think adding a crypto implementation that is not using
the crypto API is acceptable for merging. Possible options for
upstreaming would be to either the Rijndael cipher with 128 bit block
size aka AES, based on the Kernel AES implementation or to convert
the Rijndael cipher with 256 bit block size as used by ccrypt to the
existing crypto API.
> If not. Sorry for the dust :-)
Don't worry, it's always nice to see what people do with barebox and
to get a view what might be missing.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2018-04-25 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 8:01 Gerd Pauli
2018-04-22 8:27 ` Oleksij Rempel
2018-04-23 8:13 ` Sascha Hauer
2018-04-23 8:33 ` Oleksij Rempel
2018-04-23 8:39 ` Sascha Hauer
2018-04-23 12:52 ` Gerd Pauli
2018-04-25 8:23 ` Sascha Hauer [this message]
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=20180425082313.ur6rzyepbxhtcvao@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=gp@high-consulting.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