Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
Sorry for necro-ing this repository. I stumbled upon it when someone came into the go discord asking how to install this project since it isn't using go modules.
Since this project has at least one new user and a non-zero amount of stars I figured it might be prudent to update this project so that it uses modules (introduced in go 1.11). This way at the very least users can practice prudent security by building this project with updated versions of go that may include any patches to the cryptography dependencies included in the go std library. Idk that there have been any patches significant for the project but its certainly possible after 9 years.
I updated the readme to include installation instructions, and updated the new minimum required version of go.
Which is now go.1.20 since "crypto/ecdsa" has since been updated to use "crypto/ecdh" and ecdh did not exist until go 1.20. I verified that go 1.20 is able to build this project.
I removed the vendor directory as it is not needed with modules, but it can be added back if desired with
go mod vendor
.