-
Notifications
You must be signed in to change notification settings - Fork 10
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
Status #9
Comments
I'd not say it is unmaintained. There is just no interest to the project from the community. And I'm not the world best promoter, I'm afraid. |
I'm starting to be interested about it but I doubt only one person will "tilt the balance"… |
I'm interested. I think there is (or will be) broader interest in these topics, it just takes some promotion and marketing in order to convince folks that they're interested :) |
Hi, I think this project is rather great especially for embedded devices. Is there any reason it is not compatible with the current key format of signify? It'd be great to have asignify as a more feature rich and much smaller drop in replacement for OpenBSDs signify. |
AFAIR, it supports signatures verification, so only private key format is different. The main reason was because OpenBSD specified static set of algorithms with no possibility to change/extend in future. That was my main point of disagreement. But I might miss something after such a long time. |
From my understanding the algorithm is stored in the first two bytes, therefore changeable in the future: https://github.com/aperezdc/signify/blob/master/signify.c#L55 |
@vstakhov I'm thinking of slightly modifying the cli so it can be used as a drop in replacement. It would be nice to have a very simple tool for signature validation. |
@vstakhov The signatures are also very different:
vs
|
Hi,
What is the current project status? Is it unmaintained or still alive?
The text was updated successfully, but these errors were encountered: