Hi, as this was hot topic on the lists and it's FESCo blocker, so in case you missed it (as it's very new), it's now possible to create product specific password policies in Anaconda!
For details, check out https://bugzilla.redhat.com/show_bug.cgi?id=1191842#c14
Thanks bcl!
Jaroslav
On Mar 23, 2015, at 5:54 AM, Jaroslav Reznik jreznik@redhat.com wrote:
Hi, as this was hot topic on the lists and it's FESCo blocker, so in case you missed it (as it's very new), it's now possible to create product specific password policies in Anaconda!
For details, check out https://bugzilla.redhat.com/show_bug.cgi?id=1191842#c14
Thanks bcl!
Right, so we as the Server WG need to decide what exactly we want as a policy (and whether to support the click-twice-to-ignore button for "bad" passwords, then someone needs to implement it.
Let's put this on the agenda for tomorrow's meeting. I'll also state up front that I already have a fully loaded plate this week, so I'm going to need a volunteer to implement the decision. It doesn't look difficult from what I can see in the BZ. I'll be available to review the work if desired.
Jaroslav _______________________________________________ server mailing list server@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/server
On Mon, 2015-03-23 at 06:33 -0400, Stephen Gallagher wrote:
On Mar 23, 2015, at 5:54 AM, Jaroslav Reznik jreznik@redhat.com wrote:
Hi, as this was hot topic on the lists and it's FESCo blocker, so in case you missed it (as it's very new), it's now possible to create product specific password policies in Anaconda!
For details, check out https://bugzilla.redhat.com/show_bug.cgi?id=1191842#c14
Thanks bcl!
Right, so we as the Server WG need to decide what exactly we want as a policy (and whether to support the click-twice-to-ignore button for "bad" passwords, then someone needs to implement it.
Let's put this on the agenda for tomorrow's meeting. I'll also state up front that I already have a fully loaded plate this week, so I'm going to need a volunteer to implement the decision. It doesn't look difficult from what I can see in the BZ. I'll be available to review the work if desired.
Sorry folks, didn't mean to do reply-to-all on that.
On Mon, Mar 23, 2015 at 05:54:34AM -0400, Jaroslav Reznik wrote:
Hi, as this was hot topic on the lists and it's FESCo blocker, so in case you missed it (as it's very new), it's now possible to create product specific password policies in Anaconda!
For details, check out https://bugzilla.redhat.com/show_bug.cgi?id=1191842#c14
Thanks bcl!
Indeed. This looks like something we need to include in our -productimg package. (Is that still being used for F22?)
On Mon, 2015-03-23 at 15:17 -0400, Paul W. Frields wrote:
On Mon, Mar 23, 2015 at 05:54:34AM -0400, Jaroslav Reznik wrote:
Hi, as this was hot topic on the lists and it's FESCo blocker, so in case you missed it (as it's very new), it's now possible to create product specific password policies in Anaconda!
For details, check out https://bugzilla.redhat.com/show_bug.cgi?id=1191842#c14
Thanks bcl!
Indeed. This looks like something we need to include in our -productimg package. (Is that still being used for F22?)
Yes, the fedora-productimg-* packages are still in use, though they are slightly different now. They include the per-product theming used for Anaconda as well as things like default filesystem, default package environment group set, etc.
This *is* probably where the pwpolicy stuff belongs.
On Mon, Mar 23, 2015 at 03:38:14PM -0400, Stephen Gallagher wrote:
On Mon, 2015-03-23 at 15:17 -0400, Paul W. Frields wrote:
On Mon, Mar 23, 2015 at 05:54:34AM -0400, Jaroslav Reznik wrote:
Hi, as this was hot topic on the lists and it's FESCo blocker, so in case you missed it (as it's very new), it's now possible to create product specific password policies in Anaconda!
For details, check out https://bugzilla.redhat.com/show_bug.cgi?id=1191842#c14
Thanks bcl!
Indeed. This looks like something we need to include in our -productimg package. (Is that still being used for F22?)
Yes, the fedora-productimg-* packages are still in use, though they are slightly different now. They include the per-product theming used for Anaconda as well as things like default filesystem, default package environment group set, etc.
This *is* probably where the pwpolicy stuff belongs.
OK, so it looks like action items are:
(1) Provide a new /etc/security/pwquality.conf in the productimg
(2) Update our workstation KS file with %anaconda section as per instructions here: https://github.com/rhinstaller/anaconda/commit/e7e86a23d56bde2b2493d17c99b07...
Did I miss anything?
On Tue, Mar 24, 2015 at 09:36:21AM -0400, Paul W. Frields wrote:
On Mon, Mar 23, 2015 at 03:38:14PM -0400, Stephen Gallagher wrote:
On Mon, 2015-03-23 at 15:17 -0400, Paul W. Frields wrote:
On Mon, Mar 23, 2015 at 05:54:34AM -0400, Jaroslav Reznik wrote:
Hi, as this was hot topic on the lists and it's FESCo blocker, so in case you missed it (as it's very new), it's now possible to create product specific password policies in Anaconda!
For details, check out https://bugzilla.redhat.com/show_bug.cgi?id=1191842#c14
Thanks bcl!
Indeed. This looks like something we need to include in our -productimg package. (Is that still being used for F22?)
Yes, the fedora-productimg-* packages are still in use, though they are slightly different now. They include the per-product theming used for Anaconda as well as things like default filesystem, default package environment group set, etc.
This *is* probably where the pwpolicy stuff belongs.
OK, so it looks like action items are:
(1) Provide a new /etc/security/pwquality.conf in the productimg
(2) Update our workstation KS file with %anaconda section as per instructions here: https://github.com/rhinstaller/anaconda/commit/e7e86a23d56bde2b2493d17c99b07...
Did I miss anything?
Do we just need something like this to be in line with defaults?
desktop@lists.fedoraproject.org
-
Jaroslav Reznik -
Paul W. Frields -
Stephen Gallagher