asignify
asignify copied to clipboard
Status
Hi, What is the current project status? Is it unmaintained or still alive?
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 :)
@emaste we should provide help to @vstakhov trust me he needs help to promote some of his projects :)
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:
asignify-sig:1:ZRASLrzUr+w=:faDj6u0equScWUdwMAVJvV3PX1kK1t/ONdfY9mLELXK0DtPfDOiBYGKYps3HSThZSINdUFIppR0VVja/cT8sCA==
BLAKE2 (asignify) = 97aacb968d56cd93b5be4b78597d6da9cad7edb6081d6462d85c3563cbb195778da3a19ee49966060ace9ac97bdf612bc2d8ba39c914b415322f 864dfb79da81
SIZE (asignify) = 6328
vs
untrusted comment: signed by key 43de7112337a763f
RWRD3nESM3p2P79J87X96kVVaLSKg0K601FDI1y0hQQRW7UmVcxrAHV/Ubq0r8lsDJjDlnSPtCUDX9kQxnpD55LH+jW/7nsqzws=