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

Feat: extract session key #324

Closed
wants to merge 2 commits into from

Conversation

Conni2461
Copy link

PR Type

Feature

PR Checklist

  • Tests for the changes have been added / updated.
  • Documentation comments have been added / updated.
  • A changelog entry has been made for the appropriate packages.
  • Format code with the nightly rustfmt (cargo +nightly fmt).

Overview

It wraps the SessionKey String in a secrecy::Secret which is a breaking change for ppl who have implemented their own storage backend. I, e.g., did that and implemented a backend system for fred.rs because fred has sentinel support. If you guys are interested i can also upstream that.

After that it stores the extracted sessionkey in the Session struct which makes it accessible for users.

Closes #306
Closes #307 It basically finishes that PR. I also pulled their commits and squashed them.

I just need that feature, sooner rather than later, so i thought i implement it rather than poking the ppl involved, on the PR/Issue.

CC @miketwenty1
CC @LukeMathWalker

@miketwenty1
Copy link

@LukeMathWalker looks like @Conni2461 brought some life back into this request?

@LukeMathWalker
Copy link
Contributor

I'm sorry, I don't have any time for this at the moment and in the near future.

@miketwenty1
Copy link

Hey @robjtede @fafhrd91 if Luke doesn't wish to maintain this .. how would PR's like @Conni2461 ever get merged?

@robjtede
Copy link
Member

robjtede commented Oct 7, 2023

Hey @robjtede @fafhrd91 if Luke doesn't wish to maintain this .. how would PR's like @Conni2461 ever get merged?

Community reviews are hugely helpful in speeding up maintainers' efforts. I encourage lots of newcomers to get involved on this repo.

@miketwenty1
Copy link

Hey @robjtede @fafhrd91 if Luke doesn't wish to maintain this .. how would PR's like @Conni2461 ever get merged?

Community reviews are hugely helpful in speeding up maintainers' efforts. I encourage lots of newcomers to get involved on this repo.

@robjtede, If @Conni2461 rebases this .. would you consider merging it? I was under the impression Luke sort of owned this extra.

@robjtede
Copy link
Member

robjtede commented Oct 7, 2023

From just a quick skim of the diff, I'm not convinced this has enough tests or docs on new public items to demonstrate the use cases it opens up.

@LukeMathWalker
Copy link
Contributor

I am happy to continue taking care of core maintainance for sessions (security and key functionality), but I don't have bandwidth for more than that right now.

@Conni2461
Copy link
Author

From just a quick skim of the diff, I'm not convinced this has enough tests or docs on new public items to demonstrate the use cases it opens up.

I agree that i should have written test back in may. I no longer have a usecase for this so i can no longer justify investing time in adding tests/docs. Sorry

@Conni2461 Conni2461 closed this Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ability to extract SessionKey
4 participants