Re: Fedora 32 System-Wide Change proposal: Disallow Empty Password By Default

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wednesday, December 4, 2019 12:00:06 PM MST Chris Murphy wrote:
> Other alternatives:
> a. At least on ext4, you can today selectively encrypt directories and
> files, so you could have an non-encrypted ~/ by default, and choose
> what directories to encrypt. There's no GUI assistance for this yet
> that I'm aware of.
> b. If you can clearly compartmentalize our use cases, you can have two
> accounts, one is encrypted and other not.
> 
> I think the later two put a lot of burden on the user to figure out
> and manage. I'm not sure there's a way for GNOME or systemd-homed to
> directly support such use cases, but I also don't expect it would
> stand in the way of user implementation of such a scheme.

"Alternative" B is a complete cop-out. It's essentially ignoring the fault 
entirely, and blaming the using for wanting to do something the traditional 
way.

That is a workaround, not a solution.

-- 
John M. Harris, Jr.
Splentity

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux