lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190327201441.ikw76qzpgzm6t35b@altlinux.org>
Date:   Wed, 27 Mar 2019 23:14:41 +0300
From:   Vitaly Chikunov <vt@...linux.org>
To:     Mimi Zohar <zohar@...ux.ibm.com>
Cc:     Herbert Xu <herbert@...dor.apana.org.au>,
        David Howells <dhowells@...hat.com>,
        Dmitry Kasatkin <dmitry.kasatkin@...il.com>,
        linux-integrity@...r.kernel.org, keyrings@...r.kernel.org,
        linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v8 10/10] integrity: support EC-RDSA signatures for
 asymmetric_verify

On Wed, Mar 27, 2019 at 02:10:20PM -0400, Mimi Zohar wrote:
> On Tue, 2019-03-26 at 15:58 +0300, Vitaly Chikunov wrote:
> > Allow to use EC-RDSA signatures for IMA by determining signature type by
> > the hash algorithm name. This works good for EC-RDSA since Streebog and
> > EC-RDSA should always be used together.
> > 
> > Cc: Mimi Zohar <zohar@...ux.ibm.com>
> > Cc: Dmitry Kasatkin <dmitry.kasatkin@...il.com>
> > Cc: linux-integrity@...r.kernel.org
> > Signed-off-by: Vitaly Chikunov <vt@...linux.org>
> > ---
> >  security/integrity/digsig_asymmetric.c | 11 +++++++++--
> >  1 file changed, 9 insertions(+), 2 deletions(-)
> > 
> > diff --git a/security/integrity/digsig_asymmetric.c b/security/integrity/digsig_asymmetric.c
> > index d775e03fbbcc..99080871eb9f 100644
> > --- a/security/integrity/digsig_asymmetric.c
> > +++ b/security/integrity/digsig_asymmetric.c
> > @@ -104,9 +104,16 @@ int asymmetric_verify(struct key *keyring, const char *sig,
> >  
> >  	memset(&pks, 0, sizeof(pks));
> >  
> > -	pks.pkey_algo = "rsa";
> >  	pks.hash_algo = hash_algo_name[hdr->hash_algo];
> > -	pks.encoding = "pkcs1";
> > +	if (hdr->hash_algo == HASH_ALGO_STREEBOG_256 ||
> > +	    hdr->hash_algo == HASH_ALGO_STREEBOG_512) {
> > +		/* EC-RDSA and Streebog should go together. */
> > +		pks.pkey_algo = "ecrdsa";
> > +		pks.encoding = "raw";
> 
> IMA signatures are stored as xattrs, making them persistent.  Support
> for streebog was upstreamed in linux-5.0.  This change would break
> existing systems using streebog.  As long as this is not yet a concern

In what sense it would break systems?

Unless kernel crashes or signature is recognized as valid, I think, it should
not be called a break.

> Reviewed-by:  Mimi Zohar <zohar@...ux.ibm.com>

Thanks!

> 
> > +	} else {
> > +		pks.pkey_algo = "rsa";
> > +		pks.encoding = "pkcs1";
> > +	}
> >  	pks.digest = (u8 *)data;
> >  	pks.digest_size = datalen;
> >  	pks.s = hdr->sig;

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ