[DNG] heads 0.3 released!

2017-06-22 Thread para...@dyne.org
heads 0.3 released == Yet another featureful release! Due this month, I've managed to come with the promised release, and from now on, I'll be following the quarterly release scheme. This time we have some interface changes and a couple of nice features which are explained below.

Re: [DNG] grsecurity ripoff by Google, with Linus' approval WAS: I have a question about libsystemd0 in devuan ascii,

2017-06-27 Thread para...@dyne.org
On Tue, 27 Jun 2017, Bruce Perens wrote: >I've been getting credible reports that [1]grsecurity.net is >infringing the kernel by preventing customers from redistributing the >GPL code for their patch. Can you provide proof? In no way are they violating the GPL. It might be a question

Re: [DNG] grsecurity ripoff by Google, with Linus' approval WAS: I have a question about libsystemd0 in devuan ascii,

2017-06-27 Thread para...@dyne.org
business move. On Tue, 27 Jun 2017, Bruce Perens wrote: >The allegation is that customers receive a patch to GPL software and >that the company makes it clear to the customers that this patch must >not be redistributed. > >On Tue, Jun 27, 2017 at 1:30 PM, [1]p

Re: [DNG] grsecurity ripoff by Google, with Linus' approval WAS: I have a question about libsystemd0 in devuan ascii,

2017-06-27 Thread para...@dyne.org
On Tue, 27 Jun 2017, Bruce Perens wrote: >> You are allowed to redistribute the patch legally, but you shall >> simply lose access to future patches. One could call it blackmail, >> another would call it a business move. >Do you work for [1]grsecurity.net or do you have first know

Re: [DNG] grsecurity ripoff by Google, with Linus' approval WAS: I have a question about libsystemd0 in devuan ascii,

2017-06-27 Thread para...@dyne.org
case. Nobody has been blocked yet, and nobody has publicly (re)distributed the non-public patches. >On Tue, Jun 27, 2017 at 2:02 PM, [1]para...@dyne.org ><[2]para...@dyne.org> wrote: > > On Tue, 27 Jun 2017, Bruce Perens wrote: > >> You are allowed

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

2017-06-28 Thread para...@dyne.org
On Wed, 28 Jun 2017, Svante Signell wrote: > On Wed, 2017-06-28 at 13:28 +0200, Edward Bartolo wrote: > > Hi, > > > > Too late for me. Apt logged the following information: > > > > Start-Date: 2017-06-25  18:47:08 > > Commandline: apt-get upgrade > > Upgrade: libpam0g:amd64 (1.1.8-3.5, 1.1.8-3.6