-
Notifications
You must be signed in to change notification settings - Fork 71
Implement the password support #671
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
base: main
Are you sure you want to change the base?
Conversation
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
b394157 to
3325dd7
Compare
|
I have read the CLA Document and I hereby sign the CLA |
f4c2f05 to
0248f4e
Compare
0248f4e to
2dd37be
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file must not be changed here, as it marks the upgrade procedure to qaul version 2.0.0-rc.1
We must create a new folder and a new qaul version (2.0.0 rc.4) to make the configuration file upgrade needed for your changes.
This should be done shortly before merging the PR(s) and must to reflect all changes of the configuration file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
resolved
a348fdb to
883b375
Compare
883b375 to
474d821
Compare
…anagement functions
474d821 to
63ffd51
Compare
Part of #531
Note:
Completed the core logic of adding password support, which includes updating the protobuf definitions. Also, I've been using unwraps in some places, and would add proper error handling at the completion of this PR.
I'm using
qaul_id: PeerIdinstead of QaulId, that would be updatedUpdate:
The commit history is now sane.
The protobuf definitions have been revised based on our IRC chat.