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

Status #9

Open
Ypnose opened this issue Jun 21, 2016 · 9 comments
Open

Status #9

Ypnose opened this issue Jun 21, 2016 · 9 comments

Comments

@Ypnose
Copy link

Ypnose commented Jun 21, 2016

Hi,
What is the current project status? Is it unmaintained or still alive?

@vstakhov
Copy link
Owner

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.

@Ypnose
Copy link
Author

Ypnose commented Jun 22, 2016

I'm starting to be interested about it but I doubt only one person will "tilt the balance"…

@emaste
Copy link

emaste commented Jun 22, 2016

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 :)

@bapt
Copy link
Contributor

bapt commented Jun 22, 2016

@emaste we should provide help to @vstakhov trust me he needs help to promote some of his projects :)

@aparcar
Copy link

aparcar commented Jun 11, 2020

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.

@vstakhov
Copy link
Owner

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.

@aparcar
Copy link

aparcar commented Jun 11, 2020

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

@aparcar
Copy link

aparcar commented Jul 17, 2020

@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.

@aparcar
Copy link

aparcar commented Jul 17, 2020

@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=

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

No branches or pull requests

5 participants