Bug#701141: [PATCH 2/2] add several useful crypto utilities to libnss3-tools (Closes: #701141)

2013-03-29 Thread Mike Hommey
On Fri, Mar 29, 2013 at 01:07:50PM -0400, Daniel Kahn Gillmor wrote: > Re: Bug#701141: [PATCH 2/2] add several useful crypto utilities to > libnss3-tools (Closes: #701141) > > On Fri 2013-03-22 02:29:53 -0400, Daniel Kahn Gillmor wrote: > > > i'd be fine ship

Bug#701141: [PATCH 2/2] add several useful crypto utilities to libnss3-tools (Closes: #701141)

2013-03-29 Thread Daniel Kahn Gillmor
Re: Bug#701141: [PATCH 2/2] add several useful crypto utilities to libnss3-tools (Closes: #701141) On Fri 2013-03-22 02:29:53 -0400, Daniel Kahn Gillmor wrote: > i'd be fine shipping the last category and optionally the client/server > utilities with an nss- prefix if you think th

Bug#701141: [PATCH 2/2] add several useful crypto utilities to libnss3-tools (Closes: #701141)

2013-03-21 Thread Matthew Hall
We can always locate them using dpkg if we are unsure of their names, so a prefix or other small adjustment should be fairly innocuous. -- Sent from my mobile device. Daniel Kahn Gillmor wrote: >On 03/22/2013 01:51 AM, Mike Hommey wrote: > >> I'm not particularly happy with binaries with prett

Bug#701141: [PATCH 2/2] add several useful crypto utilities to libnss3-tools (Closes: #701141)

2013-03-21 Thread Daniel Kahn Gillmor
On 03/22/2013 01:51 AM, Mike Hommey wrote: > I'm not particularly happy with binaries with pretty generic names > ("addbuiltin" is a good example of such) ending up in /usr/bin... > But you can try to convince me otherwise. Or move them in some other > directory. hm, i think the following new bin

Bug#701141: [PATCH 2/2] add several useful crypto utilities to libnss3-tools (Closes: #701141)

2013-03-21 Thread Matthew Hall
They could be prefixed with nss- as needed. But it defeats the purpose of libnss-tools package if so many are missing by default. -- Sent from my mobile device. Mike Hommey wrote: >On Fri, Mar 22, 2013 at 01:28:37AM -0400, Daniel Kahn Gillmor wrote: >> On 03/22/2013 12:47 AM, Matthew Hall wrot

Bug#701141: [PATCH 2/2] add several useful crypto utilities to libnss3-tools (Closes: #701141)

2013-03-21 Thread Matthew Hall
Well I have some things I want to encrypt with various symmetric keys, which I am required to protect using NSS's PKCS11 nssdb for reasons of FIPS compliance in my day job. In order to insert these into the nssdb symkeyutil is critical because certutil only supports asymmetric keys with certs. -

Bug#701141: [PATCH 2/2] add several useful crypto utilities to libnss3-tools (Closes: #701141)

2013-03-21 Thread Mike Hommey
On Fri, Mar 22, 2013 at 01:28:37AM -0400, Daniel Kahn Gillmor wrote: > On 03/22/2013 12:47 AM, Matthew Hall wrote: > > BEAUTIFUL bug fix. Thank you so much for doing this, it is a big help for > > usage of NSS, especially symkeyutil, despite the bad documentation I really > > needed that one so m

Bug#701141: [PATCH 2/2] add several useful crypto utilities to libnss3-tools (Closes: #701141)

2013-03-21 Thread Daniel Kahn Gillmor
On 03/22/2013 12:47 AM, Matthew Hall wrote: > BEAUTIFUL bug fix. Thank you so much for doing this, it is a big help for > usage of NSS, especially symkeyutil, despite the bad documentation I really > needed that one so much I had to recompile from deb src and hand copy it into > place. Well, it

Bug#701141: [PATCH 2/2] add several useful crypto utilities to libnss3-tools (Closes: #701141)

2013-03-21 Thread Matthew Hall
BEAUTIFUL bug fix. Thank you so much for doing this, it is a big help for usage of NSS, especially symkeyutil, despite the bad documentation I really needed that one so much I had to recompile from deb src and hand copy it into place. -- Sent from my mobile device. Daniel Kahn Gillmor wrote:

Bug#701141: [PATCH 2/2] add several useful crypto utilities to libnss3-tools (Closes: #701141)

2013-03-21 Thread Daniel Kahn Gillmor
Listed below are the tools in mozilla/dist/bin which we could ship in debian's libnss3-tools package (see http://bugs.debian.org/701141) I'm noting my consideration here about which tools to ship or not ship. "YES" means the binary was already shipped in 2:3.14.3-1 "NO" means we should not ship "