| 5 | | Moreover, based upon the, IMHO, rather strong cautionary language of why the upstream OpenSSH project, did not merge the https://github.com/openssh-gsskex patches, as well as the fact that they themselves do not appear to have updated their codebase in several months, as well as my general tendency to reduce dependencies and attack surfaces and thus my own personal choice in using the OpenSSH port is to -kerberos5 -gsskex -authx variants for example, I am probably not really of the general mindset even think that refactoring the previous patch for the current version of OpenSSH is a wise idea without a lot more convincing, and given that my interest in updating the port was predominantly to keep it in alignment with the openssh.com current release, and I am merely a volunteer without commit access, I would encourage you to seek out other guidance since I doubt I will be able to be of much additional assistance given my present circumstances. |
| | 5 | Moreover, based upon the, IMHO, rather strong cautionary language of why the upstream OpenSSH project, did not merge the https://github.com/openssh-gsskex patches, as well as the fact that they themselves do not appear to have updated their codebase in several months, as well as my general tendency to reduce dependencies and attack surfaces and thus my own personal choice in using the OpenSSH port is to -kerberos5 -gsskex -xauth variants for example, I am probably not really of the general mindset even think that refactoring the previous patch for the current version of OpenSSH is a wise idea without a lot more convincing, and given that my interest in updating the port was predominantly to keep it in alignment with the openssh.com current release, and I am merely a volunteer without commit access, I would encourage you to seek out other guidance since I doubt I will be able to be of much additional assistance given my present circumstances. |
