<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">This is a Terrible Idea.<div class=""><br class=""></div><div class="">The first rule of computer security is to update your stuff.</div><div class=""><br class=""></div><div class="">Adding the complexity of allowing arbitrary software versions means that now we have to make sure that we update our stuff <b class="">and</b> make sure that we’re not still running old, insecure code even after we’ve updated. It’s asking for trouble.</div><div class=""><br class=""></div><div class="">I don’t want Apple to give me the option of running old ssh (or any other old code) when I update macOS, and I don’t want MacPorts to give me the same option.</div><div class=""><br class=""></div><div class="">And that’s on top of the unworkable maintenance issues discussed before.</div><div class=""><br class=""></div><div class="">A big Nope, both as a user and a port maintainer.</div><div class=""><br class=""></div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Oct 3, 2020, at 11:00 AM, Ryan Schmidt <<a href="mailto:ryandesign@macports.org" class="">ryandesign@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 24px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">It would be a major project if it were clear how it could possibly work and it were just a matter of doing it. But so far I have no idea how it could work.</span></div></blockquote></div><br class=""></div></body></html>