Closed abiligiri closed 4 weeks ago
Personally, I like the approach of using a well-tested library for SRP, and the upstream library seems to provide this. So I would be in favour of this implementation vs #639
If I can make a suggestion, forking adam-fowler/swift-srp and publishing as a separate package with the necessary changes would be my preference for the following reasons:
Note that both options use a library for SRP. This uses https://github.com/adam-fowler/swift-srp/blob/main/Sources/SRP/client.swift and #639 fixes the srp code that was already in repo most likely from https://github.com/Bouke/SRP. I see that Adam Fowler implementation is still active. Maybe that is another reason to use it.
@MattKiazyk I was able to download and install Xcode 16.1.0. Not sure what you mean by download doesn't work.
May I also request merging this for the release https://github.com/XcodesOrg/XcodesApp/pull/632
I cleaned this up a bit. Using patched swift-srp from https://github.com/abiligiri/swift-srp and removed local copy. I have also opened MR for upstream https://github.com/adam-fowler/swift-srp/pull/13
@abiligiri hope you don't mind I clean up some extra prints that were in there as well as moved the swift-srp
dependency to an xcodes fork. I copied your changes from your branch into main on our fork.
Fixes https://github.com/XcodesOrg/XcodesApp/issues/630