Am 07.03.2022 um 17:39 schrieb Justin Keller via lpi-examdev:
On Mon, Mar 7, 2022 at 11:18 AM Fabian Thorns via lpi-examdev
Then there is a list of medium size considerations:
What do you think about additional file systems in 203?
I am kind of missing any encryption. Whether it be fscript (ext4),
ecryptfs, gocryptfs or cryfs.
I know we have it in 331.3, but I feel encryption is almost everywhere
these days.
Shall we add certbot and Let's Encrypt to 208.2? Alternatively, we could
consider having one Apache HTTPD and another NGINX objective and finally a
HTTPS / TLS objective focussing on certificate procurement and enabling it in
both servers. What's your ideal vision of Apache HTTPD/NGINX coexisting
(assume, Squid disappears from the exam)?
My impression is that both have become "dumb" frontends for the actual
application webservers (g/unicorn, puma, caddy, etc.). I think we need
to cover more than just the two.
Shall we rename 210.1 to "Automated Network Configuration" and include full
coverage of IPv6 SLAAC and DHCPv6? What do you think about Kea?
I am not aware of any major distribution using it or frankly anyone
outside facebook. And important features like flexible identifiers are
locked behind paid "premium" hooks.
So my view is we should just extend our current coverage of isc-dhcp to
dhcpv6.
Both SUSE and Red Had have replaced OpenLDAP with 389 DS. Shall we do the same
in 210.4 ?
Debian/Ubuntu packages exist, but OpenLDAP still seems to be the primary
choice. I wouldn't drop it just yet.
Markus
_______________________________________________
lpi-examdev mailing list
[email protected]
https://list.lpi.org/mailman/listinfo/lpi-examdev
