Workstation WG meeting recap 2019-Sep-30
by Michael Catanzaro
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-2/2019-09-30/workstation...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting-2/2019-09-30/workstation...
Log:
https://meetbot.fedoraproject.org/fedora-meeting-2/2019-09-30/workstation...
=================================
#fedora-meeting-2: Workstation WG
=================================
Meeting started by mcatanzaro at 13:00:27 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2019-09-30/workstation...
.
Meeting summary
---------------
* Roll call (mcatanzaro, 13:00:34)
* Attendance (mcatanzaro, 13:09:20)
* ACTION: aday to create a ticket to continue this discussion
(mcatanzaro, 13:30:24)
* Automatically install the OpenH264 codecs (mcatanzaro, 13:31:43)
* LINK: https://paste.gnome.org/potu4skdo (mcatanzaro, 13:33:42)
* ACTION: cschalle to comment in ticket and look into question about
license terms (mcatanzaro, 13:34:16)
* Workstation repos are not available for Branched and Rawhide
(mcatanzaro, 13:34:30)
* LINK: https://pagure.io/fedora-workstation/issue/102 (petersen,
13:36:16)
* ACTION: cschalle to ping repo maintainers (mcatanzaro, 13:41:22)
* Workstation x86_64 live image is over size target (mcatanzaro,
13:42:17)
* Ship fedora-workstation-repositories on install media (mcatanzaro,
13:51:22)
* LINK: https://pagure.io/fedora-workstation/issue/106 < mailing list
discussion (etc) (aday, 13:51:38)
* LINK: https://pagure.io/fedora-workstation/issue/105 (petersen,
13:54:38)
* Open floor (mcatanzaro, 13:59:55)
* LINK: https://pagure.io/fedora-workstation/issue/76#comment-598430
(cmurf, 13:59:59)
Meeting ended at 14:03:40 UTC.
Action Items
------------
* aday to create a ticket to continue this discussion
* cschalle to comment in ticket and look into question about license
terms
* cschalle to ping repo maintainers
Action Items, by person
-----------------------
* aday
* aday to create a ticket to continue this discussion
* cschalle
* cschalle to comment in ticket and look into question about license
terms
* cschalle to ping repo maintainers
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mcatanzaro (79)
* petersen (54)
* aday (22)
* cmurf (21)
* zodbot (17)
* otaylor (13)
* langdon (8)
* cschalle (6)
* sgallagh (4)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
4 years, 2 months
Questions about encrypting user homes by default
by Chris Murphy
My working assumption is that g-i-s and Users panel need to grow the
ability to present appropriate interface for per user encryption;
maybe that could be as simple as an "encrypt" checkbox at user
creation time, ticked by default.
1. How to handle Anaconda vs GNOME encryption features?
a. It's not apparent that the two offerings differ, how they differ,
that they can be combined, that combining them has consequences.
b. In the Installation Destination spoke, "Encrypt my data" is visible
and unchecked by default. It could be construed as user home only
encryption. It is, however, full disk encryption (minus /boot).
c. If user chooses this option in the installer, now what? Do not
enable or even present the GNOME encryption features? Or double
encrypt?
d. Alternatively, does it get renamed to better indicate it's full
disk encryption? Or remove it entirely?
2. Consequences of an fscrypt/ext4 only solution
a. Users choosing anything other than ext4 not only don't get user
home encrypted by default, they can't opt into what we're initially
proposing.
b. In some sense it diminishes the message that privacy of user data
is important, because it comes with a "only if you pick ext4" catch.
c. How would the user be informed of a & b (goes back to #1).
3. Upsides of fscrypt/ext4 only solution
a. Faster delivery than systemd-homed? (Is this certain?)
4. What about /home only encryption?
a. Wrap a single LUKS passphrase stored for each user login? Any valid
user reveals that passphrase, and is automatically used to unlock
/home; g-i-s could one-time acquire the LUKS passphrase used during
installation from the (first/admin) user
b. Use each user's login passphrase as a LUKS passphrase, stored in a
LUKS keyslot? (Might aid chance of recovery in case all login files
are lost.)
c. Requires Anaconda changes. Retask "encrypt my data" to mean /home
encryption? How to indicate full disk encryption? Present both
options?
5. What about always using a /dev/urandom derived key at boot time for swap?
--
Chris Murphy
4 years, 2 months
Workstation WG meeting recap 2019-Sep-16
by Langdon White
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-2/2019-09-16/workstation...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting-2/2019-09-16/workstation...
Log:
https://meetbot.fedoraproject.org/fedora-meeting-2/2019-09-16/workstation...
==============================
#fedora-meeting-2: workstation
==============================
Meeting started by langdon at 13:03:34 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-2/2019-09-16/workstation...
.
Meeting summary
---------------
* rollcall (langdon, 13:03:53)
* agenda (langdon, 13:07:55)
* LINK:
https://pagure.io/fedora-workstation/issues?status=Open&tags=meeting&clos...
(cmurf, 13:08:45)
* using
https://pagure.io/fedora-workstation/issues?status=Open&tags=meeting&clos...
for today's agenda.. starting from oldest first then open floor
(langdon, 13:09:41)
* "Replace Rhythmbox with GNOME Music in default install"
https://pagure.io/fedora-workstation/issue/33 (langdon, 13:10:13)
* defering #33 until next meeting when aday will (hopefully) be here
(langdon, 13:13:33)
* "Automatically install the OpenH264 codecs"
https://pagure.io/fedora-workstation/issue/84 (langdon, 13:13:59)
* proposal to perform 2 changes to enable the codec (langdon,
13:32:03)
* change 1: Workstation WG requests releng to change
fedora-cisco-openh264 from enabled=0 to enabled=1 (langdon,
13:32:13)
* change 2: Install fedora-workstation-repositories by default in
Workstation (langdon, 13:32:26)
* AGREED: Workstation WG requests releng to change
fedora-cisco-openh264 from enabled=0 to enabled=1 [+7] (langdon,
13:49:17)
* "Ship fedora-workstation-repositories on install media"
https://pagure.io/fedora-workstation/issue/105 (langdon, 13:49:48)
* Workstation live image is over size target (mcatanzaro, 14:01:35)
* Workstation x86_64 live image is over size target :
https://pagure.io/fedora-workstation/issue/104 (langdon, 14:01:35)
* Workstation x86_64 live image is over size target :
https://pagure.io/fedora-workstation/issue/104 (langdon, 14:01:48)
* mcatanzaro proposed new schedule at
https://apps.fedoraproject.org/calendar/workstation/ (mcatanzaro,
14:09:31)
Meeting ended at 14:11:09 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* langdon (99)
* kalev (73)
* cmurf (66)
* mcatanzaro (66)
* Son_Goku (58)
* petersen (42)
* mclasen (17)
* zodbot (13)
* aday (11)
* sgallagh (4)
* otaylor (4)
* otaylor_ (3)
* cschalle_ (1)
* cschaller (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
4 years, 2 months
Re: Proposing a Test Day for F31 Cycle
by Sumantro Mukherjee
On Tue, Sep 10, 2019 at 6:51 PM Kalev Lember <klember(a)redhat.com> wrote:
> How about right after the Beta release so that we have a few days between
> to give time for the 3.34.0 megaupdate update to go to stable and get a new
> branched compose? (Beta is shipping with 3.33.92, and we have 3.34.0 almost
> ready to go to bodhi). Maybe wait with the test day scheduling a bit until
> we know if the Beta is releasing on schedule or if it is going to be
> slipped?
>
> Kalev
>
The Beta is about to be out, can we fix on a day? :)
The week of 23rd works, if you all are okay with it.
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>
4 years, 2 months
[Test Day] Fedora 31 Gnome 3.34 2019-09-18
by Sumantro Mukherjee
Hola!
Wednesday, 2019-09-18 will be Fedora 31 Gnome 3.34 Test Day!
As part of this planned Change for Fedora 31, So this is an important Test
Day!
Beta is on its way, we try to make sure that all the gnome features
are performing as they should and then file bugs well ahead of time.
We need to ensure it's working well enough and catch any remaining issues.
It's also pretty easy to join in: all you'll need is Test Day image (which
you can grab from the wiki page[0]).
As always, the event will be in #fedora-test-day on Freenode IRC.
[0] https://fedoraproject.org/wiki/Test_Day:2019-09-18_Gnome_3.34_Test_Day
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>
4 years, 2 months