linux-kernel - Re: FU: RE: Why is no one discussing this anymore?

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>] [day] [month] [year] [list]

Message-ID: <4fca34d1b2c8a7f67c780b5df31f6d58@memeware.net>
Date:   Fri, 28 Dec 2018 17:22:04 +0000
From:   vsnsdualce@...eware.net
To:     leo_tck@...ny.cz
Cc:     Christopher Turkel <turkel.christopher@...il.com>,
        misc@...nbsd.org, owner-misc@...nbsd.org,
        linux-kernel@...r.kernel.org, gentoo-user@...ts.gentoo.org
Subject: Re: FU: RE: Why is no one discussing this anymore?

I was addressing OpenBSD as-well, I chose the lists to CC to: linux 
lists and BSD, since the underlying concerns are the same.

It took slightly longer to find the appropriate openbsd list, infact, so 
you definitely weren't CC'd by accident.

On 2018-12-27 22:54, leo_tck@...ny.cz wrote:
> zeur here.
> 
> I now[0] see that a whole bunch of lists were Cc'd, and while I'm not
> sorry for not preserving the Ccs, I realize that you might not have 
> been
> addressing us, misc@...nBSD.org.
> 
> I still think my point holds, though. This should be a matter of great
> concern for OpenBSD, like it is to just about every other project
> relying on licensed code, "open" or not.
> 
>         --zeur.
> 
> [0] post-coffee-intake =)
> 
>> This whole discussion is best served elsewhere.