On Tue, 2018-06-05 at 08:08 -0700, Adam Williamson wrote:
> On Tue, 2018-06-05 at 11:16 +0200, Nikos Mavrogiannopoulos wrote:
> > On Mon, 2018-06-04 at 11:46 -0700, Adam Williamson wrote:
> > > On Fri, 2018-06-01 at 13:40 +0200, Jan Kurik wrote:
> > > > = Proposed System Wide Change: Strong crypto settings: phase 2
> > > > =
> > > > https://fedoraproject.org/wiki/Changes/StrongCryptoSettings2
> > >
> > >
> > > How about clients for networking with other OSes - e.g. Samba
> > > clients,
> > > and the tools for enrolling systems as Active Directory domain
> > > members?
> > > Do those respect the system policy? If so, have we considered the
> > > impact of these changes on those configurations?
> >
> > Do these clients use TLS?
>
> I don't know, but it seems worth considering, and my basic point here
> is this is something the Change owner should be responsible for
> figuring out: making at least a reasonable effort to evaluate which
> important (particularly release-critical) software and workflows will
> be affected by the change and proposing plans for testing them. "we
> should check curl behaves as expected" just doesn't really cut it as
> a
> test plan.
Do we have a list of the release-critical software and functionality?
Of course verifying that all the packages in Fedora still work (in what
sense?) is a quite bit unrealistic requirement.
--
Tomáš Mráz
No matter how far down the wrong road you've gone, turn back.
Turkish proverb
[You'll know whether the road is wrong if you carefully listen to your
conscience.]
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/JODSHUPXNLSEXFFJQBH5EDYGDEAP4CIQ/
