netdev - Re: DCCP Deprecation

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: Tue, 29 Aug 2023 17:38:19 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: "Maglione, Gregorio" <Gregorio.Maglione@...y.ac.uk>
Cc: Stephen Hemminger <stephen@...workplumber.org>, Paolo Abeni
 <pabeni@...hat.com>, Kuniyuki Iwashima <kuniyu@...zon.com>, "David S.
 Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Florian
 Westphal <fw@...len.de>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
 "Rakocevic, Veselin" <Veselin.Rakocevic.1@...y.ac.uk>,
 "Markus.Amend@...ekom.de" <Markus.Amend@...ekom.de>,
 "nathalie.romo-moreno@...ekom.de" <nathalie.romo-moreno@...ekom.de>
Subject: Re: DCCP Deprecation

On Tue, 29 Aug 2023 15:17:08 +0000 Maglione, Gregorio wrote:
> For the purpose of upstreaming, the repository was forked
> [https://github.com/GREGORIO-M/mp-dccp] to remove non-GPL components
> and to update the license to show GPL-2.0. Is this enough to solve
> the license issue? If so, is it still agreeable for us to upstream
> and maintain MP-DCCP, so that, once DCCP deprecates, MP-DCCP becomes
> the sole DCCP enabler in the kernel? What steps would the upstreaming
> involve? Do you require any information about the MP?

Who is going to use it? Your earlier responses gave me the impression
that you just need a number of implementations for the standardization
process - apologies if I'm mistaken - but we suffered thru maintaining
the unused DCCP code for years, we need real users who will care.

Please use a sane email client you're responses are very hard to parse.