Write a proposed policy on moving algorithms to the legacy provider

[hlandau]

Discussed on 2024-01-30
Blocked on #437

[hlandau]

My personal view is that the legacy provider probably isn't worth it as a concept.

While I understand the feeling where, we really don't like DES and want to be able to "get rid of it" (for example), my feeling is the issues it creates aren't really worth the marginal gains of reducing the scope and size of the default provider.

In practice people install both providers. no-legacy can still mask algorithms we have deemed legacy.

[hlandau]

OK, so I understand there is a desire to be able to enable and disable legacy algorithms via config because people want to configure apps they didn't make.

[hlandau]

Need input on the reasons and rationale behind the legacy provider in the first place. (Chesterton's fence.)