-
Notifications
You must be signed in to change notification settings - Fork 3
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
user-key #3
Comments
Hi, I try to switch from the "original" keyble to this, as I am more python fan (than java), and the other required "node" is not easily available any more. I decided to reset the lock, and re-register users. I also found the same error message as you. Status does not give any reasonable response, but lock and unlock run without error, but the lock does not move. |
Hi @yunnanpl and @frederictobiasc, We are in the same situation that the "original" keyble does not work anymore and we are looking for alternatives.
Could you make this repository work in the end or what solution did you use after all? I'd appreciate any help! |
I'm sorry I missed all the notifications. (aka too many projects). One of the problems is the missing support for decrypting messages. |
@schlagmichdoch : I was using the "original" node release for the time being. Now unfortunately it stopped working too, so it seems to be time to switch to something more "pythonic". |
I've pushed a couple of old commits I forget. Open/Close should now work. |
Sounds good! |
I honestly don't know. Both "should" work. If you have time to test the new commits it would be great. |
Hey and thanks for your work.
When I'm trying to register, the script
keyble.py
fails constantly in line 61 since userkey is not set. The help states, that user-key is generated when registering, so it seems like a bug.Any idea how to get it to work?
The text was updated successfully, but these errors were encountered: