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

[FIX] Keyban now correctly checks the master key validity #425

Merged
merged 1 commit into from
Sep 9, 2024

Conversation

Florimond
Copy link
Member

Keyban just didn't work. There was a strange channel check while all that was required was to check the validity of the master key. See straighforward code change, for more info.

@Florimond Florimond self-assigned this Aug 30, 2024
@coveralls
Copy link

coveralls commented Aug 30, 2024

Coverage Status

coverage: 92.793% (-0.04%) from 92.83%
when pulling b4b4aed on fix_keyban
into 996fa4a on master.

@Florimond Florimond force-pushed the fix_keyban branch 4 times, most recently from 3078395 to 8264a05 Compare August 30, 2024 00:39
Keyban just didn't work. There was a strange channel check while all
that was required was to check the validity of the master key.
See straighforward code change, for more info.

Among other todos to discuss with @kelindar:

Can a master key expires?
@Florimond Florimond changed the title [DRAFT][FIX] Keyan now correctly checks the master key validity [DRAFT][FIX] Keyban now correctly checks the master key validity Aug 31, 2024
@Florimond Florimond marked this pull request as ready for review September 9, 2024 23:20
@Florimond Florimond merged commit 74e6649 into master Sep 9, 2024
3 checks passed
@Florimond Florimond deleted the fix_keyban branch September 9, 2024 23:21
@Florimond Florimond changed the title [DRAFT][FIX] Keyban now correctly checks the master key validity [FIX] Keyban now correctly checks the master key validity Sep 14, 2024
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.

3 participants