On Thu, Dec 28, 2017 at 05:42:19PM -0500, Michael Orlitzky wrote:
> We now have IUSE="+cracklib" in sys-apps/shadow, sys-auth/pambase, and
> sys-libs/pam (thanks robbat2).
>
> Does that address everyone's concerns?
>
> Enough so that I can revert the revert without anyone reverting the
> revert r
We now have IUSE="+cracklib" in sys-apps/shadow, sys-auth/pambase, and
sys-libs/pam (thanks robbat2).
Does that address everyone's concerns?
Enough so that I can revert the revert without anyone reverting the
revert revert?
On Wed, Dec 27, 2017 at 4:16 PM, Nils Freydank wrote:
> Am Mittwoch, 27. Dezember 2017, 22:33:03 CET schrieb R0b0t1:
>> On Wed, Dec 27, 2017 at 10:32 AM, William Hubbs wrote:
>> > As he said, he contactedd the maintainers in ample time, so I would say
>> > that since they didn't respond he went a
Am Mittwoch, 27. Dezember 2017, 22:33:03 CET schrieb R0b0t1:
> On Wed, Dec 27, 2017 at 10:32 AM, William Hubbs wrote:
> > As he said, he contactedd the maintainers in ample time, so I would say
> > that since they didn't respond he went ahead in good faith. I'll get the
> > link later, but as I re
On Wed, Dec 27, 2017 at 10:32 AM, William Hubbs wrote:
> As he said, he contactedd the maintainers in ample time, so I would say
> that since they didn't respond he went ahead in good faith. I'll get the
> link later, but as I recall, the dev manual recommends a 2-4 week wait
> for maintainers not
On Wed, Dec 27, 2017 at 05:42:04PM +0200, Mart Raudsepp wrote:
> On K, 2017-12-27 at 09:57 -0500, Michael Orlitzky wrote:
> > > 2) What you plan to do to have USE=cracklib enabled by default. Two
> > > people suggested you should keep this (one way or another) but
> > instead
> > > everyone is now
On 12/27/2017 10:42 AM, Mart Raudsepp wrote:
> If you want to make such a base profile change, then I believe you
> should contact the maintainers and see which one wants it default
> disabled, and which default enabled; do the default enabled changes
> and only afterwards you can touch a base defa
On K, 2017-12-27 at 09:57 -0500, Michael Orlitzky wrote:
> > 2) What you plan to do to have USE=cracklib enabled by default. Two
> > people suggested you should keep this (one way or another) but
> instead
> > everyone is now without it enabled by default.
>
> I plan to do nothing, because I think
On 12/27/2017 05:49 AM, Jeroen Roovers wrote:
> OK, let me explain again.
>
> In #gentoo we give a lot of attention and support to people who want to
> set up full disk encryption, tor, VPNs, and other security mechanisms,
> and this tells me that they actually want security. By saying that "some
On Fri, 22 Dec 2017 12:30:35 -0500
Michael Orlitzky wrote:
> On 12/21/2017 02:27 PM, Jeroen Roovers wrote:
> > On Thu, 21 Dec 2017 10:10:30 -0500
> > Michael Orlitzky wrote:
> >
> >> The "cracklib" USE flag ... this commit removes it from
> >> base/make.defaults.
> >>
> >> Closes: https://bug
On 12/21/2017 02:27 PM, Jeroen Roovers wrote:
> On Thu, 21 Dec 2017 10:10:30 -0500
> Michael Orlitzky wrote:
>
>> The "cracklib" USE flag ... this commit removes it from base/make.defaults.
>>
>> Closes: https://bugs.gentoo.org/635698
>
> As there:
>> ...
>
> Let me (easily) counter that by sta
On Thu, 21 Dec 2017 10:10:30 -0500
Michael Orlitzky wrote:
> The "cracklib" USE flag has long (since 2007ish) been enabled by
> default for all profiles. But, the features that it provides are not
> critical for any of the packages that use it: typically, the library
> is used to evaluate a candi
The "cracklib" USE flag has long (since 2007ish) been enabled by
default for all profiles. But, the features that it provides are not
critical for any of the packages that use it: typically, the library
is used to evaluate a candidate password and to prevent the user from
choosing a weak one.
Sinc
13 matches
Mail list logo
