Comment 1 for bug 1794868

Email from Dean Troyer:
> What alternatives do we have for this functionality?

Alternatives in increasing levels of commitment to lshell:
* replace it
* fork the project and fix the CVEs and continue
* adopt the project and take over maintenance as a stand0-alone project should the existing maintainer be interested in doing so[0]

I am specifically not listing 'do nothing' as active CVEs must be addressed...

dt

[0] OpenStack has done this on occasion when a dependency goes dormant and the maintainer has no interest in continuing and the cost of converting outweighs the perceived cost of maintenance and ownership.