NSS:ToolsToShip: Difference between revisions

no edit summary
No edit summary
 
No edit summary
Line 7: Line 7:
*"main" tools that get installed in the global program search path (like /usr/bin on Linux) and should therefore be documented and part of NSS' QA
*"main" tools that get installed in the global program search path (like /usr/bin on Linux) and should therefore be documented and part of NSS' QA
*"unsupported" tools that do not have documentation, that are not necessarily part of the NSS QA, that will not get installed in the search path, but in a secondary location like /usr/lib/nss/unsupported-tools
*"unsupported" tools that do not have documentation, that are not necessarily part of the NSS QA, that will not get installed in the search path, but in a secondary location like /usr/lib/nss/unsupported-tools
The idea is
*make the unsupported tools available with the OS, so that developers do not have to compile them themselves
*ensure that by default the unsupported tools will not be available on the command line
*require that developers add the unsupported directory to their search path
==Proposal for packaging==
Ship the unsupported tools in the same package as the supported tools.
This ensures that everybody looking for tools will find the unsupported tools as well! Having a separate package for the unsupported tools would make it much more difficult to find them.


==Group 1: Tools that are shipping already==
==Group 1: Tools that are shipping already==
Line 39: Line 50:
===dbck===
===dbck===
No docs. Proposal: do NOT package this tool
No docs. Proposal: do NOT package this tool
==Group 3: Requested or Proposed Undocumented tools==
We received requests to ship the following tools:
*derdump
*pp
*ocspclnt
*tstclnt
*selfserv
*vfyserv
*atob
*btoa
(There is more info on atob and btoa later in this document)
For the following tools we have not yet been asked to ship them, but they all seem to provide a functionality that might eventually be helpful while debugging or testing:
*addbuiltin
*symkeyutil
*p7content
*p7env
*p7sign
*p7verify
*vfychain
Assumption: nobody volunteers to write documentation for them short term.
Proposal based on that assumption: ship them as unsupported tools
==Group 4: Undocumented tools that should not get shipped==
It seems unlikely that non-NSS developers might want to use the following tools in their current state:
*bltest
*certcgi
*checkcert
*client
*crmftest
*dbtest
*digest
*example
*fipstest
*makepgq
*mangle
*minigzip
*oidcalc
*rsaperf
*sdrtest
*server
*shlibsign
*strsclnt
Confirmed users
563

edits