Bug#773861: Signify - OpenBSD's cryptographic signing tool

2015-01-13 Thread Riley Baird
On 14/01/15 12:46, Paul Wise wrote: On Sat, Jan 10, 2015 at 1:31 PM, Riley Baird wrote: Typos in upstream code: equivilent - equivalent ouput - output Do these really have to be fixed? They won't be visible to the user, and it's likely to annoy upstream more than anything. I'll do it if I

Bug#773861: Signify - OpenBSD's cryptographic signing tool

2015-01-13 Thread Riley Baird
On 13/01/15 21:40, Henrique de Moraes Holschuh wrote: On Tue, 13 Jan 2015, Riley Baird wrote: On 12/01/15 12:37, Brian White wrote: I don't maintain Signify it any longer (or even use it) so feel free to do with it whatever you like. Hmm... does that mean that I need to adopt signify before

Bug#773861: Signify - OpenBSD's cryptographic signing tool

2015-01-13 Thread Paul Wise
On Sat, Jan 10, 2015 at 1:31 PM, Riley Baird wrote: Typos in upstream code: equivilent - equivalent ouput - output Do these really have to be fixed? They won't be visible to the user, and it's likely to annoy upstream more than anything. I'll do it if I have to, though. If upstream are so

Bug#773861: Signify - OpenBSD's cryptographic signing tool

2015-01-13 Thread Henrique de Moraes Holschuh
On Tue, 13 Jan 2015, Riley Baird wrote: On 12/01/15 12:37, Brian White wrote: I don't maintain Signify it any longer (or even use it) so feel free to do with it whatever you like. Hmm... does that mean that I need to adopt signify before signify-openbsd will be accepted? Well, you cannot

Bug#773861: Signify - OpenBSD's cryptographic signing tool

2015-01-13 Thread Jakub Wilk
* Riley Baird bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch, 2015-01-10, 16:31: Have you talked with upstream about the name collision? No, I haven't. OpenBSD is definitely not going to change the name, How do you know? In any case, rename is not the only possible positive outcome of

Bug#773861: Signify - OpenBSD's cryptographic signing tool

2015-01-12 Thread Riley Baird
On 12/01/15 12:37, Brian White wrote: I don't maintain Signify it any longer (or even use it) so feel free to do with it whatever you like. Hmm... does that mean that I need to adopt signify before signify-openbsd will be accepted? -- To UNSUBSCRIBE, email to

Bug#773861: Signify - OpenBSD's cryptographic signing tool

2015-01-11 Thread Brian White
I don't maintain Signify it any longer (or even use it) so feel free to do with it whatever you like. -- Brian On Sat, Jan 10, 2015 at 12:31 AM, Riley Baird bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote: Thanks for the review

Bug#773861: Signify - OpenBSD's cryptographic signing tool

2015-01-09 Thread Riley Baird
Thanks for the review http://mentors.debian.net/debian/pool/main/s/signify-openbsd/signify-openbsd_8-1.dsc The package FTBFS here: |dh_auto_clean | make[1]: Entering directory '/build/signify-openbsd-EGTooy/signify-openbsd-8' | /bin/sh: 1: pkg-config: not found | Makefile:52: ***

Bug#773861: Signify - OpenBSD's cryptographic signing tool

2015-01-09 Thread Jakub Wilk
* Riley Baird bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch, 2015-01-08, 17:51: http://mentors.debian.net/debian/pool/main/s/signify-openbsd/signify-openbsd_8-1.dsc The package FTBFS here: |dh_auto_clean | make[1]: Entering directory '/build/signify-openbsd-EGTooy/signify-openbsd-8'

Bug#773861: Signify - OpenBSD's cryptographic signing tool

2015-01-07 Thread Riley Baird
Greetings, debian-security! OpenBSD has recently developed a tool called signify for cryptographic signing and verifying. It is extremely lightweight, and produces extremely small signatures. For an idea of how small, note that this is a complete signature: