The last time I looked at this, go had moved on to use newer features of the
Security.Framework that couldn't be duplicated for older systems, so it was
stuck at an older pegged version.
I see here and there that some folks have managed to get newer versions of the
Security.Frameworks from
I may try to make some magic and bring fresh go
--
wbr, Kirill
> On 27. Jul 2023, at 18:39, Christopher Nielsen
> wrote:
>
> At present, our Go port is pinned at an older version - 1.17.3 - for macOS
> 10.12 and earlier. With the result being that many Go-based ports simply fail
> to