netdev - Re: [PATCH] SUNRPC: Add a check for gss_release

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: <6530850bc6f0341d1f2d5043ba1dd04e242cff66.camel@hammerspace.com>
Date:   Wed, 21 Apr 2021 13:11:03 +0000
From:   Trond Myklebust <trondmy@...merspace.com>
To:     "a.shelat@...theastern.edu" <a.shelat@...theastern.edu>,
        "leon@...nel.org" <leon@...nel.org>
CC:     "davem@...emloft.net" <davem@...emloft.net>,
        "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
        "chuck.lever@...cle.com" <chuck.lever@...cle.com>,
        "dwysocha@...hat.com" <dwysocha@...hat.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "kuba@...nel.org" <kuba@...nel.org>,
        "sudipm.mukherjee@...il.com" <sudipm.mukherjee@...il.com>,
        "bfields@...ldses.org" <bfields@...ldses.org>,
        "anna.schumaker@...app.com" <anna.schumaker@...app.com>,
        "pakki001@....edu" <pakki001@....edu>,
        "linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH] SUNRPC: Add a check for gss_release_msg

On Wed, 2021-04-21 at 15:19 +0300, Leon Romanovsky wrote:
> On Wed, Apr 21, 2021 at 11:58:08AM +0000, Shelat, Abhi wrote:
> > > > 
> > > > > > They introduce kernel bugs on purpose. Yesterday, I took a
> > > > > > look on 4
> > > > > > accepted patches from Aditya and 3 of them added various
> > > > > > severity security
> > > > > > "holes".
> > > > > 
> > > > > All contributions by this group of people need to be
> > > > > reverted, if they
> > > > > have not been done so already, as what they are doing is
> > > > > intentional
> > > > > malicious behavior and is not acceptable and totally
> > > > > unethical.  I'll
> > > > > look at it after lunch unless someone else wants to do it…
> > > > 
> > 
> > <snip>
> > 
> > Academic research should NOT waste the time of a community.
> > 
> > If you believe this behavior deserves an escalation, you can
> > contact the Institutional Review Board (irb@....edu) at UMN to
> > investigate whether this behavior was harmful; in particular,
> > whether the research activity had an appropriate IRB review, and
> > what safeguards prevent repeats in other communities.
> 
> The huge advantage of being "community" is that we don't need to do
> all
> the above and waste our time to fill some bureaucratic forms with
> unclear
> timelines and results.
> 
> Our solution to ignore all @umn.edu contributions is much more
> reliable
> to us who are suffering from these researchers.
> 

<shrug>That's an easy thing to sidestep by just shifting to using a
private email address.</shrug>

There really is no alternative for maintainers other than to always be
sceptical of patches submitted by people who are not known and trusted
members of the community, and to scrutinise those patches with more
care.

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@...merspace.com