-
Notifications
You must be signed in to change notification settings - Fork 11
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
Invalid argument(s): Unsupported block type for private key: 17 #287
Labels
bug
Something isn't working
Comments
@cconstab has either atSign been reset? |
The error log is pretty brutal, here is a sample..
|
So on a hunch I deleted the ~/.ai6bh/@atgps01 directory to force a resync and can now send stuff again.. If anyone needs/wants the deleted directory I have it.. |
Root cause found and reported here: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When sending an at_talk message from @atgps01 to @atgps02 messages never arrive. When running with -v the following message appears in the log:-
'SEVERE|2023-01-27 09:09:43.059190| atTalk |Invalid argument(s): Unsupported block type for private key: 17'
This was the first time that these two atSigns communicated. This issue does NOT happen everytime in fact I have not seen it at all with other atSigns communicating.
But I also see no way to correct the error from a dev point of view.
Steps to reproduce
Expected behavior
Never to have a miss managed key if that is what the issue is.
Screenshots
No response
Smartphones
code used is the nosync branch which uses the at_chops lib
https://github.com/atsign-foundation/at_talk/tree/nosync
Were you using an atApplication when the bug was found?
at_talk
Additional context
I was testing to ensure that newly created atSigns can communicate without a problem using chops and notification (this used to have other issues in that the RSA key was not in place)
The text was updated successfully, but these errors were encountered: