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] [day] [month] [year] [list]
Date:   Fri, 19 Mar 2021 10:00:27 +0900
From:   "Namjae Jeon" <namjae.jeon@...sung.com>
To:     "'Randy Dunlap'" <rdunlap@...radead.org>
Cc:     "'Linux Kernel Mailing List'" <linux-kernel@...r.kernel.org>,
        <linux-cifs@...r.kernel.org>,
        <linux-cifsd-devel@...ts.sourceforge.net>,
        "'Hyunchul Lee'" <hyc.lee@...il.com>,
        "'Steve French'" <sfrench@...ba.org>,
        "'Sergey Senozhatsky'" <sergey.senozhatsky@...il.com>,
        "'Stephen Rothwell'" <sfr@...b.auug.org.au>,
        "'Linux Next Mailing List'" <linux-next@...r.kernel.org>
Subject: RE: linux-next: Tree for Mar 18 (cifsd: Kconfig)

> On 3/18/21 3:08 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > News: there will be no linux-next release on Friday this week.
> >
> > Warning: Some of the branches in linux-next are still based on
> > v5.12-rc1, so please be careful if you are trying to bisect a bug.
> >
> > News: if your -next included tree is based on Linus' tree tag
> > v5.12-rc1{,-dontuse} (or somewhere between v5.11 and that tag), please
> > consider rebasing it onto v5.12-rc2. Also, please check any branches
> > merged into your branch.
> >
> > Changes since 20210317:
> >
Hi Randy,
> > The cifsd tree lost its build failure.
> 
> kconfig warning in cifsd:
> 
> WARNING: unmet direct dependencies detected for CRYPTO_ARC4
>   Depends on [n]: CRYPTO [=y] && CRYPTO_USER_API_ENABLE_OBSOLETE [=n]
>   Selected by [y]:
>   - SMB_SERVER [=y] && NETWORK_FILESYSTEMS [=y] && INET [=y]
> 
> 
> 
> Either
> 	select CRYPTO_ARC4 if CRYPTO_USER_API_ENABLE_OBSOLETE or add
> 	select CRYPTO_USER_API
> 	select CRYPTO_USER_API_ENABLE_OBSOLETE
> 
> The first choice is certainly more palatable if it is OK.
> 
> 
> thanks.
> --
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@...radead.org>
I will make the patch included your reported-by tag.
Thanks for your report and patch!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ