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

bcrypt: add easy bcrypt example #99

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Conversation

elgohr
Copy link

@elgohr elgohr commented Sep 3, 2019

No description provided.

@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it!) and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

ℹ️ Googlers: Go here for more info.

@elgohr
Copy link
Author

elgohr commented Sep 3, 2019

@googlebot I signed it!

@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: yes and removed cla: no labels Sep 3, 2019
@gopherbot
Copy link
Contributor

This PR (HEAD: 9b37a44) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/crypto/+/193079 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
Within the next week or so, a maintainer will review your change and provide
feedback. See https://golang.org/doc/contribute.html#review for more info and
tips to get your patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11, it means that this CL will be reviewed as part of the next development
cycle. See https://golang.org/s/release for more details.


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 1:

(2 comments)


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Lars Gohr:

Patch Set 1:

I'll correct the commit message.
The second comment doesn't match the documentation (https://godoc.org/golang.org/x/crypto/bcrypt#CompareHashAndPassword).
At my point of view I would like to go with the error.


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 1:

Patch Set 1:

I'll correct the commit message.
The second comment doesn't match the documentation (https://godoc.org/golang.org/x/crypto/bcrypt#CompareHashAndPassword).
At my point of view I would like to go with the error.

I misread! Thanks for pointing that out. :)


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Lars Gohr:

Patch Set 1:

Patch Set 1:

I'll correct the commit message.
The second comment doesn't match the documentation (https://godoc.org/golang.org/x/crypto/bcrypt#CompareHashAndPassword).
At my point of view I would like to go with the error.

Sorry, didn't read correctly. Will also have a look at the second.


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 1:

Patch Set 1:

Patch Set 1:

I'll correct the commit message.
The second comment doesn't match the documentation (https://godoc.org/golang.org/x/crypto/bcrypt#CompareHashAndPassword).
At my point of view I would like to go with the error.

I misread! Thanks for pointing that out. :)

Confused myself there.


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

This PR (HEAD: 9bf4791) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/crypto/+/193079 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info


func ExampleBcrypting() {
password := []byte("mypassword")
securedPassword, err := GenerateFromPassword(password, DefaultCost)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe you can rename it hashedPassword, like the first param of CompareHashAndPassword

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's salted and hashed. As saltedHashedPassword was a little to long for me, I called it secured.
Does that make sense?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ping

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok. But securedPassword comes from nowhere. But it's clear to me.
I try to improve.
But you're right. 👍

@gopherbot
Copy link
Contributor

Message from Lars Gohr:

Patch Set 2:

Should be fixed now


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 2: Code-Review+1


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 2: Run-TryBot+1


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 2:

TryBots beginning. Status page: https://farmer.golang.org/try?commit=e3cd2cc9


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 2: TryBot-Result+1

TryBots are happy.


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@elgohr
Copy link
Author

elgohr commented Nov 1, 2019

So what's missing for this getting merged?

@gopherbot
Copy link
Contributor

Message from Ian Lance Taylor:

Patch Set 2:

Ping Filippo.


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Lars Gohr:

Patch Set 2:

Patch Set 2:

Ping Filippo.

Already did that on the 16th of October via Twitter...


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@elgohr
Copy link
Author

elgohr commented Dec 26, 2019

Ping

1 similar comment
@elgohr
Copy link
Author

elgohr commented Mar 5, 2020

Ping

@elgohr elgohr changed the title Add easy bcrypt example golang.org/x/crypto/bcrypt: Add easy bcrypt example Mar 7, 2020
@elgohr elgohr changed the title golang.org/x/crypto/bcrypt: Add easy bcrypt example golang.org/x/crypto/bcrypt: add easy bcrypt example Mar 7, 2020
@gopherbot
Copy link
Contributor

Message from Dave Cheney:

Patch Set 4:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

This PR (HEAD: 155868f) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/crypto/+/193079 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

This PR (HEAD: 4cac054) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/crypto/+/193079 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Filippo Valsorda:

Patch Set 6:

(5 comments)

Thank you! A few nits.


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 6:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Filippo Valsorda:

Patch Set 6:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@elgohr elgohr changed the title golang.org/x/crypto/bcrypt: add easy bcrypt example bcrypt: add easy bcrypt example Mar 20, 2020
@gopherbot
Copy link
Contributor

This PR (HEAD: bd8e858) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/crypto/+/193079 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

This PR (HEAD: f6acff4) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/crypto/+/193079 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@elgohr
Copy link
Author

elgohr commented Apr 23, 2020

Ping

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 9: Code-Review+1

Looks good to me. Even though we're in the freeze,
this is an example, so I think it should be okay.

Ping Filippo.


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@elgohr
Copy link
Author

elgohr commented Sep 17, 2020

Ping

@gopherbot
Copy link
Contributor

Message from Ian Lance Taylor:

Patch Set 9:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Go Bot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
Within the next week or so, a maintainer will review your change and provide
feedback. See https://golang.org/doc/contribute.html#review for more info and
tips to get your patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11, it means that this CL will be reviewed as part of the next development
cycle. See https://golang.org/s/release for more details.


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Go Bot:

Patch Set 2:

TryBots beginning. Status page: https://farmer.golang.org/try?commit=e3cd2cc9


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Go Bot:

Patch Set 2: TryBot-Result+1

TryBots are happy.


Please don’t reply on this GitHub thread. Visit golang.org/cl/193079.
After addressing review feedback, remember to publish your drafts!

@elgohr
Copy link
Author

elgohr commented Aug 1, 2022

Ping...

@google-cla google-cla bot added cla: no and removed cla: yes labels Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants