Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

replace github.com/satori/go.uuid with github.com/gofrs/uuid #470

Closed
ripienaar opened this issue Oct 27, 2018 · 0 comments
Closed

replace github.com/satori/go.uuid with github.com/gofrs/uuid #470

ripienaar opened this issue Oct 27, 2018 · 0 comments

Comments

@ripienaar
Copy link
Member

The satori version has weak random integration and can come up with some weak series of uuid's as per satori/go.uuid#73

Probably not a big deal for this project but nonetheless moving is best as per satori/go.uuid#84

ripienaar added a commit to ripienaar/go-choria that referenced this issue Oct 27, 2018
The satory/go.uuid is abandoned and uses rand in an unsafe way
while the gofrs one is maintained but has an unfortunate API change
to protect against unsafe UUID generation

Rock and a hard place but ultimately making this breaking API change
is the right things to do
ripienaar added a commit to ripienaar/go-choria that referenced this issue Oct 27, 2018
The satory/go.uuid is abandoned and uses rand in an unsafe way
while the gofrs one is maintained but has an unfortunate API change
to protect against unsafe UUID generation

Rock and a hard place but ultimately making this breaking API change
is the right things to do
ripienaar added a commit to ripienaar/go-choria that referenced this issue Oct 27, 2018
The satory/go.uuid is abandoned and uses rand in an unsafe way
while the gofrs one is maintained but has an unfortunate API change
to protect against unsafe UUID generation

Rock and a hard place but ultimately making this breaking API change
is the right things to do
ripienaar added a commit to ripienaar/go-choria that referenced this issue Oct 27, 2018
The satory/go.uuid is abandoned and uses rand in an unsafe way
while the gofrs one is maintained but has an unfortunate API change
to protect against unsafe UUID generation

Rock and a hard place but ultimately making this breaking API change
is the right things to do
ripienaar added a commit that referenced this issue Oct 27, 2018
(#470) replace satori/go.uuid with gofrs/uuid
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant