-
Notifications
You must be signed in to change notification settings - Fork 376
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
Update gem to get latest changes #36
Comments
Are you asking to cut a new release? |
Yes, please :) |
Released 0.1.12. Let me know if you'd like to join as a co-maintainer. On Mon, May 5, 2014 at 12:27 PM, keysen [email protected] wrote:
Jeff Lindsay |
Yanked and re-released as 1.0 since there were backwards incompatible API changes. |
Thanks a lot :). I could join as co-maintainer, why not! |
Added, welcome! |
Hello,
I must check the algorithm found in the token to avoid some errors, because you can encode with HMAC or RSA, but if we choose RSA, we use #encode where the shared secret is an instance of RSA, and the problem it's that is different it's a string when we choose HMAC.
Because I store the shared secret in my DB, I want to make restriction on the availables algorithms.
Could you please update your gem, because my current answer to this problem require to get access your latest added method #decoded_segments.
The text was updated successfully, but these errors were encountered: